Scrum

Page 3 & 4 7, 9--- IMportant

---------------------------------------------------
1. INTRO

Product Backlog - All available task for the projevt (to do list of the project)
Sprint - 1 month or less to create something valuable for clients
Sprint Backlog -

------------------------------------------------------------------------------------------------------------------------
2. Agile Overview

Values (4)
Individuals and Interactions over Process and Tools
Working software over Comprehensive documentation
Customer collaboration over Contract negotiation
Responding to Change over Following a plan

Principles (12)

------------------------------------------------------------------------------------------------------------------------
3. Scrum Overview
Scrum is a framework
Empirical - Data driven
Lean - Reduce wastage

3 pillars of Scrum ----> Transperancy (To Do) ---- Inspection (Outcomes) ----- Adaptation
(Feedback)
Reduce Risk and Increased Predictablity to clients

Scrum Framework (Simple Guidelines)

3 Roles
5 Events
3 Artifacts

3 roles
Product Owner
Developer --- People working on the working functionality
Scrum Master ---

5 Inspect and Adapt Events

Sprint
Sprint Planning
Daily Scrum
Sprint review - with stakeholders for gathering feedback
Sprint Retrospective - only with 3 roles (team reflection based on the feedback)

5 Scrum Values
Courage
Focus
Commitment
Respect
Openness

3 Artifacts
Product Backlog
Sprint Backlog
Increment

1 Inspect and Adapt Activity

Product backlog refinement ----- Most pref time is to do this in middle of the sprint
------------------------------------------------------------------------------------------------------------------------4.
Product Backlog - product owner is responsible for maintaining this artifact

What all will be added

1. New requests
2. Defects
3. Feedback
4. Technical Debt
5. Maintenance

Product Backlog Items / User Stories

DEEP
Detailed appropriately (more granular items are added in future as they near the top near
top)
Emergent (items/details may be added, removed, reordered and refined over time)
Estimated by Developers
Prioritized prior to Sprint Planning
------------------------------------------------------------------------------------------------------------------------
5. Technical Debt
To DO: Pg 18 to 21
------------------------------------------------------------------------------------------------------------------------
6. Scrum Roles
Product owner
Anybody can edit but PO only prioritises
decides what and why? of deliverables
review of demo with PO in middle of sprint
PO has authority to cancel sprint
cision, roadmap and budget
decides on rel dates
Not do - How (only from dev)
PO is a single person not a grp or comittee
Dont push/dictate
And no proxy (A PO with availablity and no authority OR less avalilablity with full authority)

Developers
No sub teams
self managed and cross functional
Generalists and Specialists
Work on the increament of every sprint

Definition of done - dev will adhere to this dod

Estimate
Sign up for work
Decide on HOW?
Should attend all scrum meetings proactively
Sync with PO and scrum master

Scrum Master
1. --> Servent Leaders - serve the team no authority just guide to reach the goal not how
when what
creating a environment where team is productive
lead through influence
no authority on any tm
encouraging guiding and facilitating

2. Change Agent
Teach --> Unlearn the traditional and help them learn new ascpects of Scrum
Coach --> If the team has already achieved scrum then coach them accordingly to situations

3. Impediment Remover
Blockers remover for team members

4. shield their team from interactions - help them only stay focussed on the development

5. Facilitate - make it easy and possible and assist

Help the team work cohesively to achieve a goal
Encourage experimentation
Adress Issues
Access to Decision Making

What not to do
---> not ur teams note taker
---> not tool updater
--->

IMP ACTIVITY – How SM adds value to the project

Best Example – Even the best sports person has their coach till their last game

Adv of scrum
pbi --------------------------------------------------------------------- Value
Daily issues of Team

Max 2 teams as a scrum master

Issues - no dedicated Team members
PM Role - Product owners or Scrum Masters
------------------------------------------------------------------------------------------------------------------------

DAY 2
------------------------------------------------------------------------------------------------------------------------

7. Sprint Events
1. Sprint Pg 34
Sprint Length: How long can we lock in our scope?
How long it takes to develop a working increment?
Some teams experiment and rethink abt the length of the sprint in the retrospective
2. Sprint Planning
PO, SM, D
Max 8hrs - 1m sprint
Confirmation with PO on priorities and creating sprint goal and sprint backlog
Past performance - how much userstories are we able to complete without burining down
Projected Capacity - How much time on meetings for what and where r we meeting, Team
availablity (timeoffs, holidays), resources
Definition of Done -
Why(Sprint Goal) What(Product Backlog) and How (Sprint Backlog) in sprint planning
Only if the cross functional dependencies are affecting the team, inviting people, facilitating
SM is invloved else developers can individually take them
SM is not a bridge anyone can approach anyone

