logging in or signing up The Zen of Scrum 1.0 amrik Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINT lite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 727 Category: Entertainment License: All Rights Reserved Like it (0) Dislike it (0) Added: February 28, 2009 This Presentation is Public Favorites: 2 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript The Zen of Scrum : The Zen of Scrum Jurgen Appelo – jurgen@noop.nl version 1.0 picture by ePi.Longo Agenda : Problems Agile Scrum Roles Scrum Process Hot Issues Results Agenda Problemswith traditional software development : Problemswith traditional software development photo by Jule_Berlin Traditional : Traditional Phased development Anticipated results Up-front design picture by jasonb42882 Requirements Not Clear : Requirements Not Clear Fear to go to the next phase Analysis paralysis Requirements Change : Requirements Change Change gets more and more expensive Customers don’t get what they want Project Takes Too Long : Project Takes Too Long 34% of projects delivered successfully Long duration defers revenue (Source: Standish Report 2003) No Time for Testing : No Time for Testing Quality assurance gets crunched Late integration means late failures Time Wasted on Junk : Time Wasted on Junk 52% of requirements implemented 64% of functionality rarely used (Source: Standish Report 1994) Poor Progress Visibility : Poor Progress Visibility % Task complete not sufficient Average overrun 43% (Source: Standish Report 1994) Agilesoftware development : Agilesoftware development Process Complexity (M) : Process Complexity (M) Agile projects Chaotic projects Structured projects Agile Manifesto : Agile Manifesto February 2001 http://agilemanifesto.org/ Agile Principles : Agile Principles Satisfy the Customer Welcome Change Deliver Frequently Work as a Team Motivate People Communicate Face-to-Face Measure Working Software Maintain Constant Pace Excel at Quality Keep it Simple Evolve Designs Reflect Regularly Agile Adoption : Agile Adoption Has Your Organization Adopted One or More Agile Techniques? Agile Adoption Survey 2008 Scott W. Ambler www.ambysoft.com/scottAmbler.html Scrum : Scrum picture by Kiwi Flickr The Gurus : The Gurus Ken Schwaber Jeff Sutherland Mike Beedle Mike Cohn Scrum Usage : Scrum Usage Commercial software - In-house development Contract development - Fixed-price projects Financial applications - ISO 9001-certified applications Embedded systems - 24x7 systems with 99.999% uptime Joint Strike Fighter - Video game development FDA-approved, life-critical systems - Web sites Satellite-control software - Handheld software Mobile phones - Network switching applications ISV applications - Some of the largest applications in use The Goal of Scrum : The Goal of Scrum Manage Complexity, Unpredictability and Change through Visibility, Inspection and Adaptation picture by OnTask Scrum Roles : Scrum Roles picture by exfordy Product Owner : Product Owner Owner of project vision Represents the customer picture by Official Star Wars Blog Product Owner : Product Owner Define features (according to vision) Prioritize features (according to ROI) Pick release dates Give feedback Manage stakeholders Accept or reject results The Team : The Team Small (5–9 people) Colocated - Cross-functional Self-organized - Full-time picture by ewen and donabel The Team : The Team Define tasks Estimate effort Develop product Ensure quality Evolve processes Scrum Master : Scrum Master Servant leader Team protector Scrum guide picture by Orange Beard Scrum Master : Scrum Master Remove impediments Prevent interruptions Facilitate the team Support the process Manage management Pigs and Chickens : Pigs and Chickens Product Owner Scrum Master Team Members Users Managers Marketing Scrum Process : Scrum Process Product Backlog : Product Backlog Express value Defer decisions picture by juhansonin Product Backlog : Product Backlog sample sample from Eclipse.org Product Backlog : 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 Product Backlog : Product Backlog Includes rough estimates Prioritized by value & risk Publicly visible Better to describe as user stories User Stories : User Stories As a <user> I want <functionality>( so that <benefit> ) As a librarian I want to be able to search for books by publication year Sprints : Sprints Timeboxed – Frozen features Variable scope – Shippable result Sprint Planning : Sprint Planning Team capacity, Product backlog, Current product, Business, Technologies Goal = + + picture by Darcy McCarty Sprint Planning : Sprint Planning Face-to-face communication Small reversible steps User’s perspective Sprint Planning (Part 1) : Sprint Planning (Part 1) Strategical level planning Prioritize/select features Discuss acceptance criteria Verify understanding ½ - 1 hour per sprint/week Sprint Planning (Part 2) : 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 Sprint Backlog : Sprint Backlog Breakdown of business value into assignable tasks picture by oskay Sprint Backlog : Sprint Backlog sample Sprint Backlog : Sprint Backlog Owned by the team Team allocates work No additions by others Daily Scrum : Daily Scrum The heartbeat of Scrum picture by Hamed Saber Daily Scrum : Daily Scrum picture by Hamed Saber Commitment and accountability Say what you do, do what you say Whole world is invited Daily 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 Not to Scrum Master No problem solving Max 15 minutes Standing up Task Board : Task Board Definition of Done : Definition of Done Avoid the 90% syndrome Coded, commented, checked in, integrated, reviewed, unit tested, deployed to test environment, passed user acceptance test& documented... = DONE DONE Sprint Burn Down : Sprint Burn Down picture by NibiruTech Sprint Review : Sprint Review Satisfy Product Owner Get feedback on product picture by oskay Sprint Review : Sprint Review picture by oskay Informal, no slides Whole team participates The world is invited Sprint Review : Sprint Review Preparation needed Show complete features Accept or reject results 1-2 hours per sprint/week Sprint Retrospective : Sprint Retrospective Evolve the process picture by kevindooley Sprint Retrospective : Sprint Retrospective Reflect on process and product Whole team participates Sprint Retrospective : Sprint Retrospective What to start doing What to stop doing What to continue doing (Product Owner not required) Burn Down Chart : Burn Down Chart Scope change Burn Up Chart : Burn Up Chart Scope keeps expanding Pipeline gets fatter Release Planning : Release Planning Plan features in sprints and releases Releases depend on accepted sprints picture by Sviluppo Agile Release Sprints : Release Sprints Usability testing Documentation Help files Packaging pictures by VistaICO Sprint Termination : Sprint Termination Only in extreme cases Team terminates: cannot meet sprint goal Product Owner terminates: priority change Work reverted to end of prior sprint Raises visibility of problems picture by VistaICO Sprints : Sprints Steady pull of business value Inspect and Adapt picture by kelsey e. Sprints : Sprints picture by kelsey e. Driven by Product Owner Small reversible steps Welcome change Cross-functional team Include design and testing Maintain constant pace Share commitment High quality, DONE Get feedback “Fail fast” Hot Issues : Hot Issues Scrum vs. XP : Scrum vs. XP picture by extremeprogramming.org Scrum vs. RUP : Scrum vs. RUP picture by WittmannClan.com Scrum vs. Kanban : Scrum vs. Kanban picture by Lean Software Engineering Scaled Scrum(Scrum of Scrums) : Scaled Scrum(Scrum of Scrums) picture by Mountain Goat Software Distributed Scrum : Distributed Scrum Resultseffects ofapplying Scrum : Resultseffects ofapplying Scrum Managed Uncertainty : Managed Uncertainty Rolling wave planning Simpler mini-projects lowers risk Flexible Scope : Flexible Scope Allow changes at fixed intervals Releases enable learning Faster Delivery : Faster Delivery Shorter time to market Value delivered in increments Higher Quality : Higher Quality Testing happens continuously Process improvement built-in Eliminated Waste : Eliminated Waste Nothing is designed that is not built Nothing is built that is not used Increased Visibility : Increased Visibility All problems are made visible Progress is running tested software Preconditions : Preconditions Empowerment Discipline Courage Stamina Passion Coaching Stable Teams Cross-Functional Available Customer picture by mpov Disclaimer : Disclaimer No Engineering Practices Looks Simple, Is Hard No Silver Bullet Not Complete Takes Time picture by a2gemma Books : Books Sites : Sites www.scrumalliance.org www.controlchaos.com www.mountaingoatsoftware.com www.jeffsutherland.com www.implementingscrum.com www.agilesoftwaredevelopment.com www.noop.nl picture by VistaICO Q & A : picture by -bast- Q & A NOOP.NL : NOOP.NL This is my blog, go read it now! Slide 80: http://creativecommons.org/licenses/by-nd/3.0/ This presentation was inspired by the works of many people, andI cannot possibly list them all. Though I did my very best to attribute all authors of texts and images, and to recognize any copyrights. If you think that anything in this presentation should be changed, added or removed, please contact me at jurgen@noop.nl. You do not have the permission to view this presentation. In order to view it, please contact the author of the presentation.
The Zen of Scrum 1.0 amrik Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINT lite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 727 Category: Entertainment License: All Rights Reserved Like it (0) Dislike it (0) Added: February 28, 2009 This Presentation is Public Favorites: 2 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript The Zen of Scrum : The Zen of Scrum Jurgen Appelo – jurgen@noop.nl version 1.0 picture by ePi.Longo Agenda : Problems Agile Scrum Roles Scrum Process Hot Issues Results Agenda Problemswith traditional software development : Problemswith traditional software development photo by Jule_Berlin Traditional : Traditional Phased development Anticipated results Up-front design picture by jasonb42882 Requirements Not Clear : Requirements Not Clear Fear to go to the next phase Analysis paralysis Requirements Change : Requirements Change Change gets more and more expensive Customers don’t get what they want Project Takes Too Long : Project Takes Too Long 34% of projects delivered successfully Long duration defers revenue (Source: Standish Report 2003) No Time for Testing : No Time for Testing Quality assurance gets crunched Late integration means late failures Time Wasted on Junk : Time Wasted on Junk 52% of requirements implemented 64% of functionality rarely used (Source: Standish Report 1994) Poor Progress Visibility : Poor Progress Visibility % Task complete not sufficient Average overrun 43% (Source: Standish Report 1994) Agilesoftware development : Agilesoftware development Process Complexity (M) : Process Complexity (M) Agile projects Chaotic projects Structured projects Agile Manifesto : Agile Manifesto February 2001 http://agilemanifesto.org/ Agile Principles : Agile Principles Satisfy the Customer Welcome Change Deliver Frequently Work as a Team Motivate People Communicate Face-to-Face Measure Working Software Maintain Constant Pace Excel at Quality Keep it Simple Evolve Designs Reflect Regularly Agile Adoption : Agile Adoption Has Your Organization Adopted One or More Agile Techniques? Agile Adoption Survey 2008 Scott W. Ambler www.ambysoft.com/scottAmbler.html Scrum : Scrum picture by Kiwi Flickr The Gurus : The Gurus Ken Schwaber Jeff Sutherland Mike Beedle Mike Cohn Scrum Usage : Scrum Usage Commercial software - In-house development Contract development - Fixed-price projects Financial applications - ISO 9001-certified applications Embedded systems - 24x7 systems with 99.999% uptime Joint Strike Fighter - Video game development FDA-approved, life-critical systems - Web sites Satellite-control software - Handheld software Mobile phones - Network switching applications ISV applications - Some of the largest applications in use The Goal of Scrum : The Goal of Scrum Manage Complexity, Unpredictability and Change through Visibility, Inspection and Adaptation picture by OnTask Scrum Roles : Scrum Roles picture by exfordy Product Owner : Product Owner Owner of project vision Represents the customer picture by Official Star Wars Blog Product Owner : Product Owner Define features (according to vision) Prioritize features (according to ROI) Pick release dates Give feedback Manage stakeholders Accept or reject results The Team : The Team Small (5–9 people) Colocated - Cross-functional Self-organized - Full-time picture by ewen and donabel The Team : The Team Define tasks Estimate effort Develop product Ensure quality Evolve processes Scrum Master : Scrum Master Servant leader Team protector Scrum guide picture by Orange Beard Scrum Master : Scrum Master Remove impediments Prevent interruptions Facilitate the team Support the process Manage management Pigs and Chickens : Pigs and Chickens Product Owner Scrum Master Team Members Users Managers Marketing Scrum Process : Scrum Process Product Backlog : Product Backlog Express value Defer decisions picture by juhansonin Product Backlog : Product Backlog sample sample from Eclipse.org Product Backlog : 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 Product Backlog : Product Backlog Includes rough estimates Prioritized by value & risk Publicly visible Better to describe as user stories User Stories : User Stories As a <user> I want <functionality>( so that <benefit> ) As a librarian I want to be able to search for books by publication year Sprints : Sprints Timeboxed – Frozen features Variable scope – Shippable result Sprint Planning : Sprint Planning Team capacity, Product backlog, Current product, Business, Technologies Goal = + + picture by Darcy McCarty Sprint Planning : Sprint Planning Face-to-face communication Small reversible steps User’s perspective Sprint Planning (Part 1) : Sprint Planning (Part 1) Strategical level planning Prioritize/select features Discuss acceptance criteria Verify understanding ½ - 1 hour per sprint/week Sprint Planning (Part 2) : 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 Sprint Backlog : Sprint Backlog Breakdown of business value into assignable tasks picture by oskay Sprint Backlog : Sprint Backlog sample Sprint Backlog : Sprint Backlog Owned by the team Team allocates work No additions by others Daily Scrum : Daily Scrum The heartbeat of Scrum picture by Hamed Saber Daily Scrum : Daily Scrum picture by Hamed Saber Commitment and accountability Say what you do, do what you say Whole world is invited Daily 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 Not to Scrum Master No problem solving Max 15 minutes Standing up Task Board : Task Board Definition of Done : Definition of Done Avoid the 90% syndrome Coded, commented, checked in, integrated, reviewed, unit tested, deployed to test environment, passed user acceptance test& documented... = DONE DONE Sprint Burn Down : Sprint Burn Down picture by NibiruTech Sprint Review : Sprint Review Satisfy Product Owner Get feedback on product picture by oskay Sprint Review : Sprint Review picture by oskay Informal, no slides Whole team participates The world is invited Sprint Review : Sprint Review Preparation needed Show complete features Accept or reject results 1-2 hours per sprint/week Sprint Retrospective : Sprint Retrospective Evolve the process picture by kevindooley Sprint Retrospective : Sprint Retrospective Reflect on process and product Whole team participates Sprint Retrospective : Sprint Retrospective What to start doing What to stop doing What to continue doing (Product Owner not required) Burn Down Chart : Burn Down Chart Scope change Burn Up Chart : Burn Up Chart Scope keeps expanding Pipeline gets fatter Release Planning : Release Planning Plan features in sprints and releases Releases depend on accepted sprints picture by Sviluppo Agile Release Sprints : Release Sprints Usability testing Documentation Help files Packaging pictures by VistaICO Sprint Termination : Sprint Termination Only in extreme cases Team terminates: cannot meet sprint goal Product Owner terminates: priority change Work reverted to end of prior sprint Raises visibility of problems picture by VistaICO Sprints : Sprints Steady pull of business value Inspect and Adapt picture by kelsey e. Sprints : Sprints picture by kelsey e. Driven by Product Owner Small reversible steps Welcome change Cross-functional team Include design and testing Maintain constant pace Share commitment High quality, DONE Get feedback “Fail fast” Hot Issues : Hot Issues Scrum vs. XP : Scrum vs. XP picture by extremeprogramming.org Scrum vs. RUP : Scrum vs. RUP picture by WittmannClan.com Scrum vs. Kanban : Scrum vs. Kanban picture by Lean Software Engineering Scaled Scrum(Scrum of Scrums) : Scaled Scrum(Scrum of Scrums) picture by Mountain Goat Software Distributed Scrum : Distributed Scrum Resultseffects ofapplying Scrum : Resultseffects ofapplying Scrum Managed Uncertainty : Managed Uncertainty Rolling wave planning Simpler mini-projects lowers risk Flexible Scope : Flexible Scope Allow changes at fixed intervals Releases enable learning Faster Delivery : Faster Delivery Shorter time to market Value delivered in increments Higher Quality : Higher Quality Testing happens continuously Process improvement built-in Eliminated Waste : Eliminated Waste Nothing is designed that is not built Nothing is built that is not used Increased Visibility : Increased Visibility All problems are made visible Progress is running tested software Preconditions : Preconditions Empowerment Discipline Courage Stamina Passion Coaching Stable Teams Cross-Functional Available Customer picture by mpov Disclaimer : Disclaimer No Engineering Practices Looks Simple, Is Hard No Silver Bullet Not Complete Takes Time picture by a2gemma Books : Books Sites : Sites www.scrumalliance.org www.controlchaos.com www.mountaingoatsoftware.com www.jeffsutherland.com www.implementingscrum.com www.agilesoftwaredevelopment.com www.noop.nl picture by VistaICO Q & A : picture by -bast- Q & A NOOP.NL : NOOP.NL This is my blog, go read it now! Slide 80: http://creativecommons.org/licenses/by-nd/3.0/ This presentation was inspired by the works of many people, andI cannot possibly list them all. Though I did my very best to attribute all authors of texts and images, and to recognize any copyrights. If you think that anything in this presentation should be changed, added or removed, please contact me at jurgen@noop.nl.