Internal Use

Agile & Scrum Overview -

Getting ready for
PSM-I Certification
iEvolve
Offering ID:
Course ID: 55617

December 2022

The current presentation contains Alistair Cockburn’s Copyrighted Material, for educational purposes only.
Source: https://www.heartofagile.academy
Internal Use
Internal Use
Why this course?

Internal Use 2 TCS Internal

Internal Use

Internal Use TCS Internal

Internal Use

Please minimize multitasking

Interact as one team to help each other
✓Use Chat to collaborate and enter comments and/or observations
✓Feel free to use Teams/Webex reactions during the session
✓Have fun collaborating together

Think about how the material can help you personally and professionally, and in
your desired journey towards a Scrum Master (SM), Product Owner (PO) role,
or if you are looking to get a PSM-I Certification soon.

Internal Use TCS Internal

Internal Use

Hello!

▪ I am Jorge Carlos Ponton (aka Jorge, Yorch, George, or Ponton).

Born on February 1974, in Mexico City, Mexico.

▪ More than two decades as Consultant on IT Processes & Governance

▪ Passionate musician, technical communicator, and eager self-paced learner

▪ Collaborating with TCS since May 2013, working for BFSI major account, Data
Management Services and Governance. (Agile Coaching and Leadership,
Transformation and Innovation Management)

▪ Associate Consultant - Roles: Agile Coach for LATAM - Peru & Brazil / Data & Analytics
Program Manager / BI Specialist / HSE - Mgmt. Representative for TCS Guadalajara 4 My website:
https://jorgecarlosponton.com

▪ Having obtained such a mix of skills is giving me the opportunity to learn and serve the Emp. ID: 780625 – TCS Email:
greater good, helping on the betterment of my community and dear colleagues. [email protected]

Linkedin:https://linkedin.com/in/
Helping others create a better future! jorgecarlosponton

Internal Use TCS Internal

Internal Use
About the Course - What is in for me?
After completing this course participants will:

• 1. Be able to explain what is Agile, know the origins of Agile methods and frameworks, and have
a better idea of Agile nowadays
• 2. Be able to define and understand important concepts of Scrum such as:
✓ Sprint
✓ Product Backlog
✓ Scrum Roles (Product Owner, Scrum Master, Developers)
✓ Scrum Events (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective)
✓ Scrum Commitments (Product Goal, Sprint Goal, Definition of Done)
✓ Scrum Values
• 3. Know how to write a “User Story“
• 4. Be able to participate in scrum events confidently and add value to scrum projects
• 5. Will know how to do estimation for scrum projects
• 6. Be able to find out dos and don’ts of scrum project and thereby suggest the best way to
execute
• 7. Be able to get all participants ready for PSM examination

Internal Use 6 TCS Internal

Internal Use
Course Material Needed

Make sure to keep the following links open :

• Agile Manifesto : https://agilemanifesto.org/

• The 2020 Scrum Guide : https://scrumguides.org/scrum-guide.html

• Google : https://www.google.com/

Support material:

• Scrum.org - The Home of Scrum : https://scrum.org

• Scrum Quiz - Scrum Master Practice Test : ScrumQuiz.org

• Mikhail Lapshin’s Scrum Quizzes : https://mlapshin.com/index.php/scrum-quizzes/

Internal Use 7 TCS Internal

TCS Internal
Internal Use

What is Agile?

Internal Use TCS Internal

Internal Use

Being Agile
“Having the ability to create and respond to
change. A way of dealing with, and ultimately
succeeding in, an uncertain and turbulent
environment.”
AgileAlliance.org

Source: https://www.agilealliance.org/agile101/

Internal Use 9 TCS Internal

Internal Use
What is Agile?

Allows you to continuously delight the customer

Enables you to respond effectively to changes in your

environment

Permits you to mitigate risks by pushing you to fail faster

Encourages a continuous learning mindset

Lets you integrate ecosystems and generate value

Enhances the productivity and cohesiveness of teams

Internal Use 10 TCS Internal

Internal Use
Agile Manifesto

Source: https://agilemanifesto.org
Internal Use 11 TCS Internal
Internal Use
Agile Manifesto
We are uncovering better ways of developing ‘software
offerings by doing it and
helping others do it. Through this work we have come to value:

