View stunning SlideShares in full-screen with the new iOS app!Introducing SlideShare for AndroidExplore all your favorite topics in the SlideShare appGet the SlideShare app to Save for Later — even offline
View stunning SlideShares in full-screen with the new Android app!View stunning SlideShares in full-screen with the new iOS app!
AgendaWhats the software problem? Agile Agile Manifesto Origins Whats SCRUM? Used by? Used for? When to use SCRUM?
Agenda Roles Activities Artifacts SCRUM Rules SCRUM Add-ons How to start SCRUM SCRUM Planning SCRUM MetricsCollocation and Team Rooms
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
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
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
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
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
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
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
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
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!!!
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• Technical debt• Work-in-process• Story cycle time• Cost per sprint/story point• Real value delivered• ROI or NPV
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
Not the end...But to be continued, I hope :) Thanks!