Agile ScrumJason Dean, CSM

AgileScrumPro.org

Agile Scrum

• What is Agile?– Agile Manifesto – Ethos of Agile– Agile Scrum Context– Scrum in a Nutshell

• Roles and Responsibilities• Details

– Epics, Stories, and COS– Meetings– Shippable

• Measurement

Agile Manifesto

Individuals and Interactions

Processesand Tools

WorkingSoftware

ComprehensiveDocumentation

CustomerCollaboration

ContractNegotiation

Respondingto Change

Followinga Plan

over

over

over

over

Agile – Development Framework

• Practices

– Iterative Development

– Test Driven Development

– Refactoring

– Pair Programming

– Continuous Integration

– User Stories

– Automated Testing

• Dev Approaches

– Extreme Programming (XP)

– Scrum

– Dynamic Systems Development Method (DSDM)

– Lean

Scrum in a Nutshell

SprintBacklog

done

PotentiallyShippableSoftware

Discovery Sessions

Defects

Strategy

1. User Story2. User Story3. User Story4. User Story5. User Story

Product Backlog

goal

feedback

Review (Demo)

Retrospective

Sprint Planning

Roles and Responsibilities• Defines features and release dates• Responsible for ROI• Prioritizes features by business value• Accepts or rejects work

ProductOwner

ScrumMaster

TeamMember

Ensures team is functioning and productive

Removes barriers (impediments)

Shields team from external interference

Ensures the process is followed

Facilitates planning, not a traditional PM

Cross functional, 7 +/- 2 members

Self directed

Organizes itself and tasks

Commits to Sprint and Demos to Product Owner

Chickens and Pigs

Epics, Stories, and COS

• Release – group of functionality going out to the customer

• Epic – large block of functionality

• User Story – bite sized piece of functionality– As a <user type> I want <some functionality> so that

<reason>.

– As a user I want to be able to print my list of items so I can use it as a shopping list at the store.

• Conditions of Satisfaction (Acceptance Criteria) –Details that determine the definition of “Done”

• Theme – Epics or stories that are grouped together

1. User Story2. User Story3. User Story4. User Story5. User Story

Product Backlog

Startup and Daily Meetings

• Sprint Planning

– Review User Stories

– Tasking and some task assignments

– Deployment considerations

• Daily Scrum – stand up, only pigs talk, not status

– What did you do yesterday?

– What are you going to do today?

– What is impeding your progress?

SprintBacklog

1. User Story2. User Story3. User Story4. User Story5. User Story

Product Backlog

Wrapup Meetings

• Sprint Review

– Demonstrate functionality to Customers/Stakeholders

• Retrospective (Post Mortem)

– What did we do well?

– What should we do again?

– What opportunities do we have to improve?

Sprinting

• No changes during a sprint – No one can add or remove work

but the team

– If necessary Team can work with Product Owner to trade insertion with something else

– Recommitment and Tasking

• Abnormal Termination– If can’t meet the Sprint Goal

– If business needs change

Potentially Shippable

• Each sprint ends with a Potentially Shippable product increment– May not push out to the user, but can

– Done, Done, Done (testing, integration, deployment, etc)

• May not be cohesive– i.e. Print preview but no print

– May take more than one Sprint to release

Measurement

0

5

10

15

20

25

Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10

Sprint Burndown

Actual

What did we talk about?

• Agile Scrum ethos, context, and overview

• Roles and Responsibilities

• Details (Stories, Meetings)

• Measurement

AgileScrumPro.orgjason@jasonleedean.com

References

• Ken Schwaber - ControlChaos.com

• Mike Cohn - MountainGoatSoftware.com

• Martin Fowler – MartinFowler.com

• ScrumAlliance.com

• ImplementingScrum.com

• AgileManifesto.org

• Rugby Video -http://www.youtube.com/watch?v=IEQyCcageGg