Individuals and interactions OVER Processes and tools

Working software OVER Comprehensive documentation

Customer Satisfaction OVER Contract negotiation

Responding to change OVER Following a plan

That is, while there is value in the items on the right,

we value the items on the left more.

Internal Use 12 TCS Internal

Internal Use

Internal Use 13 TCS Internal

Internal Use
It’s not the strongest of the species that survive, nor the most intelligent,
but the ones most responsive to change

Internal Use 14
Internal Use

TCS’ RESPONSE TO THE

NEED FOR CHANGE

Internal Use 15 TCS Internal

Internal Use
Our purpose statement -

Building a greater future through innovation and collective knowledge

L Leading Change

I Integrity
TCS VALUES
R Respect for Individual

E Excellence

L Learning and Sharing

Internal Use 16 TCS Internal

Internal Use
Business 4.0 – Pillars and Behaviors

Internal Use 17 TCS Internal

Internal Use

Fixed vs Growth Mindset (an Agile Mindset)

Internal Use 18 TCS Internal

Internal Use

Attention please!

Let’s watch a brief video (10 minutes)

A Brief History of Lean & Agile (Barry L Smith)

Courtesy of: Barry L Smith, CEO Unify Consulting

https://vimeo.com/543180832

https://www.linkedin.com/feed/update/urn:li:activity:67896376
99889438720/ - subtitled

Internal Use TCS Internal

Internal Use

The Heart of
Agile Essentials

Alistair Cockburn
Agile Manifesto Co-author,
Heart of Agile Founder

https://heartofagile.com

Internal Use 20
Internal Use

The Heart of
Agile Essentials

Internal Use 21
Internal Use

The Heart of
Agile Essentials

Internal Use 22
Internal Use

The Heart of
Agile Essentials

Internal Use 23
Internal Use

The Heart of
Agile Essentials

Internal Use 24
Internal Use

The Heart of
Agile Essentials

Internal Use 25
Internal Use

Q&A

Internal Use 26 TCS Internal

Internal Use

Scrum Fundamentals
- Culture Overview
• Introduction to Scrum, Fundamentals, and an initial
Overview
• Scrum Origins – History of Scrum, the Foundation
of Scrum
• Scrum vs. Waterfall, Key Differences between
Scrum and others, Scrum added value
• Scrum Pillars and Principles
• Scrum Values and Scrum Resources
• Scrum Rituals and Roles
• Scrum Commitments
December 2022

Internal Use TCS Internal

Internal Use
Origins of Scrum

• Japanese and rugby roots

• Introduced initially in the 80’s by Hirotaka Takeuchi and
Ikujiro Nonaka
• In the 90’s Ken Schwaber and Jeff Sutherland structured
the Scrum framework
• Sutherland & Schwaber helped to write the
Agile Manifesto in 2001
• They are co-authors of the definitive Scrum Guide
(public document initially released in 2009)
• Schwaber co-founded the ScrumAlliance.org and later
founded Scrum.org

Internal Use 28 TCS Internal

Internal Use
What is Scrum?

• A framework to solve problems & deliver value

• An Agile “methodology” (as per the definition in the
2020 Scrum Guide ”it’s a lightweight framework”)
• The most popular Agile method for delivering
projects
• An iterative, time-boxed approach
• Incremental delivery with continuous improvement
• Customer centric, focus on value, deliver often &
quickly
• Adaptive, fast, flexible Courtesy: O’Reilly Learning

Internal Use 29 TCS Internal

Internal Use
What is Scrum? (Definition as per The Scrum Guide 2020)

• Scrum is a lightweight framework that helps

people, teams and organizations generate value
through adaptive solutions for complex problems.
• In a nutshell, Scrum requires a Scrum Master to
foster an environment where:
1. A Product Owner orders the work for a complex
problem into a Product Backlog.
2. The Scrum Team turns a selection of the work into
an Increment of value during a Sprint.
3. The Scrum Team and its stakeholders inspect the
results and adjust for the next Sprint. Courtesy: O’Reilly Learning

4. Repeat

