S.

No Questions

1 Which of the following statements are correct

Which of the following BEST describes the approach for

2 determining the Sprint length in Scrum?

Ron has just started as a Scrum Master for an Agile team. He

has acquired knowledge by reading multiple sources. After
3 practicing Scrum for a while on the job, he is looking for a
certification to benchmark. What can be recommended for
him?

4 Which one of these is NOT an XP practice?

5 The Product Owner in a Scrum project …

Kris is an experienced Project Manager with a customer

project where he commands the teams and micro manages
the team members at task level. How can he help the TCS
6 Agile vision?

7 Daily Scrum is NOT recommended for collocated teams

Lee joins a project team that attempts to build a consumer

device with embedded software_ The team is adopting 2-
week sprint Lee notices that the project must produce an
outcome that will be highly adoptable by the users to become
successful. After every Sprint Review, the Product Owner
keeps changing the Product vision and makes contradictory
statements about user needs. What can be suggested for this
8 environment?
 Lee joins a project team that attempts to build a consumer
device with embedded software_ The team is adopting 2-
week sprint Lee notices that the project must produce an
outcome that will be highly adoptable by the users to become
successful. After every Sprint Review, the Product Owner
keeps changing the Product vision and makes contradictory
statements about user needs. What can be suggested for this
8 environment?

9 Who manages the team's work during a Sprint?

10 Agile Manifesto has ... Values and ..... Principles

Agile Teams need to comply by the Agile Values and Principles

11 but have flexibility to choose appropriate value-adding
practices

12 The reason for holding regular Sprint Retrospective is

Noor's Scrum Team had a great Sprint Review of a new feature

with their Product Owner. Product Owner was happy with
new feature, and wanted to release the feature to user_ But,
the Scrum Team cannot do it themselves because production
13 environment is owned the company's IT operations team_
Scrum Team was directed to create a ticket with IT operations
for production release_ and wait a week for an Ops engineer
to manually Work on the ticket What is missing in this
environment?

14 What BEST describes a Scrum Team?

Martin is from the TCS BPS team. As part of TCS Agile vision.
he was recommended to attain EID competency in Agile.
15 Martin Was thinking that Agile was only for software. How
could Agile knowledge help Martin in his work?
 A team is having the first Sprint Planning meeting_ What are
16 the activities that the team must perform during the meeting?

Increasing number of TCS customers are moving to the Agile

17 way of working. Why is this a true statement?

18 Sprint itself is an event in Scrum

Charles is very knowledgeable on Scrum_ He joined a Scrum

Team where the Scrum Master is Magneto. Contrary to his
expectation of Scrum Master as a coach, he finds that
19 Magneto acts like a traditional manager_ Magneto controls
the team heavily by individually assigning tasks and leading
the Daily Scrum meetings to collect the percentage of task
completion. What is recommended for Charles?

20 Who owns quality in a Scrum Team?

Which of the following BEST represent the Scrum approach to

21 planning?

Which of these are the needed actions to realize TCS vision of

22 "0-4-2.?

Providing additional feature without clear understanding of

23 the business need - What is this category of waste?
 Providing additional feature without clear understanding of
23 the business need - What is this category of waste?

Which of the following statements about changing

24 requirements in software development, are correct?

Which framework prescribes User Story as the format for

25 backlog items?

Lee joins a project team that attempts to build a consumer

device with embedded software. The team is adopting 2-week
sprint. Lee notices that the project must produce an outcome
that will be highly adoptable by the users to become
26 successful. After every Sprint Review, the Product Owner
keeps changing the Product vision and makes contradictory
statements about user needs. What can be suggested for this
environment?

A Scrum Team works on a 4 weeks Sprint. After new Sprints,

the team finds that they spend more effort on unit testing, as
27 the code base size has increased. What can be BEST
recommended for this team?

28 Scrum defines roles events and artifacts

29 The time box for a Daily Scrum is …

