Scrum software develoment

20
Scrum

Transcript of Scrum software develoment

Page 1: Scrum software develoment

Scrum

Page 2: Scrum software develoment

[email protected]@alex_sukhanov

Alexander Sukhanov

Page 3: Scrum software develoment

3 pillars of Scrum

• Transparency– Definition of Done– Common language

• Inspection• Adaptation (to minimize deviation from the

goal)

Page 4: Scrum software develoment

People

• Scrum Team– Product Owner (PO)– Development Team (DT)– Scrum Master (SM)

• Stakeholders

Page 5: Scrum software develoment

Product Owner

• Responsible for Product Backlog (PB)• Expresses PB• Prioritizing PB

Can delegate above work to DT, but is still responsible

Page 6: Scrum software develoment

Development Team

• Self-organizing. No one tells them how to turn PB into the Increment

• Cross-functional• Only one title – “Developer”• No sub-teams• The whole team is held responsible• Only DT creates the Increment

Size: 3-9 people

Page 7: Scrum software develoment

Scrum Master

Page 8: Scrum software develoment

Scrum Master to PO

• Effective backlog management• The need for clear Backlog items• Prioritizing Backlog items for max. value• Practicing Agility• Facilitating Scrum Events

Page 9: Scrum software develoment

Scrum Master to DT

• Coaching in self-organization and cross-functionality

• Help in creating high value products• Removing impediments• Facilitating Scrum Events• Coaching DT

Page 10: Scrum software develoment

Scrum Master to Organization

• Leading and coaching on Scrum adoption• Planning Scrum implementation• Explaining Scrum• Change helping the Scrum Team

Page 11: Scrum software develoment

Scrum Events

• Sprint• Sprint Planning• Daily Scrum• Scrum Review• Scrum Retrospective

Page 12: Scrum software develoment

Sprint

• Length: 2-4 weeks• No changes with Sprint Backlog• Quality doesn’t decrease• Scope could be re-negotiated between DT and

PO

*PO can cancel a Sprint

Page 13: Scrum software develoment

Sprint Planning

• What can be done this Sprint• How will the chosen work be done• Sprint goal• Max time – 8 hours

Page 14: Scrum software develoment

Daily Scrum

• My work yesterday on the Sprint Goal• My work today on the Sprint Goal• Do I see any impediment?

Max time – 15 minutes

Page 15: Scrum software develoment

Sprint Review

• Adapt Sprint Backlog• PO invites attendees and explains what is

“Done” and what is not.• What will be done next• Review of 4 characteristics of the project:

time, scope, quality, budget.• Max time – 4 hours

Page 16: Scrum software develoment

Sprint Retrospective

• Inspect how the Sprint went• Identify areas of improvement• Plan for the next Sprint• Max time – 3 hours

Page 17: Scrum software develoment

Scrum Artifacts

• Product Backlog• Sprint Backlog• Increment

Page 18: Scrum software develoment

Scrum +

Page 19: Scrum software develoment

Story points & planning poker

Page 20: Scrum software develoment

Burndown chart