Internal Use 30 TCS Internal

Internal Use

Internal Use 31 TCS Internal

Internal Use
Scrum vs. Waterfall

Scrum: Waterfall:
• Quick delivery with a focus on value; • Longer term delivery with a focus on
customer centric requirements; business centric
• Iterative • Sequential
• Scope is variable & negotiable • Scope is fixed
• Continuous reflection for improvement • Lessons learned at the end of the project
• Frequent testing • Testing during a phase
• Roles blur • People in defined roles

Internal Use 32 TCS Internal

Internal Use
Scrum vs. Waterfall

Waterfall: Sequential

Scrum: Iterative, Incremental

Courtesy: O’Reilly Learning

Scrum employs an iterative, incremental approach to optimize predictability and to control risk.

Scrum engages groups of people who collectively have all the skills and expertise to do the work and share
or acquire such skills as needed. (Source: The Scrum Guide 2020)

Internal Use 33 TCS Internal

Internal Use
Scrum Pillars and Scrum Principles – a Solid Foundation of Scrum as a Culture

Transparency Inspection Adaptation

Significant aspects of the process Scrum artifacts are frequently When there’s variation vs. desired
must be visible for the outcome inspected to review progress and and acceptable outcomes
variances adjustments are made

Scrum Pillars
3 pillars of empiricism

Scrum Theory is founded on empiricism and lean thinking.

Internal Use 34 TCS Internal

Internal Use
Scrum Pillars and Scrum Principles – a Solid Foundation of Scrum as a Culture

Management

Courtesy: O’Reilly Learning

https://www.scrumstudy.com/whyscrum/scrum-principles

Scrum Principles

Internal Use 35 TCS Internal

Internal Use
Scrum and Others
Courtesy: O’Reilly Learning

* DAD
* LeSS
* Spotify

Lighter Agile approaches More extensive Agile

approaches

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed.
Lean thinking reduces waste and focuses on the essentials. (Source: The Scrum Guide 2020)

Internal Use 36 TCS Internal

Internal Use

• Commitment
Scrum Values –
• Courage
the Essence of
Scrum as a • Focus
Culture • Openness
• Respect

Internal Use 37 TCS Internal

Internal Use

OPENNESS
Scrum Values –
C OURAGE
the Essence of
Scrum as a RESPECT
Culture FOC U S
COMMITMENT
The Scrum Team commits to achieving its goals and to supporting each other.

Internal Use 38 TCS Internal

Internal Use
Scrum Accountabilities (Roles)
Courtesy: O’Reilly Learning

DEVELOPERS

Scrum Team Accountabilities (Roles)

Internal Use 39 TCS Internal

Internal Use
Scrum Accountabilities (Roles)

Scrum Master
• A facilitator • Helps team to reach it goals
• Leads, supports, guides and helps • Ensure adherence to
• Removes roadblocks and impediments Scrum Framework and rituals
• Leads daily stand-ups • Servant-Leader
(Situational-approach Leader)
• Keeps the team focused on goals & Courtesy: O’Reilly Learning
objectives • Coaches team
• Keeps time on track • Works closely with Product Owner
• Not a traditional Team Lead or Project
Manager
• Facilitates key sessions and encourages
team to improve

Internal Use 40 TCS Internal

Internal Use
Scrum Accountabilities (Roles)

Product Owner
• Represents the customer and • Bridge between the team and
stakeholders stakeholder
• Defines the product in customer • Should be different to the
centric terms Scrum Master
• Owns the product backlog • Steers direction of what is
being delivered Courtesy: O’Reilly Learning

• Prioritizes based on importance and

dependencies • Negotiates priorities, scope, funding, and
schedule
• A Scrum Team should have only one
Product Owner
• A person can be the Product Owner for
more than one team

Internal Use 41 TCS Internal

Internal Use
Scrum Accountabilities (Roles)

Developers
• Responsible for delivering “shippable” • Instills quality by adhering to
increments every sprint a Definition of Done
• Typically, 10 or fewer team members • Adapts their plan each day DEVELOPERS
who carry out tasks like: toward the Sprint Goal
• Analysis, design, development, • Holds each other accountable
testing, just enough docs., etc. as professionals Courtesy: O’Reilly Learning

