This document discusses Agile project management techniques. It outlines the five Scrum rituals: storytime, sprint planning, daily standup, sprint review, and retrospective. It provides tips for daily standups, including sticking to a script, standing, meeting at the same time daily, and having separate Scrum of Scrums meetings for multiple teams. It also covers user story format and acceptance criteria format, noting acceptance criteria should test functionality and include error states. Finally, it asks if the reader has experienced Agile implementations and what has worked well and been hardest to incorporate.

1. Welcome to
Why Agile Falls Apart

2. Charis Loveland
Co-founder, ML Assist
Product manager in AI/ML,
design thinker, metrics-driven leader
@Mozilla, General Assembly, formerly Microsoft,
Rue La La, EMC, SAP
@charislovestech
LinkedIn

4. Time to Dispel the Myths...

6. 5 Scrum Rituals
1. Storytime
2. Sprint Planning
3. Daily Stand Up
4. Sprint Review
5. Retrospective
Sprint Cycle
Daily
Standup
Sprint
Review
Sprint
Planning
Testing and
Development
Product Backlog
Sprint Backlog
Releasable Product
Release Product

10. Tips for Your Daily Standup
✓ The daily standup meeting is meant to be self-regulating. The Scrum Master should not
have to ‘call upon’ team members to speak.
✓ Other team members can attend like the Product Owner
✓ Stick to the script. Team members will be less likely to stray. Take all other discussions
offline.
✓ Insist on standing. The idea is that the discomfort of standing will force everyone to stay
focused.
✓ Meet at the same time every morning. Choose a time such as 8:03 AM (not on an hour, half
or quarter). This helps people to be on time. Begin exactly on time, don’t wait for anyone.
✓ To coordinate multiple teams, have a separate Scrum of Scrum Meeting. Scrum of scrums
take the same format and are attended by one member of each delivery team.
✓ Master the daily stand up! It will allow you to better predict delivery, head off issues before
they impact the sprint, and keep the team focused and motivated.

11. User Story Format
1
2
3
As a type of user
I want to goal
So that I can reason
Who is this functionality
for?
What should we create?
Why is it valuable to the
user?

12. A User Story Should Meet INVEST Criteria
INDEPENDENT NEGOTIABLE VALUABLE ESTIMABLE
SIZED
APPROPRIATELY
TESTABLE
As a user, I want to log into my
mobile app so I can check my
balance on the go.
As a vacationer, I want to see
photos of the hotel rooms, so I can
determine which has the nicest
rooms.

13. How do you know when
a story is done?

14. Acceptance Criteria
● Written at the same time as the
user story
● Varies in number
● Tests if the functionality meets
expectations before release
● Includes both what the feature
should do & error states
● Includes design

16. Given context
when event
then outcome
Acceptance Criteria Format
1
2
3
What are the circumstances?
When does it occur?
What is the result?

22. Brief Debrief
● Have you experienced Agile
implementations?
● What has worked well?
● What is the hardest value to
incorporate?

25. Charis Loveland
Co-founder, ML Assist
Product manager in AI/ML,
design thinker, metrics-driven leader
@Mozilla, General Assembly, formerly Microsoft,
Rue La La, EMC, SAP
@charislovestech
LinkedIn