Key IngredientScrum Training by Lucina Stricko, CSPO

Presented on September 12, 2014

Recap

What is Scrum?

Scrum is

A light-weight, iterative and incremental Agile project management framework

Scrum at a glance

Individuals in Scrum Team

Product Manager

Individuals in Scrum

ScrumMaster

Individuals in Scrum

Scrum Team - self-organizing

Individuals in Scrum

Scrum Team - cross-functioning “T-shaped” team members

Individuals

Ideal Size - 7 +/- 2

2 pizza team

Interactions are time-boxed

• Stakeholders Meeting [1 hour per Sprint]

• Planning Meetings [depends on length of Sprint]

• Daily Scrum/Standups [15 minutes per day]

• Sprint Review/Demo [1 hour per Sprint]

• Retrospective [1 hour per Sprint]

Stakeholders Meeting

• Seek to Understand Business Objectives• Prioritize Items in Backlog based on Business Value• Manage Stakeholder Expectations…

• You cannot promise when something will get done, only that it will get added to the backlog!• If they think it’s the “highest priority” you need to get stakeholders to AGREE that it’s higher than the top things on the stakeholder…

Planning Meeting

• Grooming - Break down large stories (EPICs) into smaller tasks (Children)• Estimate tasks• Commit to achieving the Sprint Goal• Commit to completing tickets before the end of the Sprint

Example of an EPIC

Example of AssociatedChildrenTickets

Anatomy of a User Story

Example of a Clear User Story

Estimating Tickets

• Estimating in Story Points, T-Shirt Sizes

• What Story Points Tell Us

• Why Not Estimate in Hours?

Choosing Estimating Games

• Fibonacci Cards• 0, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89

• “as a feature increases in size, our inherent ability to accurately estimate its size diminishes”

• http://pmstudent.com/implementing-scrum-the-basics-part-2/

• Planning Poker• http://en.wikipedia.org/wiki/Planning_poker

Anatomy of a Scrum Board

Pull vs. Push

Daily Standups

Daily Standups - Time Boxed [15m]

Sprint Review (aka Demo Time)

Burn Down Chart

Retrospective• In Practice… these can be somewhat difficult to manage.• Focus on specific things that went well & didn’t go well.• Focus on the work, not on the person!• Try to get to 1 thing we might want to do better next time.• The ScrumMaster will remind the team to keep working on that item during the sprint.• At the next Retro, you will have a victory to celebrate!

Scrum

VS

Kanban

Commitment in Scrum

Problems with Scrum1. Management Doesn’t Get it!!! (Imposed Deadlines/etc)

2. Requires Small Teams, hard to grow…

3. Co-location (problems with remote teams/members)…. using online tools and having a dedicated ScrumMaster with the team helps

4. Planning takes a lot of collaboration

5. Everyone wants to solve problems in standup - take it offline

6. Cross-functioning not always possible… teams not all with same skills.

7. Unshippable Sprint Results - avoidable with thorough planning

8. Training new Team members - forming new team interrupts with norming and performing

9. Interruptions/Urgent changes - allowed as one “Silver Bullet” at a time

Scrum: Quick-Reference GuidePig = Directly committed to developing products (see 3 Scrum Roles)Chicken = Involved but not in the trenches (Customers, Managers, Marketing)

3 Scrum Roles: 3 Scrum Ceremonies: 3 More Ceremonies:Product Owner Sprint Planning Meeting Stakeholders MeetingScrumMaster Daily Scrum / Standup Backlog GroomingScrum Team Retrospective Demonstrations

3 Artifacts: 3 Best Practices: 3 Agile Acronyms: Product Backlog User Stories TDD Test Driven DevelopmentSprint Backlog Estimating/Planning Poker MVPBurndown Chart Scrum Board YAGNI

Doing Scrum vs Being AgilePlease see “Becoming an Agile Team Member” from Planigle -

http://www.planigle.com/presentations/Becoming-an-Agile-Team-Member.pdf

Questions?Feedback?

Source References● slide 2 http://www.agile-pm.org/ ● slide 3 http://www.votility.com/ ● slide 5 http://scrummethodology.com/ ● slide 6 http://www.thousandtyone.com/blog/HowBigAreYourTeams.aspx ● slide 16 http://alaverdyan.com ● slide 21 https://www.outsystems.com/blog/2010/11/scrum-vs-kanban.html ● slide 22 http://stevenhollidge.blogspot.com/2011/10/agile-principles.html ● slide 24 http://tatiyants.com/geek-comic-daily-standups/ ● slide 25 http://www.agiledocs.com/new-questions-for-daily-scrum-standups/ ● slide 26 http://www.rodrigodetoledo.com/ ● slides: 14, 15, 16, 17, 28, 29

○ https://keyingredient.unfuddle.com