Your SlideShare is downloading. ×
0
Scrum in an hour
   Giordano Scalzo, 12/03/2009
Agenda
– Introduction to Scrum (30 m)
– Scrum in Registratori (10 m)
– Q&A? (15 m)
Traditional
Phased development
Anticipated results
Up-front design
Results

    Requirements Not Clear
  Fear to go to the next phase
  Analysis Paralysis



 Requirements Change
Change get...
Results

      Project Takes Too Long
   34% of projects delivered successfully
   Long duration defers revenue
   (Source...
Results

          Time Wasted on Junk
       52% of requirements implemented
       64% of functionality rarely used
    ...
Agile
  project
management
Agile Principles
1. Satisfy the Customer
2. Welcome Change
3. Deliver Frequently
4. Work as a Team
5. Motivate People
6. C...
Scrum
Origin of Scrum

“The New New Product Development Game”
  Hirotaka Takeuchi and Ikujiro Nonaka - 1986



         “The Kno...
The Goal of
                             Scrum




Manage Complexity, Unpredictability and Change
 through Visibility, Ins...
Scrum is
A methodology framework

An iterative process

A wrapper for existing
practices
A way to improve
communications
A...
Scrum is not
A silver bullet

A magic wand

Just for software

About engineering pratices

A shortcut
A step-by-step cookb...
Scrum
 Roles
Product Owner




           Owner of project vision
          Represents the customer
Product Owner
Define features
(according to vision)

Prioritize features
(according to ROI)

Pick release dates


Give fee...
The Team




      Small (5–9 people)
  Colocated - Cross-functional
   Self-organized - Full-time
The Team
Define tasks
Estimate effort
Develop product
Ensure quality
Evolve processes
Scrum Master




 Servant leader
 Team protector
  Scrum guide
Scrum Master
Remove
impediments
Prevent
interruptions
Facilitate the team
Support the process
Manage
management
Scrum Process
Scrum Process
Product Backlog
Product Backlog
Owned by Product Owner
High-level requirements
Expressed as business
value
Not complete, nor perfect
Expec...
Product Backlog



Prioritized by
 value & risk         Includes rough
                         estimates




 Better to d...
Sprints




     Timeboxed – Frozen features
   Variable scope – Shippable result
Sprint Planning




                  +
                  +
                  =
Sprint Planning
Face to face
communication
Small reversible steps
User’s perspective
Sprint Planning
    (Part 1)
Strategical level planning
Prioritize/select features
Discuss acceptance criteria
Verify unde...
Sprint Planning
    (Part 2)
Tactical level planning
Define sprint backlog items
Estimate sprint backlog items
Use velocit...
Sprint Backlog




  Breakdown of business value into
         assignable tasks
Sprint Backlog
Sprint Backlog


Owned by the team
Team allocates work
No additions by others
Daily Scrum




      The heartbeat of Scrum
Daily Scrum
What I did since last
meeting
What I will do until next
meeting
What things are in my
way

Only the team talks...
Task Board




       Information irradiator
Definition of Done




    ...Coded, commented, checked in,
    integrated, reviewed, unit tested,
    deployed to test en...
Burndown Chart
Sprint Review




           Satisfy Product Owner
         Get feedback on product
Sprint Review

Informal, no slides
Whole team participates
The world is invited
Show complete
features

Accept or reject r...
Sprint Retrospective




 Evolve the process
Sprint
 Retrospective
Reflect on process and
product
Whole team participates
What to start doing
What to stop doing
What t...
Sprints




Steady pull of business value
     Inspect and Adapt
Sprints

Driven by Product
Owner
Welcome change
Include design and
testing
Share commitment
“Fail fast”
Abnormal Sprint
   Termination
Only in extreme cases
Team terminates: cannot meet
sprint goal
Product Owner terminates: pr...
Results
   effects of
 applying Scrum
Managed Uncertainty
Rolling wave planning
Simpler mini-projects lowers risk




          Flexible Scope
          Allow c...
Faster Delivery
Shorter time to market
Value delivered in increments




        Higher Quality
        Testing happens co...
Eliminated Waste
Nothing is designed that is not built
Nothing is built that is not used




Increased Visibility
All prob...
Scrum
applied
Scrum Taskboard
Planning poker cards
Pomodoro timer
Rules
Sprint
Backlog
Q&A?
Scrum in an hour
Scrum in an hour
Scrum in an hour
Upcoming SlideShare
Loading in...5
×

Scrum in an hour

10,140

Published on

A brief introduction to Scrum and to benefits of agile metodologies

Published in: Technology, News & Politics
0 Comments
27 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
10,140
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
587
Comments
0
Likes
27
Embeds 0
No embeds

No notes for slide

Transcript of "Scrum in an hour"

  1. 1. Scrum in an hour Giordano Scalzo, 12/03/2009
  2. 2. Agenda – Introduction to Scrum (30 m) – Scrum in Registratori (10 m) – Q&A? (15 m)
  3. 3. Traditional Phased development Anticipated results Up-front design
  4. 4. Results Requirements Not Clear Fear to go to the next phase Analysis Paralysis Requirements Change Change gets more and more expensive Customers don’t get what they want
  5. 5. Results Project Takes Too Long 34% of projects delivered successfully Long duration defers revenue (Source: Standish Report 2003) No Time for Testing Quality assurance gets crunched Late integration means late failures
  6. 6. Results Time Wasted on Junk 52% of requirements implemented 64% of functionality rarely used (Source: Standish Report 1994) Poor Progress Visibility % Task complete not sufficient Average overrun 43% (Source: Standish Report 1994)
  7. 7. Agile project management
  8. 8. Agile Principles 1. Satisfy the Customer 2. Welcome Change 3. Deliver Frequently 4. Work as a Team 5. Motivate People 6. Communicate Face-to- Face 7. Measure Working Software 8. Maintain Constant Pace 9. Excel at Quality 10.Keep it Simple 11.Evolve Designs 12.Reflect Regularly
  9. 9. Scrum
  10. 10. Origin of Scrum “The New New Product Development Game” Hirotaka Takeuchi and Ikujiro Nonaka - 1986 “The Knowledge Creating Company” Hirotaka Takeuchi and Ikujiro Nonaka - 1988 “Agile Manifesto” Ken Schwaber and Jeff Sutherland - 1994
  11. 11. The Goal of Scrum Manage Complexity, Unpredictability and Change through Visibility, Inspection and Adaptation
  12. 12. Scrum is A methodology framework An iterative process A wrapper for existing practices A way to improve communications A way to maximize productivity A buzzword
  13. 13. Scrum is not A silver bullet A magic wand Just for software About engineering pratices A shortcut A step-by-step cookbook approach Easy: it needs time and discipline
  14. 14. Scrum Roles
  15. 15. Product Owner Owner of project vision Represents the customer
  16. 16. Product Owner Define features (according to vision) Prioritize features (according to ROI) Pick release dates Give feedback Manage stakeholders Accept or reject results
  17. 17. The Team Small (5–9 people) Colocated - Cross-functional Self-organized - Full-time
  18. 18. The Team Define tasks Estimate effort Develop product Ensure quality Evolve processes
  19. 19. Scrum Master Servant leader Team protector Scrum guide
  20. 20. Scrum Master Remove impediments Prevent interruptions Facilitate the team Support the process Manage management
  21. 21. Scrum Process
  22. 22. Scrum Process
  23. 23. Product Backlog
  24. 24. Product Backlog Owned by Product Owner High-level requirements Expressed as business value Not complete, nor perfect Expected to change & evolve Limited view into the future
  25. 25. Product Backlog Prioritized by value & risk Includes rough estimates Better to describe as user stories Publicly visible
  26. 26. Sprints Timeboxed – Frozen features Variable scope – Shippable result
  27. 27. Sprint Planning + + =
  28. 28. Sprint Planning Face to face communication Small reversible steps User’s perspective
  29. 29. Sprint Planning (Part 1) Strategical level planning Prioritize/select features Discuss acceptance criteria Verify understanding ½ - 1 hour per sprint/week
  30. 30. Sprint Planning (Part 2) Tactical level planning Define sprint backlog items Estimate sprint backlog items Use velocity (Yesterday’s Weather) Share commitment ½ - 1 hour per sprint/week
  31. 31. Sprint Backlog Breakdown of business value into assignable tasks
  32. 32. Sprint Backlog
  33. 33. Sprint Backlog Owned by the team Team allocates work No additions by others
  34. 34. Daily Scrum The heartbeat of Scrum
  35. 35. Daily Scrum What I did since last meeting What I will do until next meeting What things are in my way Only the team talks Not to Scrum Master No problem solving Max 15 minutes
  36. 36. Task Board Information irradiator
  37. 37. Definition of Done ...Coded, commented, checked in, integrated, reviewed, unit tested, deployed to test environment, passed user acceptance test & documented...
  38. 38. Burndown Chart
  39. 39. Sprint Review Satisfy Product Owner Get feedback on product
  40. 40. Sprint Review Informal, no slides Whole team participates The world is invited Show complete features Accept or reject results ½ - 1 hour per sprint/week
  41. 41. Sprint Retrospective Evolve the process
  42. 42. Sprint Retrospective Reflect on process and product Whole team participates What to start doing What to stop doing What to continue doing
  43. 43. Sprints Steady pull of business value Inspect and Adapt
  44. 44. Sprints Driven by Product Owner Welcome change Include design and testing Share commitment “Fail fast”
  45. 45. Abnormal Sprint Termination Only in extreme cases Team terminates: cannot meet sprint goal Product Owner terminates: priority change Raises visibility of problems
  46. 46. Results effects of applying Scrum
  47. 47. Managed Uncertainty Rolling wave planning Simpler mini-projects lowers risk Flexible Scope Allow changes at fixed intervals Releases enable learning
  48. 48. Faster Delivery Shorter time to market Value delivered in increments Higher Quality Testing happens continuously Process improvement built-in
  49. 49. Eliminated Waste Nothing is designed that is not built Nothing is built that is not used Increased Visibility All problems are made visible Progress is running tested software
  50. 50. Scrum applied
  51. 51. Scrum Taskboard
  52. 52. Planning poker cards
  53. 53. Pomodoro timer
  54. 54. Rules
  55. 55. Sprint Backlog
  56. 56. Q&A?
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×