On the last day of the Sprint, a Scrum Team named

Almostflone is ready to show their work but requires just 2
30 more days to complete the testing. What should the Scrum
Master recommend?
 There are two Product Development Teams, Team ToyZon and
Team Zan. Team ToyZon follows traditional way and Team Zon
31 follows Agile way of working. Which team has the higher
chance to provide early benefts to the customer?

Match the framework to its author(s) in the order of listing:

32 Scrum; Crystal; Extreme programming

Jerald is a leader of a TCS Customer Account. He learnt that

the company's aspiration on Agile is to become 100% Agile by
2020. He gathered his Agile Experts within the account and
33 asked them for a plan to transition from current way of
working to 100% Agile way of working as defined in the text
book. Jerald correctly understood TCS aspiration.

John, a team member, has completed EO -Agile for Beginners.

He wants to contribute to TCS Agile Vision. He wants to find
34 out what is planned for his account. Whom should he contact
for details?

35 What is the purpose of Sprint Review'?

36 A good Agile team should exhibit the following qualities ...

Mannar & Company kick started a major cross company

project that involved working with multiple business unit
leaders to build enterprise wide platform. Impressed by the
success of small projects in Agile: company leadership
37 enforced Agile in this transformation project. Shortly after few
Sprints, teams witnessed that The Product Owner was not
able to build consensus among the business unit leaders on
requirements. There were several political aspects behind the
collaboration. What went wrong?
 Mannar & Company kick started a major cross company
project that involved working with multiple business unit
leaders to build enterprise wide platform. Impressed by the
success of small projects in Agile: company leadership
37 enforced Agile in this transformation project. Shortly after few
Sprints, teams witnessed that The Product Owner was not
able to build consensus among the business unit leaders on
requirements. There were several political aspects behind the
collaboration. What went wrong?

38 The time box for a Daily Scrum is

….. improves the flow of business idea through its

39 development and release to users.

A team is having the first Sprint Planning meeting. What are

40 the activities that the team must perform during the meeting?

41 Which of these are Agile estimation techniques?

Which of the following statements BEST describe why Agile is

42 winning?

What is MOST likely to happen if the Product Owner is not

43 available during a Sprint?
 What is MOST likely to happen if the Product Owner is not
43 available during a Sprint?

44 Who owns the Product backlog?

45 What does NOT match with Agile Manifesto?

46 How should work be allocated to the team in a Scrum project?

Lee joins a project team that attempts to build a consumer

device with embedded software. The team is adopting 2-week
sprint. Lee notices that the project must produce an outcome
that will be highly adoptable by the users to become
47 successful. After every Sprint Review, the Product Owner
keeps changing the Product vision and makes contradictory
statements about user needs. What can be suggested for this
environment?

48 Only these people are allowed to attend Sprint Retrospective

Munnabhai knows the four values of Agile Manifesto by heart.

However, he was confused when a customer spoke with him
highlighting Agile characteristics of short software
49 development cycles or iterations. He could not recollect
anything about short iterations in Agile Manifesto. What did
he miss to learn about?

50 Which of these is a benefit of Agile?

51 TCS Agile vision ‘100% Agile by 2020’ means

52 Why is the Daily Scrum held at the same time and same place?

53 The Agile way is:

54 What is the purpose of Sprint burndown chart?

55 Which of these are Scrum anti patterns?

56 Which one is a popular tool used in Agile software development

57 What is a Kanban board?

The Scrum team Is using the Kanban board to make worK

visually available to all What CANNOT be Interred from the
58 board?
 The Agile approach to documentation is

59

Why were the practitioners of alternative

software development methods not satisfied with
the traditional waterfall method?

60

and acquired PSM I certification already The customer may

soon move to a large scale Agile Which other certification may
be beneficial for Eric so he can be prepared to help the
61 customer?

62 Agile principles can be only used for software development

Agile for Beginners course is intended towards motivating you

