Your SlideShare is downloading. ×
AgendaWhats the software problem?           Agile      Agile Manifesto          Origins      Whats SCRUM?         Used by?...
Agenda          Roles        Activities         Artifacts      SCRUM Rules     SCRUM Add-ons   How to start SCRUM     SCRU...
Whats the software problem?    Releases take too long    Stabilisation takes too long    Changes are hard to make    Q...
Whats the software problem?    31.1% of IT projects will be canceled before    completion    52.7% of completed projects...
Whats the software problem?
Whats the software problem?
Agile
Agile Manifesto•   Undefined (nothing “written in stone”)•   Flexible (change project scope)•   Visible (no late surprises...
Agile Manifesto
SCRUM Origins•   1970: Dr. Winston Royce “Managing the development of    large software systems”•   1986: Takeuchi & Nanon...
Whats SCRUM?•   Transparency * Inspection * Adaptation•   Simplest Agile framework•   Real world progress of a project = “...
Whats SCRUM?
Whats SCRUM?
Whats SCRUM?
Whats SCRUM? UserStories
Used by?
Used for?    Commercial software                                             Video game development    In-house develop...
What can I expect?
When to use SCRUM?
SCRUM Roles   Team
SCRUM RolesProduct Owner
SCRUM RolesScrum Master
SCRUM Activities•     Time boxed meetings•     Sprint is the heartbeat of the SCRUM cycle     SPRINT                    SP...
SCRUM Activities                     Sprint Planning•   When iteration is planned•   2 hours for each week of sprint durat...
SCRUM Activities Daily SCRUM
SCRUM Activities               Sprint Review Meeting•   Not a product “demo” showtime•   Inspect – Feedback – Adapt THE PR...
SCRUM Activities                Spring Retrospective•   Inspect – Feedback – Adapt THE PROCESS•   Design a “Whats working ...
SCRUM ArtifactsProduct Backlog
SCRUM Artifacts Sprint Backlog
SCRUM Artifacts Sprint Backlog
SCRUM Artifacts Sprint Backlog
SCRUM Artifacts Sprint Backlog
SCRUM ArtifactsBurndown Charts Sprint Burndown
SCRUM ArtifactsBurndown Charts
SCRUM ArtifactsBurndown Charts Product Burndown
SCRUM Rules•   A potentially shippable product increment at the end of    the sprint•   Pottentially shippable <> Shippabl...
SCRUM Add-ons•   Optional for SCRUM approach     –   Release Planning     –   Release Sprint     –   Backlog Refinement   ...
How to start SCRUM?•   Train the team in in the basics of SCRUM•   Establish the vision•   Write user stories to form the ...
SCRUM Planning?•   Velocity based planning•   Story points (estimate the size, not the duration)•   Planning poker
SCRUM Metrics?•   Customer and team surveys•   Velocity chart•   Burnup/burndown chat•   Running automated test•   Technic...
Collocation and Team Rooms
Conclusions•   SCRUM only attempts to manage the manageable•   Not a silver bullet in project management•   “Done” and “Un...
Not the end...But to be continued, I hope :)          Thanks!
Avantica presentacion scrum
Upcoming SlideShare
Loading in...5
×

Avantica presentacion scrum

1,010

Published on