• Empowered
• Self-managed
• Accountable for creating a plan for the
Sprint, the Sprint Backlog

Internal Use 42 TCS Internal

Internal Use
Scrum Master Services Provided to Other Roles

To the Product Owner

• Ensuring that goals, scope, and product domain are understood by

everyone Courtesy: Edureka.co

• Finding techniques for effective Product Backlog management

• Helping the Scrum Team to understand the need for concise and clear Product
Backlog
• Understanding Product Planning in an empirical environment
• Ensuring the Product Owner knows how to arrange the Product Backlog to
maximize the value
• Understanding and practicing agility
• Facilitating Scrum events

Internal Use 43 TCS Internal

Internal Use
Scrum Master Services Provided to Other Roles

To Developers

• Coaching Developers in self-organization and cross-functionality

• Helping Developers to create high-value products
Courtesy: Edureka.co

• Removing impediments to accelerate Team’s progress

• Facilitating Scrum events as requested or needed
• Coaching Developers in organizational environment in which Scrum is not yet
fully adopted and understood

Internal Use 44 TCS Internal

Internal Use
Scrum Master Services Provided to Other Roles

To the Organization

• Leading and coaching the organization in its Scrum adoption

• Planning Scrum implementations within the organization
Courtesy: Edureka.co

• Helping employees and stakeholders to understand and enact Scrum and

empirical product development
• Causing change that increases the productivity of the Scrum Team
• Working with other Scrum Masters to increase the effectiveness of the
application of Scrum in the organization

Internal Use 45 TCS Internal

Internal Use
Scrum Events (Rituals, Ceremonies)

Scrum Events:
1. The Sprint (the container)
2. Sprint Planning
3. Daily Scrum
4. Sprint Review
5. Sprint Retrospectives

• Backlog refinement
/ grooming

Scrum combines four formal events for inspection and adaptation within a containing event, the Sprint. These
events work because they implement the empirical Scrum pillars of transparency, inspection, and adaptation
(Source: The Scrum Guide 2020)

Internal Use 46 TCS Internal

Internal Use
Sprint (the container)
• Sprints are the heartbeat of Scrum, where ideas are
turned into value.
• They are fixed length container of all the events of one
month or less to create consistency.
• All the work necessary to achieve the Product Goal,
including Sprint Planning, Daily Scrums, Sprint Review,
and Sprint Retrospective, happens within Sprints.
• No changes are made that would endanger the Sprint
Goal;
• The Product Backlog is refined as needed
• If there is Scope change, it may be clarified and
renegotiated with the Product Owner as more is learned.
• Note: A Sprint could be cancelled if the Sprint
Goal becomes obsolete. Only the Product
Owner has the authority to cancel the Sprint.

Internal Use 47 TCS Internal

Internal Use
Sprint Planning
Courtesy: Scrum.org

• Lays out the work to be performed for the Sprint

• Ensures the Product Backlog has been refined to an appropriate level

of detail

• The Product Owner should have ordered the work on the Product
Backlog and have a general idea of how to negotiate a valuable
Sprint Goal with Developers.

• Developers should have an idea of how much work they believe

they can take on by using their experience with previous Sprints

• The Sprint Goal, the Product Backlog items selected for the Sprint,
plus the plan for delivering them are together referred to as the
Sprint Backlog.

• Timeboxed to a maximum of 8 hours for a one-month Sprint. For

shorter Sprints, the event is usually shorter.

Internal Use 48 TCS Internal

Internal Use
Sprint Planning (Product Backlog Refinement)
Courtesy: Scrum.org

• Refinement is NOT a formal event but an ongoing activity - the process of

adding detail, order, and estimates to Product Backlog Items such as Epics
or User Stories
• Scrum Teams decide how often to do this (good idea to make it a daily
routine)
• Refinement shouldn’t take more than 10% of a team’s total time during a
Sprint
• Product Backlog is refined in a timely manner so that Sprint Planning can
occur without impediment(s)
• Helps to examine each PBI and discuss its scope, and the acceptance
criteria that will be necessary for its completion
• Each item will be estimated using a technique such as Planning Poker, T-
Shirt Sizing, or Ideal days/hours