63 to learn more about agile so that you can become

Juaraz is a TCS Delivery Partner for the account ABC running in

Agile. Operating out of Mexico He has to ramp up the team
based on customer need, and he is not getting right skilled
people in Mexico He is acing at setting up another ODC at Pune.
india where his skill requirements are met for an effective
64 Distributed Agile set up, what is recommended?

65 Design Thinking is other name for Agile Manifesto

How is the Agile value responding to change over blowing a

plan addressed In Scrum

66
 How is the Agile value responding to change over blowing a
plan addressed In Scrum

66

Industry survey show that in traditional approach. users do not

use near1 60% of the features delivered What do you think ere
the probable causes

67

68 Product Owner and Scrum Master can be same person

 PLEASE USE THE ANSWERS MARKED IN GREEN
Agile and Design Thinking are same

Design Thinking is about Product Devopment Agile Manifesto is about Software Devopment

Design Thinking is finding the right things and Agile is about building the right things

Design Thinking is building the right things and Agile is about finding the right things

Sprints must be 30 days always

Product Owner unilaterally decides the duration of Sprint
Sprints must be two weeks always
The team must collectively agree on the length of the Sprint based on business need and
technical team's ability; subject to a maximum of one month
There is no rule on Sprint duration

Scrum Master Accredited Certificate (SMAC)

SAFe Agilist (SA)
Professional Scrum Master I (PS/VI I)

Test Driven Development

Extreme Reviews
Pair Programming
Continuous Integration
Refactoring

Has no control over the prioritization of Product Backlog Items

Has the final authority over the prioritization of Product Backlog Items
Collaborates with the developers over prioritization of Product Backlog Items, but the
developers have the final say
Collaborates with the developers over prioritization of Product Backlog Items, but Product
Owner has the final say
Creates the Product Backlog Items but leaves prioritization to Business Analyst

Proactively up-skill with skills needed to work in Agile Roles

No need to do anything as he can continue to be the Project Manager

Wait till his current customer adopts Agile

1
0

Apply design thinking first for initial phase and then bring in Agile later

More practices from Extreme Programming

Apply waterfall and have the Product Owner sign-off on the requirements

The Scrum Master manages the people so they can complete the work
The team manages the work by self-organization
The Product Owner manages the work
The Delivery Manager manages the work

• 4,10
• 6, 12
• 4.12
• 4.4

It allows the team to take a necessary break from work

It gives management information to use in team members' performance reviews
Provides an opportunity for the Scrum Team to inspect itself and create a plan for
improvements to be enacted during the next
Sprint.
Retrospectives are optional
Provides an opportunity for stakeholders to look at what the team is building

Feedback

Flow

Continuous Improvement

Small but have enough members to create the Product Increment

Collaborate with each other to self-organize their work
Team members must be specialists
Cross Functional
Reports to Product Owner

Martin is right. Agile principles are not useful outside software development
XP and DevOps can help in Robotic Process Automation
Agile principles can help in continuously improving BPS processes
The team must discuss the problems encountered in the earlier project

Team chooses the Product Backlog Items to work in the Sprint and crals a Sprint Goal.

Team must draw up the Release Plan for the final product
Each team member should come prepared with their version of the plan
The team must look at the project plan prepared by the Product Owner and understand
their tasks

For last few years, there is a double digit increment in number of Agile projects (per PMS)
year on year

In 90% of executive conversations, customers bring in Agile as a topic of conversation

For all new engagements. TCS mandates Agile
This is not a true statement
Both 1 and 2

1
0

Be prepared to face such anti patterns and work together with the team to continuously
improve and eliminate anti-patterns

Correct his understanding of Scrum and accept that Scrum Master is the Team's manager

Protest about this at the earliest possible team meeting and let others know he is more
knowledgeable about Scrum

Scrum Master
Product Owner
Scrum Team
Testers
External QA team

