Sheet1

In the middle of the iteration, how does a team handle requirement changes
from the customer?

What would be a suggested way to share and sustain knowledge with

members in a team?

How does the team know what to work upon during the iteration?

For any meeting that development team members, working in agile, have
among them, what are the points to consider?

When in a team, following Location Independent Agile model, there are

people distributed across geographies what can be a basic
recommendation?

How can one ensure that the code adheres to good coding standards?

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?

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

If you are working in a customer facing agile team, who is more

mature/ready for Agile?

When you have more than one agile team working on a single product,
which all among the following are crucial considerations?

Page 1
 Sheet1

What do you think is a good way for team members to remain updated on
work status at any given time?

What is an effective way to ensure that the integrated code is working as

per the acceptance criteria/business requirements?

What happens if the offshore team members are not able to participate in
the iteration demo due to timezone/infrastructure issues?

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?

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 3 hrs common time, M2 - 2 such M1
teams, M3 - 3 such M1 teams with more than one ProductOwner/specialist,
M4 - 4 such M1 teams with more than one ProductOwner/specialist)

How does an agile team obtain clarity on backlog items that may be picked
up in subsequent iterations?

When multiple team members are working on a related feature, how often
should they integrate their work?

How should a team have quality standards built into its deliverables?

When a Product Owner brings up an interesting feature/idea, how should a

team respond?

Page 2
 Sheet1

In a team, if someone gets stuck with the technical tasks during the
iteration, what is the immediate next step?

In a team that follows agile, how would a team member know about the
details of what others are working on?

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

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

What should be a standard way for anyone outside an agile team to get the s

Given pice of work to be executed in agile, how would you form a team?

How does an agile team manage requirements in a productive manner.

Page 3
 Sheet1

Its not recommended to incorporate any changes during an ongoing iteration

Team can always take up the changes and extend iteration duration if needed
Team has to exchange stories if the Scrum Master/Lead convey the criticality of the changes
Team may take up the changes in flight after discussing the overall impact with the project owner

Sharing of best practices and lesson learnt through email

Sharing knowledge through knowledge sharing session
Sharing knowledge through format conversations e.g. during lunch breaks
Updating best practices, lessons learnt and other topics in a central place accessible to all

The team participates in the iteration planning during which the Lead/Onsite/Scrum Master decides who should work on w
The team participates in iteration planning during which the team discusses with the Product Owner and finalizes who sh
The Scrum Master has regular interaction with the Product Owner. He/she guides the team on the tasks to be taken up.
Iteration plans are shared by Product Owner beforehand; any spill over from last iteration is taken up by default.

Dev team must keep such meetings to minimal or zero occurrences

Dev team must not allow such meetings to go beyond an hour.
Dev team must restrict such meetings to maximum 30 minutes, with few exceptions.
Dev team to decide on numbers and duration of such meetings based on situations.

The members must have at least 3 hours overlap time between all of them.
The members must have at least the daily sync-up together.
All team members must have a common 3 hours in a week to sort out dependencies.
All team members must come together at least once everyday. Amount of time overlap can be flexible.

It can be checked against the coding guidelines for the technology used by a similar project.
The code has to be reviewed by the technical expert of the team.
The code has to pass through the static code analysis without any violations.
The code has to be self reviewed to verify coding standards against a documented checklist.

Meetings must be scheduled with a lead time so that the participants can plan their work better.
Meetings must have a set agenda to facilitate a focused discussion and reduce digressions.
Meetings must be facilitated and time-boxed.
Team Lead/ScrumMaster must facilitate discussions but he/she may close meetings as per preference.

Through peer reviews

Through functional testing done by testers
Through formal unit testing using tools/softwares/plugins

Our TCS team.

Customer team.
Our TCS team and Customer team are equal.
Not sure.

All teams need to have similar agile maturity.

Product Owner/Product Specialists to devote similar time to all teams.

Page 4
 Sheet1
Teams to have occasional sync-up meets to eliminate dependencies.
All teams to have an identified co-ordinator and they stay in continuous touch to eliminate differences/issues.

Having a updated physical/digital Kanban board.

Sharing status through email with all.
Sharing individual updates with the Lead and the Lead sharing a consolidated summary with all.
Sharing and referring status reports that are shared daily.

Through automated functional tests.

Through manual functional tests.
Through automated unit tests.
Through manual unit tests.

No issues. Onsite members can have the iteration demo with the Product Owner; it is a single team anyway.
Offshore members will miss the opportunity to interact with the Product Owner and get the direct feedback about the incr
No major issue. Since offshore Lead and onsite members participate in the demo with the Product Owner, they can casc
It is a loss as the offshore members will not be able to contribute to ideas related to way of working.

Through SCM (Source Code Management tool) triggered build.

Through scheduled build.
By triggering automated build after check-in.
Through SCM (Source Code Management tool) based code branching.

M1.
M2.
M3 or M4.
The model we follow is not in the answer options.

Team discusses and clarifies doubts on backlog items in the iteration planning meeting.
Product Owner creates detailed user stories (aligned to agreed upon Definition of Ready) in the backlog before the iterati
Team can interact with the Product Owner multiple times during an iteration without waiting for the next iteration planning
Team can have backlog refinement session with the Product Owner during every iteration for gaining clarity on the subse

Depends on the whether the integration will break the build.

After they reach a logical end of coding the functionality.
In a scheduled daily (or multiple times in a day) frequency.
In a scheduled weekly (or multiple times in a week) frequency.
By procuring the best test automation suite applicable for the team.
By having an agreed and evolving set of Definition of Done items, which are automated wherever possible.
By having a robust Definition of Ready mechanism so that stories are granular enough.
Team must have a strong set of quality assurance professionals to create built in quality.

If the feature/idea sounds out of the box, team must accept it in the backlog.
Team should analyse the feature/idea based on the domain knowledge, validate the same or suggest improvements.

Page 5
 Sheet1
Even if the feature/idea is not so new, as the Product Owner understands the market demands better, team should accep
Team to analyse the technical feasibility and capacity before accepting the idea.

Without wasting time, the team member has to inform the Lead/onsite coordinator and take up another task.
The team member can reach out to other team members for help.
The team member can raise the issue during Team Retrospective.
Team member must search in google, technical forums without wasting time.

The Product Owner and the Scrum Master are responsible for maintaining work transparency.
The team should have a daily sync-up.
The onsite coordinator should share daily status for each member.
They may know from the backlog maintained in a tool (Jira, Prime, etc.) which will show the items as assigned to membe

The Scrum Master knows the status as he/she only assigns tasks to members; He/she can use any tool to manage the s
The onsite members are in a better position to track tasks at their end as they co-ordinate between the Product Owner an
All the tasks can be maintained in a common place such as a Wiki / Jira / excel / physical board / wall / any other system
The customer/Product Owner should manage and track the tasks through any available tool.

Team discuss how they can improve…

Kanban

exp, Not exceeding 9

Team must have all the required skill
exp, Not exceeding 12
Freshers

All requirements should be maintained in a common place

Page 6
 Sheet1

x x

x
x x

x
x
x

x x
x x

Page 7
 Sheet1
x
x

X
x
X

x
x
x

Page 8
 Sheet1

done/Doing/Done'.

x
x

Page 9