SCRUM training in Avantica Technologies (2010-2011)

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,010
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Debe conocer con quien está tratando es ingenuo llegar sin saber con quien se va a enfrentar.
  • Debe conocer con quien está tratando es ingenuo llegar sin saber con quien se va a enfrentar.
  • Debe conocer con quien está tratando es ingenuo llegar sin saber con quien se va a enfrentar.
  • Debe conocer con quien está tratando es ingenuo llegar sin saber con quien se va a enfrentar.
  • Transcript of "Avantica presentacion scrum"

    1. 1. AgendaWhats the software problem? Agile Agile Manifesto Origins Whats SCRUM? Used by? Used for? When to use SCRUM?
    2. 2. Agenda Roles Activities Artifacts SCRUM Rules SCRUM Add-ons How to start SCRUM SCRUM Planning SCRUM MetricsCollocation and Team Rooms
    3. 3. Whats the software problem? Releases take too long Stabilisation takes too long Changes are hard to make Quality is falling Death marches are hurting morale
    4. 4. Whats the software problem? 31.1% of IT projects will be canceled before completion 52.7% of completed projects cost on average 189% over their original estimates 16.9% of projects are completed on time and budget The larger the project, the more likely to failure Chaos Report 1995-2008
    5. 5. Whats the software problem?
    6. 6. Whats the software problem?
    7. 7. Agile
    8. 8. Agile Manifesto• Undefined (nothing “written in stone”)• Flexible (change project scope)• Visible (no late surprises)• Early results• Customer involvement (more work for client)
    9. 9. Agile Manifesto
    10. 10. SCRUM Origins• 1970: Dr. Winston Royce “Managing the development of large software systems”• 1986: Takeuchi & Nanonaka – “Hardvard Business Review”• 1990: Best practices in Japan industry (Toyota/Honda)• 1993: Jeff Sutherland – First SW development SCRUM• 1995: Ken Schwaber – SCRUM Development Process
    11. 11. Whats SCRUM?• Transparency * Inspection * Adaptation• Simplest Agile framework• Real world progress of a project = “empirical process control”• Result oriented / Value-focused• Commited-driven• Empowers and respect teams
    12. 12. Whats SCRUM?
    13. 13. Whats SCRUM?
    14. 14. Whats SCRUM?
    15. 15. Whats SCRUM? UserStories
    16. 16. Used by?
    17. 17. Used for? Commercial software  Video game development In-house development  FDA-approved, life-critical systems Contract development  Satellite-control software Financial applications  Websites ISO 9001-certified applications  Handheld software Embedded systems  Mobile phones 24x7 systems with 99.999%  Network switching applications uptime requirements  ISV applications the Joint Strike Fighter  Some of the largest applications in use
    18. 18. What can I expect?
    19. 19. When to use SCRUM?
    20. 20. SCRUM Roles Team
    21. 21. SCRUM RolesProduct Owner
    22. 22. SCRUM RolesScrum Master
    23. 23. SCRUM Activities• Time boxed meetings• Sprint is the heartbeat of the SCRUM cycle SPRINT SPRINT SPRINT DAILY PLANNING REVIEW RETROSPECTIVE SCRUM MEETING MEETING MEETING BACKLOG REFINEMENT MEETING
    24. 24. SCRUM Activities Sprint Planning• When iteration is planned• 2 hours for each week of sprint duration (8h for a 4 weeks sprint)
    25. 25. SCRUM Activities Daily SCRUM
    26. 26. SCRUM Activities Sprint Review Meeting• Not a product “demo” showtime• Inspect – Feedback – Adapt THE PRODUCT• Team present what is accomplished during the sprint• Whole world in invited
    27. 27. SCRUM Activities Spring Retrospective• Inspect – Feedback – Adapt THE PROCESS• Design a “Whats working well” - “What could work better” chart• “Start – Stop – Continue” Doing technique• Usually ignored but is A KEY for long term projects
    28. 28. SCRUM ArtifactsProduct Backlog
    29. 29. SCRUM Artifacts Sprint Backlog
    30. 30. SCRUM Artifacts Sprint Backlog
    31. 31. SCRUM Artifacts Sprint Backlog
    32. 32. SCRUM Artifacts Sprint Backlog
    33. 33. SCRUM ArtifactsBurndown Charts Sprint Burndown
    34. 34. SCRUM ArtifactsBurndown Charts
    35. 35. SCRUM ArtifactsBurndown Charts Product Burndown
    36. 36. SCRUM Rules• A potentially shippable product increment at the end of the sprint• Pottentially shippable <> Shippable• Reciprocal commitments• No changes during a sprint• Arquitecture built and user-visible functionality over time
    37. 37. SCRUM Add-ons• Optional for SCRUM approach – Release Planning – Release Sprint – Backlog Refinement – Impediment Backlog (AKA Impediment List) – Product Backlog Delta
    38. 38. How to start SCRUM?• Train the team in in the basics of SCRUM• Establish the vision• Write user stories to form the product backlog• Order the backlog items by business value• Size the backlog items• Reorder the backlog if necessary• Create the initial release plan• Plan the first sprint• Start sprinting!!!
    39. 39. SCRUM Planning?• Velocity based planning• Story points (estimate the size, not the duration)• Planning poker
    40. 40. SCRUM Metrics?• Customer and team surveys• Velocity chart• Burnup/burndown chat• Running automated test• Technical debt• Work-in-process• Story cycle time• Cost per sprint/story point• Real value delivered• ROI or NPV
    41. 41. Collocation and Team Rooms
    42. 42. Conclusions• SCRUM only attempts to manage the manageable• Not a silver bullet in project management• “Done” and “Undone” work clear for Product Owner• “Release Sprints” to complete undone work• Focus “increments” as sprint goals
    43. 43. Not the end...But to be continued, I hope :) Thanks!

    ×