Planning is a continuous activity done jointly by Scrum Master and Product Owner
Detailed planning is done upfront and not revisited
Whole team together does just enough upfront planning followed by continuous planning
throughout the project
Only planning in Scrum is the Sprint Planning
Scrum is one of the planning events

Agile Ready Partnership Review

All get Agile Certified
Agile Ready Workforce
Top-to-bottom Enterprise Agile Company ourselves
Agile Ready Workplace

Inventory
We do it all the time It is not a waste.
Over Production
Defects
Over Processing

In traditional way of software development, once the requirements are base lined, further
changes should undergo heavy change control process Review
Changes are acceptable till design but once development starts, any further change should
be rejected
In traditional way of software development, once the requirements are base lined, further
changes can be easily accepted with light process.

Organizations must adapt to rapidly changing market conditions to stay relevant in

Scrum
FDD
Crystal 0 Extreme Programming
DSDM

Apply design thinking first for initial phase and then bring in Agile later
More practices from Extreme Programming

Apply waterfall and have the Product Owner sign-off on the requirements

Unit testing is not fun anyway. As a self-organized team, choose to ignore the unit testing

Adopt practices like test automation from other frameworks like XP

Increase the duration of the sprint from 4 weeks to 6 weeks
Add two more temporary testers
Form a separate Testing team

3-5-3
5-3-3
3-3-5
5-5-3

Two minutes per person

15 minutes
2 ms
No time box 0 30 minutes

Extend the Splint by two days so that the team can complete the work

Close the sprint on time

Team ToyZon

Team Zon

Kent Beck Alistair Cockburn, Ken Schwaber and Jeff

Ken Schwaber and Jeff Sutherland; Kent Beck; Alistair Cockburn
Ken Schwaber and Jeff Sutherland; Alistair Cockburn; Kent
Alistair Cockburn Ken Schwaber and Jeff Sutherland Kent
Takeuchi and klonaka: Alistair Cockburn; Kent

Account Leadership

Customer Leadership
HR Manager

Product Owner can show the progress to the stakeholders and get the approval to release
the work to the production
To assess the team's productivity and possibly record the assessment score against the
performance
To inspect the working software with the key stakeholders and take the insights from the
feedback to next
So that the Scrum Team can reorganize for the next
Stakeholders and team discuss the Sprint Backlog for next

All in team must have the same level of technical

The team is self-organizing
The team should only take up tasks assigned by Product
The team must be hierarchical with a strict chain of
The team is cross-functional

For large transformation projects, Design Thinking is required before

Agile is based on trust and collaboration so that consensus can be arrived at quickly. This
scenario did not have that
Agile doesn't require any pre-requisites. It works very well in all context. In this scenario:
the Product Owner doesn't seem to be competent

Two minutes per person

15 minutes
2 hrs
No time box
30 minutes

Waterfall method
DevOps practices
Beta release
Change Control Board (CCB)

The team must discuss the problems encountered in the earlier project

Team chooses the Product Backlog Items to work in the Sprint and crafts a Sprint Goal.

Team must draw up the Release Plan for the final product
Each team member should come prepared with their version of the plan
The team must look at the project plan prepared by the Product Owner and understand
their tasks

Full Upfront Estimates

Planning Poker
Work Breakdown Structure
T Shirt sizing
Random Distribution

Products produced by an Agile approach are cheaper than those produced by any other
approach
Agile increases the chances of delivering early business value to the market and quickly
incorporate the feedback from the market usage

Products have faster time to market but may not meet immediate customer needs

Products are expensive when compared with products produced by other approaches, but
are of top quality.

The team self-organizes itself to create value

The Business Analyst helps the team until the Product Owner returns
The Sprint deliverables may not be of desired value
The Scrum Master plays the role of Product Owner
Scrum Master terminates the Sprint and waits for the Product Owner to return

Scrum Team
Product Owner
Scrum Master
Business Analyst
Technical Lead

Processes and tools over individuals and interactions

