Scrum@accenture

  • 11,569 views
Uploaded on

Theses are the slides from the scrum Workshop at Accenture's PMO in Amsterdam, January the 5th 2011.

Theses are the slides from the scrum Workshop at Accenture's PMO in Amsterdam, January the 5th 2011.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
11,569
On Slideshare
0
From Embeds
0
Number of Embeds
5

Actions

Shares
Downloads
1,188
Comments
0
Likes
25

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Introduction to Project Management with Scrum 1 Scrum@ AccentureTechnology Solutions | PCS
  • 2. Who am I? Scrum@ Accenture Technology Solutions | PCS PMO │ Scrum Coach @ coPROcess S.A. www.coprocess.lu http://managingagile.blogspot.com/ http://paper.li/elPedroMajor 2
  • 3. About this Workshop Scrum@ Accenture Technology Solutions | PCS 3
  • 4. Objective Introduce you to Scrum Explain the basic principles Introducing Scrum Training possibilities Scrum@ Accenture Technology Solutions | PCS 4
  • 5. The Process !!! Scrum@ Accenture Technology Solutions | PCS 5
  • 6. Inspect & Adapt 3 questions: Whoam I? What’smy job? Whataimstoday? Scrum@ Accenture Technology Solutions | PCS 6
  • 7. Introduction to Scrum Scrum@ Accenture Technology Solutions | PCS 7
  • 8. 8 Scrum@ Accenture Technology Solutions | PCS Why “Scrum” ?
  • 9. We’re losing the relay race “The… ‘relay race’ approach to product development…may conflict with the goals of maximum speed and flexibility. Instead a holistic or ‘rugby’ approach—where a team tries to go the distance as a unit, passing the ball back and forth—may better serve today’s competitive requirements.” Hirotaka Takeuchi and Ikujiro Nonaka, “The New New Product Development Game”, Harvard Business Review, January 1986 9 Scrum@ Accenture Technology Solutions | PCS
  • 10. Origins Scrum@ Accenture Technology Solutions | PCS 10
  • 11. The Manifesto for Agile Software Development 2001 Scrum@ Accenture Technology Solutions | PCS 11
  • 12. Introduction by Ken Schwaber Scrum is not a methodology. Scrum does not provide the answers to how to build quality software faster. Scrum is a framework within which the game of product development is played. Your team plays and how good or not-good it is becomes highly visible. Your team gets to continuously improves itself. Scrum@ Accenture Technology Solutions | PCS 12
  • 13. 13 Scrum@ Accenture Technology Solutions | PCS How?
  • 14. Scrum is an innovative approach to complete your work Scrum is a flexible framework for complex projects. Originally Scrum has been formalized for software development. But it also works well for complex and innovative projects. The Scrum framework is deceptively simple. 14 Scrum@ Accenture Technology Solutions | PCS
  • 15. The Theory Scrum@ Accenture Technology Solutions | PCS 15
  • 16. Scrum Framework The Product Owner sets a List of Features called Product Backlog During the Sprint Planning, the Team “pulls” a piece of the top of that list: the Sprint Backlog; and decide how to implement it. The Team has a time-box to reach this goal: the Sprint ❶ 16 Scrum@ Accenture Technology Solutions | PCS
  • 17. Scrum Framework Each day, the Team measures its progress during a 15’ meeting: the Daily Scrum During the whole project, the ScrumMaster ensuresthat the Team is still focused on its objective. At the end of the Sprint, the work has to be potentialy shipable. This work is considered as done. ❷ 17 Scrum@ Accenture Technology Solutions | PCS
  • 18. Scrum Framework The Sprint ends with the Sprint Review and the Retrospective. When the next Sprint starts, the Team selects a newpieceoftheProductBacklogandrestartstheprocess. The processisdonewhen all Features areimplemented, orthebudgetisconsummed, orwhenthe time isover. ❸ 18 Scrum@ Accenture Technology Solutions | PCS
  • 19. Objective Maximize Value 19 Scrum@ Accenture Technology Solutions | PCS
  • 20. Scrum Roles 20 Scrum@ Accenture Technology Solutions | PCS
  • 21. Pigs & Chicken 21 Scrum@ Accenture Technology Solutions | PCS
  • 22. ❶ The Scrum Team 22 Scrum@ Accenture Technology Solutions | PCS
  • 23. 23 Scrum@ Accenture Technology Solutions | PCS ❷ The Team
  • 24. Self-Managed-Team vs. Traditional Organisation 24 Scrum@ Accenture Technology Solutions | PCS
  • 25. ❸ ScrumMaster Ensures Helps Coaches Protects Removes Responsible Workwith 25 Scrum@ Accenture Technology Solutions | PCS
  • 26. ❹ Product Owner Responsible Ensures Accepts Rejects Maintains Work with 26 Scrum@ Accenture Technology Solutions | PCS
  • 27. Cycle of Ceremonies 27 Scrum@ Accenture Technology Solutions | PCS
  • 28. Ceremonies are time-boxed. Sprint Planning Sprint Review Retrospective Sprint Planning Daily Meetings SPRINT 28 Scrum@ Accenture Technology Solutions | PCS
  • 29. ❶ Sprint Planning Meeting 29 Scrum@ Accenture Technology Solutions | PCS
  • 30. 30 Scrum@ Accenture Technology Solutions | PCS The “Pull” Principle
  • 31. ❶ Sprint Planning Meeting 2 Parts: Sprint Planning 1: the WHAT? Sprint Planning 2: the HOW? Product Owner: Provides the customer ‘s/ user’s prioritized product backlog Presents the Release Plan. Explain theVision Team: Estimates the Product Backlog in terms of feasibility (functional estimation) Slice the Product Backlog to Sprint Backlogs with Product Owner Slice Sprint Backlog in Tasks Team and Product Owner: Define the Sprint objective Establish “Definition of Done” for the Sprint. Moderator: Product Owner Participators: Team (active), ScrumMaster (passive) Duration: 8 Hours for a 4 week Sprint 31 Scrum@ Accenture Technology Solutions | PCS
  • 32. ❷Sprint 32 Scrum@ Accenture Technology Solutions | PCS
  • 33. ❷Sprint Development of the applications from the Sprint Backlog in which the team is involved. Maintenance of the Level of Done: Developement Unit test Acceptance Integrations test System tests Performance Co-management of impediments with the ScrumMaster. Co-maintenance of the Sprint Backlog with Product Owner. Moderator: Team Participators : Team, ScrumMaster, Product Owner Duration: 2-4 Weeks 33 Scrum@ Accenture Technology Solutions | PCS
  • 34. ❸ Daily Scrum 34 Scrum@ Accenture Technology Solutions | PCS
  • 35. ❸ Daily Scrum It is the Inspect-and-Adapt fromTeam: Synchronizationand Commitment. The 3 Questions: What did you do yesterday? Which impediments? ¨What do you plan for today? Moderator: Team Participators : Team (active), ScrumMaster (passive), Product Owner (passive) Duration: 15 min 35 Scrum@ Accenture Technology Solutions | PCS
  • 36. ❹Sprint Review 36 Scrum@ Accenture Technology Solutions | PCS
  • 37. ❹Sprint Review It is the Inspect-und-Adapt from Customer, Users and Management. The team presents the results of the Sprint. Users/Customer/ Management express their comments and find a compromise with the team. The ProductOwneracceptsorrejects Sprint Backlog Items accordingto Definition ofDone. The Product Owner has the last word here. Moderator: Product Owner Participators: Team (active), ScrumMaster (passive), Management (active), Customer (active), Users (active) Duration: 4 Hours for a 4 week Sprint. 37 Scrum@ Accenture Technology Solutions | PCS
  • 38. ❺Retrospective 38 Scrum@ Accenture Technology Solutions | PCS
  • 39. ❺Retrospective Scrum Process Analysis: How How can we improve ourselves? Inspection priorities : Team communication Relationshipbetweenteammembers Processes and Tools Training issues etc Moderator: ScrumMaster Participators: Team (active), ScrumMaster (active), Product Owner (active als Scrum Team Member) Duration: 3 Hours for a 4 week Sprint. 39 Scrum@ Accenture Technology Solutions | PCS
  • 40. Artifacts 40 Scrum@ Accenture Technology Solutions | PCS
  • 41. Product Backlog The ProductBackloganswersfollowingquestions: What? When? For who? 41 Scrum@ Accenture Technology Solutions | PCS
  • 42. Release Burndown 42 Scrum@ Accenture Technology Solutions | PCS
  • 43. Sprint Backlog 43 Scrum@ Accenture Technology Solutions | PCS
  • 44. Sprint Burndown Scrum@ Accenture Technology Solutions | PCS 44
  • 45. Definition of Done 45 Scrum@ Accenture Technology Solutions | PCS
  • 46. Level of Done For the TEAM Code corresponds to the standard Code is proper Re-factored Unit tested checked in built Has a number of applied unit tests. To achieve this, the development environment is constituted by : A Source-Code Library Codes Standards Automatic Build A Unit-tests Environment 46 Scrum@ Accenture Technology Solutions | PCS
  • 47. Definition of Done For SCRUM A Story/Item is “done” when theTeam has reached its Level-of-Done. Sprint/Iteration is “done” when All items are “done” When the Sprint reaches its goal. And when Acceptance criteria are met. Release is “done” “done” for Integration “done” for Production 47 Scrum@ Accenture Technology Solutions | PCS
  • 48. Done? Half done is not done 48 Scrum@ Accenture Technology Solutions | PCS
  • 49. Scrum Values Scrum@ Accenture Technology Solutions | PCS 49
  • 50. Tranparence Transparence Inspection Adaptation 50 Scrum@ Accenture Technology Solutions | PCS
  • 51. Scrum@ Accenture Technology Solutions | PCS Inspection 51
  • 52. Scrum@ Accenture Technology Solutions | PCS Adaptation 52
  • 53. In fact, how does it work? 53 Scrum@ Accenture Technology Solutions | PCS
  • 54. First an idea 54 Scrum@ Accenture Technology Solutions | PCS
  • 55. Then a Vision 55 Scrum@ Accenture Technology Solutions | PCS
  • 56. The Vision 56 Scrum@ Accenture Technology Solutions | PCS
  • 57. Then a Product Backlog 57 Scrum@ Accenture Technology Solutions | PCS
  • 58. Product Backlog High priority Sprint Medium Priority Release Future Releases Scrum@ Accenture Technology Solutions | PCS 58
  • 59. Product Backlog - Examples Scrum@ Accenture Technology Solutions | PCS 59
  • 60. Then build the Team Scrum@ Accenture Technology Solutions | PCS 60
  • 61. Team Building Product Owner Product Manager Business Business Analyst Functional Project Manager Scrum Master Architect Anyone (not an authority role) Not necessarily a developer. The Team Developer DBA Analyst Tester 61 Scrum@ Accenture Technology Solutions | PCS
  • 62. Scrum Cycle 62 Scrum@ Accenture Technology Solutions | PCS
  • 63. Scrum Principles Summary Scrum@ Accenture Technology Solutions | PCS 63
  • 64. Planning Game Scrum@ Accenture Technology Solutions | PCS 64 45’ immersion in Scrum
  • 65. Exercise: Deliver a brochure for the Earth Tourist Board located on Mars Create cover art, brand, and/or logo Define major topics for Martian Tourism Describean “Art Interestsin Europe” tour Describe a tour based on Photosynthesis Outline a “7 wonders of the world” Expedition Set prices for the tours Outlinewarning messages (gravity, oxygen, fungi, etc.) Suggestclothing options Explain travel options to/from Mars Describe a “Human Sports” tour Outlinerefundpolicy Suggestrelated services Defineadvertisers Definea 12-monthcampaign Set-up how to get more information Scrum@ Accenture Technology Solutions | PCS 65 You have 45’
  • 66. Setting up a Q/A Scrum@ Accenture Technology Solutions | PCS 66 15’  build a Q/A Backlog 15’  estimate & prioritize 30’  deliver
  • 67. Scrum Trainings Scrum Alliance Certified ScrumMaster Certified Product Owner Certified Scrum Developer Certified Scrum Professional Certified Scrum Trainer Certified Scrum Coach Scrum.org http://www.scrum.org/ Professional Scrum Master Professional Scrum Master 1 Professional Scrum Master 2 Professional Scrum Developer PSD .Net PSD Java http://www.scrumalliance.org/ 67 Scrum@ Accenture Technology Solutions | PCS
  • 68. My Trainings Basics : Introduction to Scrum ScrumMaster in depth Training Product Owner in depth Training Coaching Scrum Teams Hyper Productivity & Rapid Scrum ScrumBan Scrum Certification on-demand “Short Tracks”: Format: 4 Hours, 4 Trainees, 1 Problem, 1 Solution, 1 Example, 1 Counterexample, 1 Tool, 1 Template Themes: PID, ROI, Scaling Teams, Visual Management, Visioning, Scrum Tools, Magic Estimation. 68 Scrum@ Accenture Technology Solutions | PCS
  • 69. Scrum Resources 69 Scrum@ Accenture Technology Solutions | PCS
  • 70. Companies using SCRUM 70 Scrum@ Accenture Technology Solutions | PCS
  • 71. That was my introduction to Project Management with Scrum 71 Scrum@ Accenture Technology Solutions | PCS
  • 72. Thanks 72 Scrum@ Accenture Technology Solutions | PCS
  • 73. pneis@coprocess.lu 73 Scrum@ Accenture Technology Solutions | PCS