3. Daily Scrum
Max - 15min
PO, SM and Dev
Preffbly - Same Time Same Place
What work on next 24hrs, remove impediments and what work completed yesterday
3 ques / Projecting the Sprint Backlog and discussing
- What have I been working on since we last met
- What am I planning to work on until we meet again tomorrow
- Do I have any impediments that will stop us from achieving the Sprint Goal
Main Aim of Daily Scrum - Make developers self organised (neither the PO or SM is
facilitating the Daily Scrum. It is a sync up b/w the developers to make them realise if this
sprint is on track, Be self organised to take up tasks once you are done with the work)
Why?
Focussed, Red Flag, Openness, Next 24hrs, and Team Bonding (understand each other
strength and weakness way of working)

4. Sprint Review
Stakeholders/PO / SM/ Dev
Demonstrate results and Get feedback from StakeHolders
max 4hrs - sprint length 1 month
facilitated by PO (Anchor) & Dev(Demo), StakeH provide feedback, SM only to observe
Dev 1/2 vol - to take feedbck list - convert it to PBI and put it on Product Backlog

5. Sprint Retrospective
SM PO and Dev
Reflect on the Sprint outcome - What went right, Can we do better
3hrs for 1mon, 90min for 2 week sprint
After sprint review - Last day of the sprint

6. Product Backlog Refinement

Twice a sprint (Preff) / Ongoing event

Preparing PBIs for planning Sprints - To add clarity to existing PBI's, Add/Remove Tickets as
Goals Adapt, Facilitates next sprint plan and Estimations, Create an invitation link for next
sprint guests
Ensure product backlog items are appropriate, detailed, and prioritized according to their
value to the project or customer.
Ensure the backlog contains relevant items and that those at the top are ready for delivery.
Backlog is understood as a dynamic body of information that evolves over time.

Activities During Refinement:

Remove user stories that are no longer relevant.
Create new user stories based on newly discovered needs.
Reassessing the relative priority of stories.
Assigning estimates to stories.
Correcting estimates based on new information.
Splitting high-priority but coarse-grained user stories.
Scope Management: Backlog refinement helps manage scope creep, preventing
unnecessary additions that could lead to schedule and budget overruns.

PO an Dev (Optional SM)

No set time should be facilitated by PO, Suggestion was 2 small sessions every 3 days but
adjusting as needed
Daily or continuous refinement- Teams determine frequency when to meet.
8. Scrum Artifacts
Just read pg 10 in Scrum Guide

9. Definition Of DOne - integration test and quality standards

Created by entire scrum team
Created during scrum planning
Reviwed in Sprint retrospective
All quality checks/testing is listed
Is same for all tasks

10. User Stories – refer slides

Dec of a feature from end user perspective

Card/Conversation/Confirmation

Acceptance criteria - Test criteria test sheet

Written in PO's pers business pers
For building the right thing
Unique for every user story
After this confirm DoD is done

11. Estimation

Estimation is done in Product Backlog Refinement

What techniques, how much time

Sizing techniques

1. T Shirt Sizing

XS - 1/2 day
S - 1 Day
M - 2-4 days
L - A week
XL- Week plus

Can be changed - but everyone should be speaking the same lang (Small task means it will
take 1 day acc to everyone in the team)

2. Planning Poker - Story points - Fibonocci sereies popular way of calculating story points
Burdown chart is plotted against story points - to predict velocity in future

XS - 1
S-2
M-3
L-5
XL - 8

Velocity chart

12. Setup Scrum

1 or 2 weeks to plan how to implement Scrum
Refer Docs given in Email to do so
After sprint Planning send sprint review to all key stakeholders – to help set expectations

Final Email

CONGRATULATIONS on completing the work to qualify for your CSM!

Your feedback adds great value to my classes and helps me improve

them for future participants. It’s all about Inspect and Adapt!
I would appreciate it if you can please write a recommendation on
LinkedIn about your experience and what was valuable to you!

