What is Scrum? Project Management beyond the promise.

  • 2,673 views
Uploaded on

What is Scrum? Principles, rules, roles, artefacts, timeboxes of Scrum.

What is Scrum? Principles, rules, roles, artefacts, timeboxes of Scrum.

More in: Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,673
On Slideshare
0
From Embeds
0
Number of Embeds
4

Actions

Shares
Downloads
65
Comments
0
Likes
4

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. What is Scrum?Project Management beyond the promise @bartvermijlen
  • 2. Overview • introduction • roots • principles • a framework • roles • timeboxes • rules • artefacts • money for nothing and change for free
  • 3. IntroductionA project has 4 fixed aspects• Time• Budget• Quality• Scope
  • 4. IntroductionA project has 4 fixed aspects• Time (?)• Budget• Quality (?)• Scope (?)
  • 5. IntroductionA project has 4 fixed aspects• Time• Budget• Quality (?)• ScopeA scrum project has 3 fixed aspects• Time• Budget• QualityScope is not fixed!
  • 6. Scrum RootsAgile Software development:Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan(Agilemanifesto.org)
  • 7. Scrum RootsAgile Software development:Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan(Agilemanifesto.org)
  • 8. Scrum PrinciplesAgility = Responsiveness to changeTransparencyInspectionAdaptation
  • 9. Scrum = a frameworkRoles • Team • Product Owner • Scrum MasterTimeboxes • Sprint • Sprint planning • Sprint review (+ retrospective) • Daily ScrumArtefacts• Product backlog• Sprint backlog (-> Scrumboard)• Burndown chart
  • 10. Scrum RolesTeam • developers, testers, UX designers, SEO/Analytics,… • 2-7 • self organising • split product backlog into tasksProductowner • define & prioritise product backlog / user stories • negotiate definition of "Done"Scrum Master • guard scrum process • remove team impediments
  • 11. Scrum TimeboxesSprint • 1-4 weeks • ends with potentially shippable products (working software)Sprint planning (SM, Team, PO) • 1-8 hoursDaily Scrum (SM, Team) • 15 mins • yesterday/today/impedimentsSprint review (SM, Team, PO) • 30 mins - 4 hours • Demo or Die • acceptance of user stories by POSprint retrospective (SM, Team) ! • lessons learned
  • 12. Scrum Rules• Priorities never change during a sprint• Nobody (neither PO) must interfere during a sprint• Team can ask new user stories when finished early to PO• Team is self-regulating
  • 13. Scrum artefactsProduct backlog • Managed & prioritised by PO • User storiesSprint backlog • Quantified tasks (derived from product backlog) • Managed by Team
  • 14. Scrum artefacts - Burndown charthours/points s1 s2 s3 time
  • 15. Scrum artefacts - Burndown charthours/points s1 s2 s3 time
  • 16. Scrum artefacts - Scrumboard
  • 17. Change for free= obviousPO can reorder priorities at every sprint planning
  • 18. Money for nothinghours/pointspay back70% to Remove functionalitycustomer,Keep 30% s1 s2 s3 time
  • 19. Further reading- agilemanifesto.org- scrumalliance.org- scrum.org/scrumguides- scrum.jeffsutherland.com- Ken Schwaber: “Agile Project Management with Scrum” (Microsoft Press)
  • 20. @bartvermijlen