Working software over comprehensive documentation
Responding to change over following a plan
Contract negotiation over customer collaboration

The Scrum Master must assign tasks to individuals

Team members must volunteer for tasks appropriate to their skills
The complex tasks must be allocated by the Scrum Master
Tasks must be allocated to team members by the Product Owner
While senior team members volunteer for tasks, juniors must be assigned tasks by the
Scrum Master

Apply design thinking first for initial phase and then bring in Agile later
More practices from Extreme Programming

Apply waterfall and have the Product Owner sign-off on the requirements

Scrum Master and Development team

Product Owner and Development team
Scrum Master and Product Owner
Scrum Team

Agile Principles

Agile Guidelines
Agile Methods
Agile Phases

Reduced Risk
Faster time to market
Ability to respond to changing requirements
Improved collaboration between business and technical team
All of these
TCS to be regarded by the market and our customers as 100% right partner/advisor for
Agile Transformations Review
Every project in TCS must follow all practices of Extreme Programming
100% of TCS associates must be at least at Agile E3 competency
TCS to be regarded as 100% Enterprise Agile company
There should not be any Agile related non-compliance in the project audits

So that the place can be named as Daily Scrum Hub

The consistency reduces complexity and overhead
The Product Owner demands it
Rooms are hard to book and this helps in advance booking
There is no such rule

To produce working software of high business value and of the right quality, early and
incrementally
To produce working software only after requirements documentation has been signed off
by the Product Owner
To produce simple prototypes early, and release all only at the end of the project
Each developer to sit with business every day, code as they mutually discuss, and move to
production when the business seems

It is used to measure utilization of the development team

It is used to measure defects introduced during the Sprint
It is used to measure how much work is yet to be done to reach Sprint goal
It is used to measure how fast the Product Owner turns around on the queries

Programmers as one Scrum Team and Testers as another Scrum Team

Scrum Master as a servant leader
Scrum Team with 20 members
Cross Functional team
Sprint duration of 6 weeks

Rexx
Jenkins
MS PowerPoint
Tally

A list of activities banned by the team

The set of Can Have requirements
A visible chart depicting the work to be done, work in progress and work done
Board that captures the details of the entire project for audit purpose

Number of items to be worked on by the team

Percentage completion
Tasks move from left to right
LImit work in progress
Do no documentation because it is a waste of lane

Do just enough documentation to support the development and use of

the product
DO Sufficient documentation to prove you have done a good Job
Do more documentation than usual because Agile Is risky
Agile Manifesto mandates zero documentation

Waterfall is not a lightweight process

The practitioners did not like to work in a formal system and hence
did not like any methodology at all
Waterfall experience did not add value to their resume
Waterfall model failed to meet the demand for speed and was not
friendly toward changing business needs and priorities

SAFe Program Consultant (SPC

Certified Scrum Master (CSM)
Professional Scrum Master ii (PSM ii)

1
0

project leader
Agile practitioner
project manager
certified manager
None of the above

Move the entire ODC to Pune, India

Understand the TCS Point of View on Distributed Agile and see how to apply at work

Ask Agile coach to study other accounts and put together a model for Distributed Agile

1
0

Product Owner can change me sprint Backlog any day

During the Sprint Planning. Development team has all the authority
to choose any Product Backlog item to work on
Product Owner writes lightweight Change Requests for quick approvals

Product Owner can change the plan for next Sprint based on latest
market conditions and feedback from last Sprint
Product Owner can change the Product Backlog any time

These features were developed based on initial assumptions about the

user requirements but assumption turned out to be wrong

By the time the features were delivered the market and user
requirements had changed
The marketing team did not advertise the product features

1
0
Correction First set

ok

ok

First
 First

ok
First
 First

Ok

ok

First

First

First

Not sure
ok

First

First

First
 First

ok

First
First

First

First

First
 First

First

ok

First
First

First

First
Ok

First

First

ok First

First

First
Ok First