Internal Use 49 TCS Internal

Internal Use
Daily Scrum

• Is an event for the Developers of the Scrum Team Courtesy: Scrum.org

• Takes place every working day, at the same time, to

reduce complexity
• The Developers meet and plan what they will do in the next
24 hours to bring them closer to the Sprint Goal
• If the Product Owner or Scrum Master are actively working on
items in the Sprint Backlog, they participate as Developers.

• Each team member should be able to account for:

✓ What they did yesterday to help the team meet the Sprint Goal
✓ What they intend to do today to help the team meet the Sprint Goal
✓ Any impediments which are getting in their way

✓ It is timeboxed and should never take more than 15 minutes

Internal Use 50 TCS Internal

Internal Use
Sprint Review

• To inspect the outcome of the Sprint and determine future

Courtesy: Scrum.org

adaptations
• The Scrum Team presents a valuable increment of their work to
demonstrate the progress towards the Product Goal to the Product
Owner and any invited stakeholders
• The Product Owner explains how well the product is performing, to
get feedback first-hand
• Used to draw any lessons to improve the Product Backlog further
• Note: If any work has not been completed, for whatever reason,
it will also be reviewed and re-estimated on the Product Backlog
• It is timeboxed to a maximum of 4 hours for a one-month Sprint

Internal Use 51 TCS Internal

Internal Use
Sprint Retrospective
Courtesy: Scrum.org

• To plan ways to increase quality and effectiveness

• The Scrum Team inspects how the last Sprint went

• Individuals, Interactions, Processes & tools and DoD

• The Scrum Team discusses and learn about what went well during
the Sprint (problems encountered, if were or were not solved)

• To identity the most helpful changes to improve its effectiveness, and

the most impactful improvements to be addressed as soon as
possible

• It concludes the Sprint. It is timeboxed to a maximum of 3 hours

for a one-month Sprint.

Internal Use 52 TCS Internal

Internal Use
Scrum Artifacts and their Commitments

Courtesy: Scrum.org
• Scrum artifacts represent work or value
• Designed to maximize transparency of key information
• Each artifact contains a commitment to ensure it provides
information that enhances transparency and focus against which
progress can be measured:
• For the Product Backlog it is the Product Goal
• For the Sprint Backlog it is the Sprint Goal
• For the Increment it is the Definition of Done
• Commitments exist to reinforce empiricism and the Scrum values
for the Scrum Team and their stakeholders

Internal Use 53 TCS Internal

 Image: https://www.conceptdraw.com/news/scrum-workflow-solution
TCS Internal
54
Internal Use

Internal Use
Internal Use
Dos and Don’t’s – Scrum Anti-patterns

* Skipping testing
* Not my job!! * Taking partial credit for work not
* Technical debt completed
* Poor coding practice * Comparing teams using their velocity
* No code reviews * Extending the sprint
* No source code testing * Lot of work to do so let’s skip
retrospective!!
* Scrum master also as a product owner
* Assuming time scope and resources are
* Scrum master given testing development roles
fixed always
* Moving team members
* Management not interested in adopting
* Oh, its agile so no documentation!! agile
* No DOD (Definition of Done) * Security and quality assurance happens at
the end

Internal Use 55 TCS Internal

Internal Use
User Stories

• User Stories are short descriptions of a small piece of desired functionality, written in the user’s
language

• User stories are value-centric.

• The recommended form of expression is the user-voice form, as follows:

As a (user role), I want to (activity), so that (business value)

As a driver, I want to limit As a driver, I want to get a As the Finance Department,

the amount of money receipt after fueling so that we want to print receipts only
before I fuel so that I can I can expense the for drivers who request them
control my expenditure purchase. so that we save on paper

Source: scaledagile.com

Internal Use 56 TCS Internal

Internal Use
How to write a User Story

“As a <type of user>, I want <some goal>

so that <some reason>”
“As a <User of Medi app>, I want <list of medical stores nearby>
so that <I can buy my medicines>”

“As a <User of ULTIMATIX>, I want <LOGIN >

so that <GO TO MY HOME PAGE>”

