SCRUM training in Avantica Technologies (2010-2011)

2. Agenda
What's the software problem?
Agile
Agile Manifesto
Origins
What's SCRUM?
Used by?
Used for?
When to use SCRUM?

3. Agenda
Roles
Activities
Artifacts
SCRUM Rules
SCRUM Add-ons
How to start SCRUM
SCRUM Planning
SCRUM Metrics
Collocation and Team Rooms

4. What's the software problem?

Releases take too long

Stabilisation takes too long

Changes are hard to make

Quality is falling

Death marches are hurting morale

5. What's 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

6. What's the software problem?

7. What's the software problem?

8. Agile

9. Agile Manifesto
• Undefined (nothing “written in stone”)
• Flexible (change project scope)
• Visible (no late surprises)
• Early results
• Customer involvement (more work for client)

10. Agile Manifesto

11. 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

12. What's 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

13. What's SCRUM?

14. What's SCRUM?

15. What's SCRUM?

16. What's SCRUM?
User
Stories

17. Used by?

18. 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

19. What can I expect?

20. When to use SCRUM?

21. SCRUM Roles
Team

22. SCRUM Roles
Product Owner

23. SCRUM Roles
Scrum Master

24. 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

25. SCRUM Activities
Sprint Planning
• When iteration is planned
• 2 hours for each week of sprint duration (8h for a 4 weeks sprint)

26. SCRUM Activities
Daily SCRUM

27. 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

28. SCRUM Activities
Spring Retrospective
• Inspect – Feedback – Adapt THE PROCESS
• Design a “What's working well” - “What could work better” chart
• “Start – Stop – Continue” Doing technique
• Usually ignored but is A KEY for long term projects

29. SCRUM Artifacts
Product Backlog

30. SCRUM Artifacts
Sprint Backlog

31. SCRUM Artifacts
Sprint Backlog

32. SCRUM Artifacts
Sprint Backlog

33. SCRUM Artifacts
Sprint Backlog

34. SCRUM Artifacts
Burndown Charts
Sprint Burndown

35. SCRUM Artifacts
Burndown Charts

36. SCRUM Artifacts
Burndown Charts
Product Burndown

37. 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

38. SCRUM Add-ons
• Optional for SCRUM approach
– Release Planning
– Release Sprint
– Backlog Refinement
– Impediment Backlog (AKA Impediment List)
– Product Backlog Delta

39. 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!!!

40. SCRUM Planning?
• Velocity based planning
• Story points (estimate the size, not the duration)
• Planning poker

41. 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

42. Collocation and Team Rooms

43. 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

44. Not the end...
But to be continued, I hope :)
Thanks!