Tentamen (uitwerkingen)
Tcs Agile for Practitioners Assessment Delivery
Tcs Agile for Practitioners Assessment Delivery
[Meer zien]Voorbeeld 2 van de 5 pagina's
Voorbeeld 2 van de 5 pagina's
In winkelwagengesponsord bericht van onze partner
Voorbeeld van de inhoud
lOMoARcPSD|10935195This will not get you a 100%, this got me 82%, enough to pass.
1. When PO brings up an new feature, how should a team response?
a. if feature/idea sounds out of the box, team must accept it in the backlog
b. team should analyze the feature/idea based on domain knowledge, validate the same & suggest
improvements
c. ……………, team must accept it. >> Ans
d. Team to analyze the technical feasibility and capacity before accepting the idea.
2. When you have more than one agile team working on a single product, which are crucial
considerations?
e. All teams need to have similar agile maturity
f. PO/Product specialist to devote similar time to all teams>>Ans
g. Teams to have occasional synch-up meets to eliminate dependencies >> Ans
h. All teams to have an identified coordinator and they stay in continuous touch to eliminate
differences >> Ans
3. Suggested way to share & sustain knowledge with members in a team?
i. Sharing of best practices and lesson learnt through emails
j. Sharing knowledge through knowledge sharing sessions
k. Sharing knowledge through informal conversations eg lunch breaks
l. Updating best practices, lesson learnt and other topics in a central place accessible to all >> Ans
4. Standard way to get for anyone outside an agile team (eg delivery partner) to get the work status
any time?
m. He/she can refer physical/digital Kanban board maintained by the team >> Ans
n. All team members need to send email updates to him/her daily
o. Have status review meeting whenever required
p. By talking to each team member daily to understand the status
5. What do you think is a good way for team members to remain updated on work status at any given
time?
q. Having a updated physical/digital Kanban board>> Ans
r. Sharing status through email with all
s. Sharing individual updates with the lead and the lead sharing a consolidated summary with all
t. Sharing and referring status reports that are shared daily
6. Recommended way to run retrospective?
u. Team discusses the feedback received during iteration demo, creates a roadmap in retrospective
v. Team discussed how they can improve their way of working, picks up one or two improvement
areas for next iteration>> Ans
w. Team takes a stock of current velocity and forecasts the velocity for the next iteration
x. Team is encouraged to identify and take up process improvement initiatives
7. Effective way to ensure that the integrated code is working as per the acceptance criteria?
y. Through automated functional tests
z. Through manual functional tests
aa. Through automated unit tests>>Ans
bb. Through manual unit tests
8. In a team if someone gets stuck in the technical tasks during the iteration, what is the immediate
next step?
, lOMoARcPSD|10935195
This will not get you a 100%, this got me 82%, enough to pass.
cc. W/o wasting time, the team member has to infirm the lead/onsite coordinator and take up
another task
dd. Team members can reach out to other team members for help>>Ans
ee. Team member can raise the issue during team retrospective
ff. Team member must search in google, technical forums w/o wasting time
9. In an agile team, how would a team member know what others are working on?
gg. PO & SM are responsible for maintaining work transparency
hh. Team should have a daily synch up >>Ans
ii. Onsite coordinator should share daily status for each member
jj. They may know from the backlog maintained in a tool (Jira, Prime etc.) which will show the items
assigned to each members
10. After a team member creates a working code at her level, what is the fundamental way to ensure
quality of each line?
a. Through peer review
b. Through functional testing done by testers
kk. Through formal unit testing using tools/s/w/plugins>>Ans
11. If you are working in a customer facing agile team, who is more mature/ready for agile?
c. Our TCS team
d. Customer team
e. Both are equal
ll. Not sure>>Ans
12. For any meeting that development team members, working in agile, have among them, what are the
points to consider?
mm. Dev team must keep such meetings to minimal or zero occurrences>>Ans
nn. Dev team must not allow such meetings to go beyond an hour
f. Dev team must restrict such meetings to max 30mins, with few exceptions
oo. Dev team to decide on numbers & duration of such meetings based on situations>>Ans
13. How should a team have quality standards built into its deliverables?
g. By procuring the best test automation suite applicable for the team
h. By having an agreed & evolving set of DoD items, which are automated wherever possible>>Ans
i. By having robust definition of ready mechanism so that stories are granular enough
j. team must have a string set of quality assurance professionals to create built in quality
14. Agile WoW in meetings run?
k. Meetings must be scheduled with a lead time so that the participants can plan their work better
l. Meetings must have a set agenda to facilitate a focused discussion and reduce digressions
m. Meetings must be facilitated and time-boxed>>Ans
n. team lead/SM must facilitate discussions but he/she may close meetings as per preference
15. for an agile team, easy way to track the task?
o. SM knows the status as he/she only assigns tasks to members, he/she can use any tool to
manage the same
p. Onsite members are in a better position to track tasks at their end as they co-ordinate between
PO and rest of the team
q. All the tasks can be maintained in a common place (jira,,physical board etc.) with an indication
doing, done, to be done>>Ans
Voordelen van het kopen van samenvattingen bij Stuvia op een rij:
Verzekerd van kwaliteit door reviews
Stuvia-klanten hebben meer dan 700.000 samenvattingen beoordeeld. Zo weet je zeker dat je de beste documenten koopt!
Snel en makkelijk kopen
Je betaalt supersnel en eenmalig met iDeal, creditcard of Stuvia-tegoed voor de samenvatting. Zonder lidmaatschap.
Focus op de essentie
Samenvattingen worden geschreven voor en door anderen. Daarom zijn de samenvattingen altijd betrouwbaar en actueel. Zo kom je snel tot de kern!
Veelgestelde vragen
Wat krijg ik als ik dit document koop?
Je krijgt een PDF, die direct beschikbaar is na je aankoop. Het gekochte document is altijd, overal en oneindig toegankelijk via je profiel.
Tevredenheidsgarantie: hoe werkt dat?
Onze tevredenheidsgarantie zorgt ervoor dat je altijd een studiedocument vindt dat goed bij je past. Je vult een formulier in en onze klantenservice regelt de rest.
Van wie koop ik deze samenvatting?
Stuvia is een marktplaats, je koop dit document dus niet van ons, maar van verkoper divedmark. Stuvia faciliteert de betaling aan de verkoper.
Zit ik meteen vast aan een abonnement?
Nee, je koopt alleen deze samenvatting voor €11,49. Je zit daarna nergens aan vast.
Is Stuvia te vertrouwen?
4,6 sterren op Google & Trustpilot (+1000 reviews)
Afgelopen 30 dagen zijn er 50064 samenvattingen verkocht
Opgericht in 2010, al 14 jaar dé plek om samenvattingen te kopen