Does the user story follow the INVEST MODEL?

Internal Use 57 TCS Internal

Internal Use
INVEST in a good Story

I Independent Write Stories that can be developed separately

N Negotiable Write Stories in which scope can be negotiated

V Valuable Write Stories that are valuable to the Customer

E Estimable Write Stories that can be estimated

S Small Write Stories that can fit in an Iteration

T Testable Write Stories that are testable

Source: scaledagile.com

Internal Use 58 TCS Internal

Internal Use
User Story Card Example

Internal Use 59 TCS Internal

Internal Use
Suggested Reading

“User Story Mapping: Discover the Whole “User Stories Applied: For Agile Software
Story, Build the Right Product” Jeff Patton Development” Mike Cohn

Internal Use 60 TCS Internal

Internal Use
Suggested Reading

Historias de usuario: Una visión pragmática

(Spanish Edition) Lucho Salazar & Jorge Abad

Jorge Hernan Abad Londoño

Enterprise Agile Coach, Agile Transformation Lead for TCS LATAM
https://leccionesaprendidas.info

Internal Use 61 TCS Internal

Internal Use

Q&A

Internal Use 62 TCS Internal

Internal Use

Getting ready for

PSM-I examination
Scrum Guide 2020
Scrum.org – Open Assessment
Scrum Quiz
Mikhail Lapshin Quiz

December 2022

Internal Use TCS Internal

Internal Use
Mandatory Reading

https://scrumguides.org/scrum-guide.html

Internal Use 64 TCS Internal

Internal Use
Suggested Reading for PSM-I

https://www.scrum.org/pathway/scrum-master

Internal Use 65 TCS Internal

Internal Use
Testing Your Knowledge for PSM-I

https://www.scrum.org/open-assessments/scrum-open

Internal Use 66 TCS Internal

Internal Use
Testing Your Knowledge for PSM-I

http://scrumquiz.org/#/

Internal Use 67 TCS Internal

Internal Use
Testing Your Knowledge for PSM-I

https://mlapshin.com/index.php/scrum-quizzes/sm-learning-mode/

Internal Use 68 TCS Internal

Internal Use
References - useful links to keep learning
Websites for research: Web articles and videos in chronological order:

https://agilemanifesto.org • AgileAlliance – resources videos Modern-agile (2016)

http://scrumquiz.org/#/scrum-master-practice-test • Getting to the Heart of Agile by Alistair Cockburn, InstitutLeanFrance (2019)
https://theagilerevolution.com • Heart of Agile talk with Sole Pinter in Spanish, Latam Agiles2020 (2020)
https://www.business4.tcs.com • Brice Beard – APAC Head Global Markets Execution Technology, Business Agility
https://www.heartofagile.com Champion - Linkedin Profile (2021)
https://www.heartofagile.academy • Your Organization journey Becoming Agile - Agile Manifesto Mindset, Brice Beard
http://www.lecciones-aprendidas.info/ (2021)
https://www.linkedin.com • Barry L Smith, Lean-agile Leader – Linkedin Profile (2021)
https://mlapshin.com/index.php/scrum-quizzes/ • Agile - Barry L Smith, Unify Consulting (2021)
https://www.tmtctata.com/learning-latitudes
https://www.tcs.com/about-us Special Thanks to :
https://www.tcs.com/perspectives
https://learning.oreilly.com • Jorge H. Abad Londoño, Head of Agility for TCS in Latin America | Regional Agile
https://vimeo.com/543180832 Coach | Enterprise Agile Coach | SPC 5.0, RTE 5.1, TKP, KSD, KSM | Trainer
Management 3.0 | Speaker | Author – TCS Colombia
Images Courtesy of: • Blog: Lecciones Aprendidas en Desarrollo de Software, Jorge Abad y Lucho Salazar
Alistair Cockburn - heartofagile.com
Mauricio Rubio – learning.oreilly.com
Edureka – edureka.co TCS Agile Coffee Connect
Scrum.org https://tcsglobal.webex.com/meet/Biliana.Draganova

Internal Use 69 TCS Internal

Internal Use

Thank you

Copyright
Internal Use© 2021 Tata Consultancy Services Limited