After a team member creates a working code at her level, what is the fundamental way to ensure quality of

each line?
1) Through peer reviews
2) Through functional testing done by testers
3) Through formal unit testing using tools/software/plugins

How can one ensure that the code adheres to good coding standards
1) It can be checked against coding guidelines from the technology used by a similar project
2) The code has to be reviewed by the technical expert of the team
3) The code has to pass through the static code analysis without any violations
4) The code has to be self reviewed to verify coding standards against a document check list

When in a team, following location independent agile model, there are people distributed across geographies
what can be a basic recommendation
1) The members must have at least 3 hours overlap time between all of them
2) The members must have at least the daily sync-up together
3) All team members must have a common 3 hours in a week to sort out dependencies
4) All team members must come together at least once everyday. Amount of time overlap can be
flexible

What would be a standard way for anyone outside an agile team (example delivery partner of an account) to
get the status of the work at any point in time
1) He or she can refer the physical/digital kanban board which is maintained by the team
2) All team members need to send email updates to the him/her daily
3) Have a status review meeting whenever required
4) By talking to each other daily to understand the status

What happens if the offshore team members are not able to participate in the iteration demo due to
timezone / infrastructure issues
1) No issues. Onsite members can have the iteration demo with the product owner; it is a single team
anyway
2) Offshore members will miss the opportunity to interact with the product owner and get the
direct feedback about the increment they created
3) No major issue. Since offshore lead and onsite members participate in the demo with the product
owner, they can cascade the feedback back to the offshore members
4) It is a loss as the offshore members will not be able to contribute to ideas related to way of working

For an agile team, what is an easy way to track the tasks

1) The scrum master knows the status as he/she only assigns tasks to members; he/she can use any tool
to manage the same
2) The onsite members are in a better position to track tasks at their end as they coordinate between the
product owner and rest of the team
3) All the tasks can be maintained in a common place such as wiki / jira / excel / physical board /
wall / any other system with an indication of “to be done / doing / done”.
4) Customer/product owner should manage and track the tasks through any available tool

When you have more than one agile team working on a single product, which all among the following are
crucial considerations
1) All teams need to have similar agile maturity
2) Product owner / product specialists to devote similar time to all teams
3) Teams to have occasional sync-up meets to eliminate dependencies
4) All teams to have an identified coordinator and they stay in continuous touch to eliminate
differences / issues
What do you think is a good way for team members to remain updated on work status at any given time?
1) Having a updated physical / digital kanban board
2) Sharing status through email with all
3) Sharing individual updates with the lead and the lead sharing a consolidated summary with all
4) Sharing and referring status reports that are shared daily

In the middle of the iteration, how does a team handle requirement changes from the customer
1) Its not recommended to incorporate any changes during an ongoing iteration
2) Team can always take up the changes and extend iteration duration if needed
3) Team has to exchange stories if the scrum master / lead convey the criticality of the changes
4) Team may take up changes in flight after discussing the overall impact with the product owner

If you are working in a customer facing agile team, who is more mature / ready for agile
1) Our TCS team
2) Customer team
3) Our TCS team and customer team are equal
4) Not sure

In a team, if all the members do regular check-in of the code, then how does one ensure that the code is not
broken anywhere
1) Through SCM (source code management tool) triggered build
2) Through scheduled build
3) By triggering automated build after check-in
4) Through SCM (source code management tool) based code branching

Have you undergone any “living / agile” session conducted by agile ninja coaches or unit agile leaders
1) Yes
2) No

How does an agile team manage requirements in a productive manner

1) Business analyst should manage the business requirements and technical team should manage the
technical requirements
2) Every team member should maintain a personal backlog of items they are working on
3) Scrum master / onsite coordinator to manage the requirements and communicate tasks to the team
members
4) All the requirements should be maintained in a common place such as wiki/jira/white board
and managed by the entire team

How should a team have quality standards built into its deliverables?
1) By procuring the best test automation suite applicable for the team
2) By having an agreed and evolving set of Definition of Done items, which are automated
whenever possible
3) By having a robust Definition of Ready mechanism so that the stories are granular enough
4) Team must have a strong set of quality assurance professionals to create build in quality

What would be a suggested way to share and sustain knowledge with members in a team?
1) Sharing of best practices and lessons learnt through emails
2) Sharing knowledge through knowledge sharing sessions
3) Sharing knowledge through informal conversations e.g. during lunch breaks
4) Uploading best practices, lessons learnt and other topics in a central place accessible to all

If you are in an agile team, do you have distributed team members? Which of the TCS Location Independent
Agile models do you follow? (M1 – distributed agile team members with 3hrs common time, M2 – 2 such
M1 teams, M3 – 3 such M1 teams with more than one Product Owner / Specialist, M4 – 4 such M1 teams
with more than one Product Owner / specialist)
 1) M1
