Agile software development with Scrum.

1. SCRUM 101+
Mar 2020

2. Cuong Nguyen (Michael)
Project Manager /
Scrum Master
• 10+ YOE in software development
• 6+ YOE in project management as Project
Manager and Scrum Master
• PMI-ACP certified
• PMI-PMP certified
• Scrum.org Scaled Professional Scrum
certified
• Scrum.org PSM1 certified
• Scrum.org PSPO1 certified
About Me

3. Before we start …

4. Agenda
Scrum on a Page
Scrum Team
Scrum Events
Scrum Artifacts

5. https://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp
Different
Ways to Build
a Product

6. Scrum (n)
A framework within which people can
address complex adaptive
problems, while productively and
creatively delivering products of the
highest possible value.
5 Values
Commitment
Courage
Focus
Openness
Respect
3 Pillars
Transparency
Inspection
Adaptation
Roles
Product Owner
Scrum Master
Development Team
Events
Sprint Planning
Daily Scrum
Sprint Review
Sprint Retrospective
Backlog Refinement
Artifacts
Product Backlog
Sprint Backlog
Impediment Backlog
Sprint Burndown Chart
Product Increment
https://www.scrum.org/resources/what-is-scrum

7. Scrum Team

8. Product
Owner
Maximizing the value of
the work of the
Development Team.
Represent customers and stakeholders (VOC)
Define features of the product (user stories)
Prioritize product backlog
Making trade-off between Scope & Schedule
Accept / Reject work results
We are going to
change the world with
this application!

9. Scrum
Master
Ensuring the Scrum
process is understood
and followed.
A “servant leader”
Remove impediments
Facilitate Scrum events
Coach the team to their best performance
Protect the team from external interference
Are you guys hungry?
Let me get something
for you to eat.

10. Development
Team
Turning Product Backlog
into increments of
potentially shippable
product.
“Do the work”
Typically 3 to 9 members
Cross-functional – with all skills needed to
create product increment
Self-organizing – choose how best to
accomplish the work
We will transform your
crazy vision into reality!

11. Scrum Events

12. Sprint
Sprint
“Done”, usable and potentially releasable product increment is
created.
Consistent duration throughout development effort.
A new Sprint starts immediately after the conclusion of the
previous Sprint.
During sprint: No changes to Sprint Goal; Quality goal not
decrease; Scope may be re-negotiated.
Usually 2 weeks (up to 1 month)

13. Sprint
Sprint Planning
Planning
Product Owner to present top priority Product Backlog to Team.
Team to select Product Backlog to be developed.
Sprint Goal is crafted.
Development Team to discuss on how to complete user stories
(solutioning, estimating, task breakdown …)
Sprint Goal is finalized (Everyone commits to the sprint goal).
WHAT will be done (2 hours)
HOW to build selected items (2 hours)

14. Daily
Daily Scrum
Scrum
Development Team to synchronize activities and create a plan
for the next 24 hours.
Before this meeting, what did you do?
After this meeting, what will you do?
Are there any problems / obstacles / impediments in your way?
Stand-up daily (15 minutes)
3 questions

15. Sprint
Sprint Review
Review
The team demonstrates the work that is done to Product Owner
and stakeholders.
Feedback is discussed and collected.
At the end of the Sprint (2 hours)

16. Sprint
Sprint
Retrospective
Retrospective
After Sprint Review (1.5 hours)
What worked well last Sprint that we should continue doing?
What didn’t work well last Sprint that we should stop doing?
What should we start doing?

17. Backlog
Backlog
Refinement
Refinement
Maximum 10% of team capacity.
Update product backlog items by adding details, splitting large items,
estimating and prioritizing.
Middle of current Sprint (~2 hours)

18. Scrum Artifacts

19. Product Backlog
An ordered list (by
priority) of everything
(user stories, spikes,
bugs ...) that might be
needed in the product.

20. Sprint Backlog
Set of Product Backlog
Items selected for the
Sprint, plus a plan
for delivering the Product
Increment.

21. Impediment
Backlog
Items that block the team
from doing their works.

22. Sprint Burndown
Chart
To track how much work
(story points, hours ...)
remains in a Sprint
Backlog.

23. Product Increment
(Potentially Shippable Product)
Sum of all the Product
Backlog Items completed
during a Sprint and the
value of the Increments
of all previous Sprints.

24. Some more
Concepts
Velocity vs Capacity
User Story vs Spike
Story Point estimation / Planning Poker
Definition of Done
Definition of Ready
Time-boxed

25. Before we end …

26. Scrum (n)
A framework within which people can
address complex adaptive
problems, while productively and
creatively delivering products of the
highest possible value.
5 Values
Commitment
Courage
Focus
Openness
Respect
3 Pillars
Transparency
Inspection
Adaptation
Roles
Product Owner
Scrum Master
Development Team
Events
Sprint Planning
Daily Scrum
Sprint Review
Sprint Retrospective
Backlog Refinement
Artifacts
Product Backlog
Sprint Backlog
Impediment Backlog
Sprint Burndown Chart
Product Increment
https://www.scrum.org/resources/what-is-scrum