Do you hold the PMP Certification? If YES, then please find below
the process to claim your PDUs, if NO please skip this part:

CSM class earns you 16 PDUs, to claim them:

1. Login to your PMI account

2. On the PMI dashboard, type in "Scrum Alliance" as the
organization name, you will not find it in the dropdown menu.
3. Enter the date of the class attended
4. For PDUs claimed: Split the hours evenly between Business
Acumen and Power Skills

5. Agree and submit

Lastly here are some links to videos and other useful (and in some cases
entertaining) content:

Videos:

- Product Owner in a Nutshell: https://www.youtube.com/watch?

v=502ILHjX9EE&t=26s
- Backwards Bicycle: https://www.youtube.com/watch?
v=MFzDaBzBlL0&t=28s
- The "Wrong" Way to do Agile: https://www.youtube.com/watch?
v=FJezcyKno5k&index=4&list=PLaD4FvsFdarQytrGAmCo2qW_rAWcfBKeV)
- Sh*t Bad Scrum Masters Say: https://www.youtube.com/watch?
v=GGbsgs611MM
- Nordstrom Innovation Lab: https://www.youtube.com/watch?
v=2NFH3VC6LNs
- What Motivates Us: https://www.youtube.com/watch?
v=u6XAPnuFjJc&t=3s
- Turn the Ship around: https://www.youtube.com/watch?
v=OqmdLcyES_Q&t=89s
- Start with Why: https://www.youtube.com/watch?v=u4ZoJKF_VuA
- Generalist/Specialist: https://youtu.be/wCPbPMRNnvk

--------------------------------------------------------

My Blogs:

Get in FRONT of the Daily Scrum:

https://www.linkedin.com/feed/update/urn:li:activity:7034545963964805120/
How to Engage Team Members in Scrum Events:
https://www.linkedin.com/feed/update/urn:li:activity:6732319452911702017/

Scrum Masters Help Build Good Habits:

https://www.linkedin.com/feed/update/urn:li:activity:6816069559141863424/

Improving Communication for Global Teams:

https://www.linkedin.com/feed/update/urn:li:activity:6921843404356161536/

--------------------------------------------------------

Case Studies:

- Technical Debt impact at Southwest Airlines: https://rb.gy/qop2uv

- Scrum in
Church: http://jeffsutherland.org/scrum/SutherlandScruminChurchAgile20
09.pdf
- Scrum at Sephora: https://medium.com/sephoralife/how-sephora-
teams-came-together-to-create-an-agile-task-force-3d937dd590ca
- Agile/Scrum at FBI: https://www.informationweek.com/government/fbi-
s-sentinel-project-5-lessons-learned
- Agile at Tesla: https://280group.com/product-management-blog/tesla-
agile-development/

--------------------------------------------------------

Additional Reading Materials:

- The Agile Manifesto: http://agilemanifesto.org/

- High Performing Teams: https://hbr.org/2017/08/high-performing-
teams-need-psychological-safety-heres-how-to-create-it
- Agile Contracts: https://www.scruminc.com/agile-contracts-money-for-
nothing-and/
- User Story Mapping: https://storiesonboard.com/user-story-mapping-
intro.html
- Collection of Good articles: https://openpracticelibrary.com

--------------------------------------------------------

Materials to work with your teams:

Create Definition of Done:

https://www.mitchlacey.com/intro-to-agile/scrum/definition-of-done

Online Retrospective Tools:

https://funretro.io/
https://www.goreflect.com/

--------------------------------------------------------
Some helpful Metrics:
https://rgalen.com/agile-training-news/2014/4/22/2-dozen-weird-agile-
metrics-ideas
http://www.andycleff.com/2019/09/understanding-agile-team-metrics/

--------------------------------------------------------

My favorite books on Culture Change and Servant Leadership:

Switch: How to Change Things When Change Is Hard -

https://www.amazon.com/dp/B0030DHPGQ/ref=dp-kindle-redirect?
_encoding=UTF8&btkr=1

Servant Leadership: A Journey into the Nature of Legitimate

Power and Greatness -
https://www.amazon.com/Servant-Leadership-Legitimate-Greatness-
Anniversary/dp/0809105543

Leaders Eat Last: Why Some Teams Pull Together and Others
Don't -
https://www.amazon.com/Leaders-Eat-Last-Together-Others/dp/15918453
27