2) M2
3) M3 or M4.
4) The model we follow is not in the answer options

When a Product Owner brings up an interesting feature / idea, how should a team respond?
1) If the feature / idea sounds out of the box, team must accept it in the backlog
2) Team should analyse the feature / idea based on the domain knowledge, validate the same or
3) suggest improvements
4) Even if the feature / idea is not so new, as the Product Owner understands the market demands better,
team should accept it
5) Team to analyse the technical feasibility and capacity before accepting the idea

For any meeting that development team members, working in agile, have among them, what are the points to
consider?
1) Dev team must keep such meetings to minimal or zero occurances
2) Dev team must not allow such meeting to go beyond an hour
3) Dev team must restrict such meetings to maximum 30 minutes, with few exceptions
4) Dev team to decide on numbers and duration of such meetings based on situations

What is an effective way to ensure that the integrated code is working as per the acceptance criteria /
business requirements?
1) Through automated functional tests
2) Through manual functional tests
3) Through automated unit tests
4) Through manual unit tests

How does an agile team obtain clarity on backlog items that may be pickedup in subsequent iterations?
1) Team discusses and clarifies doubts on backlog items in the iteration planning meetings
2) Product owner creates detailed user stories (aligned to agreed upon Definition of Ready) in the
backlog before the iteration starts
3) Team can interact with the Product Owner multiple times during an iteration without waiting for the
next iteration planning
4) Team can have backlog refinement session with the Product Owner during every iteration for
gaining clarity on the subsequent ones

Given a piece of work to be executed in agile, how would you form a team?
1) Team must have all the required skills. Team size will depend on scope and budget
2) Team must have all required skills, headcount being less than 12
3) Team must have experienced people, head count not exceeding 9
4) Team must have mix of experienced and freshers with right skills. Team size will depend on scope
and budget.

In a team, if someone gets stuck with the technical tasks during the iteration, what is the immediate next
step?
1) Without wasting time, the team member has to inform the Lead / Onsite Coordinator and take up
another task
2) The team member can reach out to other team members for help
3) The team member can raise the issue during Team Retrospective
4) Team member must search in google, technical forum without wasting time

When multiple team members are working on a related feature, how often should they integrate their work?
1) Depends on whether the integration will break the build
2) After they reach a logical end of coding functionality
3) In a scheduled daily (or multiple times in a day) frequency
 4) In a scheduled weekly (or multiple times in a week) frequency

How does the team know what to work upon during the iteration?
1) The team participates in the iteration planning during which the Lead / Onsite / Scrum Master
decides who should work on what
2) The team participates in the iteration planning during which the team discusses with the
Product Owner and finalizes who should work on what
3) The Scrum Master has regular interaction with the Product Owner. He / She guides the team on the
tasks to be taken up
4) Iteration plans are shared by Product Owner beforehand; any spill over from the last iteration is taken
up by default

Which among the following is a recommended way to run Retrospectives?

1) Team discusses the feedback received during the iteration demo, creates a roadmap in the
Retrospective
2) Team discusses how they can improve their way of working; picks up one or two improvement
areas for next iteration
3) Team takes a stock of current velocity and forecasts the velocity for the next iteration
4) Team is encouraged to identify and take up Process Improvement (PI) initiatives

If you are asked to bring in agile way of working into the way a meeting runs, which one among the listed
options will you implement?
1) Meetings must be scheduled with a lead time so that the participants can plan their work better
2) Meetings must have a set agenda to facilitate a focused discussion and reduce the digressions
3) Meetings must be facilitated and time-boxed
4) Team Lead / Scrum Master must facilitate discussions but he / she may close meetings as per
preference

What is an effective way to ensure that the integrated code is working as per the acceptance criteria /
business requirements?
1) Through automated functional tests
2) Through manual functional tests
3) Through automated unit tests
4) Through manual unit tests

When in a team, following location independent agile model, there are people distributed across geographies
what can be a basic recommendation?
1) The members must have at least 3 hours overlap time between all of them
2) The members must have at least the daily sync-up together
3) All team members must have a common 3 hours in a week to sort out dependencies
4) All team members must come together at least once everyday. Amount of time overlap can be
flexible

In a team that follows agile, how would a team member know about the details of what others are working
on?
1) The Product Owner and the Scrum Master are responsible for maintaining work transparency
2) The team should have a daily sync-up
3) The onsite coordinator should share daily status for each member
4) They may know from the backlog maintained in a tool (Jira, Prime, etc) which will show the
items as assigned to members.