Uploaded on

 

More in: Technology
  • 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,199
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
118
Comments
0
Likes
1

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. Scrum An introduction Tricode Professional Services www.tricode.nl 03-04-2009 Sander van Beek
  • 2. What is Scrum?
    • An adaptive framework that can be understood and implemented in a few days
    • Optimized for new product development
    • A collaborative effort involving developers and customers in ongoing dialog
    • A management wrapper around existing engineering practices, driving incremental improvements.
  • 3. What is Scrum NOT?
    • Entirely new
    • A silver bullet
    • Scrum does not handle
      • Raises, promotions, job titles
      • A team member is incompetent, lazy, etc
      • Half the team is in India
      • PRINCE2, CMMI, ISO9000, Sarbanes Oxley, etc
      • The scrum master is allergic to cats
  • 4. Small teams, short iterations, clear goals
  • 5. Scrum process
  • 6. Artifacts
  • 7. The product backlog
    • Contains user stories (!= use cases)
      • As a ... I want ... so that i can ... (functionality)
    • Each user story contains
      • Description
      • Estimate
      • Definition of done (DoD)
      • Business value
    • Prioritized on
    • business value
  • 8. The sprint backlog
    • User stories split up into tasks
    • Every sprint must yield something to demonstrate -> vertical slice of the product (e.g. Only hello world is enough)
    • Tasks include analyse, design, build, test
  • 9. Burndown chart
    • Shows progress, work to be done, work added
    • Velocity
  • 10. Roles
  • 11. Roles in scrum
    • Product owner
    • Scrum master (!= project manager)
    • Scrum team
  • 12. Product owner
    • Single point of contact for stakeholders
    • Synthesizes interests of stakeholders
    • Makes business decisions
    • Keeps eye on business value
    • Accepts or rejects result of a sprint
    • Decides wether to ship
  • 13. Scrum master
    • Facilitates the Scrum process
    • Takes away impediments, shields team
    • Helps team self organizing
    • Helps product owner with prioritizing
    • Advocates improved engineering practices
    • Has NO authority
  • 14. Scrum team
    • Cross functional (designers, developers, testers, etc)
    • Self organizing
    • Autonomous
    • Held responsible for commitments
    • +/- 7 members (min 5, max 9)
  • 15. Meetings
  • 16. Meetings in scrum
  • 17. Sprint planning meeting
    • Add estimates to user stories
    • Moving PBI’s to spring backlog
  • 18. Daily scrum
    • Timeboxed to max 15 minutes
    • Stand up meeting
    • 3 questions:
      • What did I do yesterday?
      • What will I do to today?
      • What problems did I encounter that prevent me from doing my work?
  • 19. Sprint review
    • Present the sprint product
    • Includes stakeholders
    • Approval of backlog items implemented
    • New feature requests added to product backlog
  • 20. Sprint retrospective
    • What went well / what could be improved
    • Silent writing
    • Combined with coach meeting?
  • 21. Backlog refinement
    • Every time when changes occur on the backlog
    • Scrum master advises on dependencies
  • 22. Now you know Scrum!
  • 23. When to use Scrum?
  • 24. Scrum vs Waterfall
  • 25. Scrum vs Waterfall (2)
    • feedback loop
  • 26. Timeboxing
    • Requirements
    • Time (fixed)
    • People (fixed)
  • 27. Technical debt
  • 28. Converging burndown chart
  • 29. Planning & estimation
    • Estimation poker
    • S, M, L, XL (epic)
    • Relative distances
    • Learning from others
  • 30. Stories
    • Non technical!
    • Definition of done
  • 31. Stories (2)
  • 32. Good practices that go with scrum
    • Continuous refactoring
    • Test driven development
      • Unit tests vs System tests
    • Continuous integration
    • Pair programming
  • 33. Advantages of Scrum for the business
    • Maximize business value
    • Early warning when deadlines will not be met (if you fail fail as early as possible)
    • Better end product
    • A working product very quickly
  • 34. Advantages of Scrum for developers
    • Clear goals
    • Focus on your real work
    • Choose the work you like
    • Responsability
    • Not a peon