• Like

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Introduction to Project Management with Scrum

  • 8,365 views
Uploaded on

It's a small presentation to give the basic principles of scrum. …

It's a small presentation to give the basic principles of scrum.
The presentation mode is made interactively with the audience.
The progression of the slides are scaled on progessive learning and fixing process: starting from theory to practice.

It's not enough to start a Scrum Project and do not replace a mature scrum training delivered by a senior Scrum Trainer.

More in: Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • Excellent presentation on scrum. Thank you!
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
8,365
On Slideshare
0
From Embeds
0
Number of Embeds
6

Actions

Shares
Downloads
1,263
Comments
1
Likes
20

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
  • RULES: No Mobile Phone 2 Feet Rule: your feel bored, it doesn’t meet your expectations, ... Feel free to leave. Emerging questions: Questions arise when they are. Interaction is the most important. Parking lot: some questions become they answer during the presentation and some are out of the scope. These are pushed in a Parking lot and I will give you the best answer I can at the end of the presentation.
  • Manifesto for Agile Software Development We are uncovering better ways of developing  software by doing it and helping others do it.  Through this work we have come to value: Individuals and interactions over processes and tools  Working software over comprehensive documentation  Customer collaboration over contract negotiation  Responding to change over following a plan  That is, while there is value in the items on  the right, we value the items on the left more. 
  • It’s an empirical Process Iterative & Incremental 3 Legs Transparency Inspection Adaptation “ Scrum is hard, but it sure is a whole lot better than what we were doing before!”
  • Chicken are involved. Pigs are committed.
  • Ensures that the team follows the values, principles and practices of Scrum. Helps the team and organization in the adoption of Scrum. Coaches and supports the team to improve productivity and quality. Protects the Team. Removes impediments. Responsible for the proper functioning of the project. There is only one ScrumMaster per team. The ScrumMaster is working with the team (ideally in the same room).
  • It’s the only responsible for Product Backlog’s management. Ensures the team’s created value: accepts or rejects the items according to the "Definition of Done." Maintains the Product Backlog and ensures that is visible from all. There is only one Product Owner per team The Product Owner works with the team (ideally in the same room).
  •  
  • Daily Scrum is ideally a stand-up meeting in front of the Scrum board.
  • the elevator test: "Can you explain your product in the time it takes to ride up in an elevator?" Moore (2006, p. 152).
  • Product Backlog Building: answer these questions: What? When? For Who? Product Backlog Management Clean the Backlog bottom from unused features (they can be added later if necessary) Ever keep in mind : is that really necessary? For Backlog Meeting: transcribe it on cards and stick up

Transcript

  • 1. Scrum by coPROcess
  • 2.
    • Scrum Coach & PMO
      • coPROcess S.A.
      • www.scrumcenter.lu
      • http://managingagile.blogspot.com/
    Scrum by coPROcess
  • 3. Scrum by coPROcess
  • 4.
    • Introduce you to Scrum
    • Explain the basic principles
    • Introducing Scrum Training possibilities
    Scrum by coPROcess
  • 5.
    • “ 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 Scrum by coPROcess
  • 6. Scrum by coPROcess
  • 7. Scrum by coPROcess 1995
  • 8. Scrum by coPROcess
  • 9. PO Training - Pierre NEIS 2001
  • 10.
    • 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 by coPROcess
  • 11. Scrum by coPROcess
  • 12.
    • 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.
    Scrum by coPROcess
  • 13. Scrum by coPROcess
  • 14.
    • 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
    Scrum by coPROcess
  • 15.
    • Each day, the Team measures its progress during a 15’ meeting: the Daily Scrum
    • During the whole project, the ScrumMaster ensures that 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.
    ❷ Scrum by coPROcess
  • 16.
    • The Sprint ends with the Sprint Review and the Retrospective .
    • When the next Sprint starts, the Team selects a new piece of the Product Backlog and restarts the process.
    • The process is done when all Features are implemented, or the budget is consummed, or when the time is over.
    Scrum by coPROcess
  • 17.
    • Maximize Value
    Scrum by coPROcess
  • 18. Scrum by coPROcess
  • 19. Scrum by coPROcess
  • 20. Scrum by coPROcess
  • 21. Scrum by coPROcess
  • 22. Scrum by coPROcess Self ManagingTeams Traditional Organization customer-driven management driven multi-skilled workforce workforce of isolated specialists few job descriptions Many Job Descriptions Information widely shared Information limited Few levels of management Many levels of Management Whole-business focus Function/department focus Shared goals Segregated goals Seemingly chaotic Seemingly organized Purpose achievement emphasis Problem-solving emphasis High worker commitment High Management commitment Continuous improvements Incremental improvements Self-controlled Management-controlled Values/principles based Policy/procedure based Source: "Leading self-directed work teams" by Kimball Fisher
  • 23.
    • Ensures
    • Helps
    • Coaches
    • Protects
    • Re moves
    • Responsible
    • Work with
    Scrum by coPROcess
  • 24.
    • Responsible
    • Ensures
    • Accepts
    • Rejects
    • Maintains
    • Work with
    Scrum by coPROcess
  • 25. Scrum by coPROcess
  • 26. Daily Meetings Scrum by coPROcess
  • 27. Scrum by coPROcess
  • 28. Scrum by coPROcess
  • 29.
    • Moderator: Product Owner
    • Participators: Team (active), ScrumMaster (passive)
    • Duration: 8 Hours for a 4 week Sprint
    • 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.
    Scrum by coPROcess
  • 30. Scrum by coPROcess
  • 31.
    • Moderator: Team
    • Participators : Team, ScrumMaster, Product Owner
    • Duration: 2-4 Weeks
    • 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.
    Scrum by coPROcess
  • 32. Scrum by coPROcess
  • 33.
    • Moderator: Team
    • Participators : Team (active), ScrumMaster (passive), Product Owner (passive)
    • Duration: 15 min
    • It is the Inspect-and-Adapt fromTeam: S ynchronization and Commitment.
    • The 3 Questions:
      • What did you do yesterday?
      • Which impediments?
      • ¨What do you plan for today?
    Scrum by coPROcess
  • 34. Scrum by coPROcess
  • 35.
    • Moderator: Product Owner
    • Participators: Team (active), ScrumMaster (passive), Management (active), Customer (active), Users (active)
    • Duration: 4 Hours for a 4 week Sprint.
    • 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 Product Owner accepts or rejects Sprint Backlog Items according to Definition of Done.
    • The Product Owner has the last word here.
    Scrum by coPROcess
  • 36. Scrum by coPROcess
  • 37.
    • Moderator: ScrumMaster
    • Participators: Team (active), ScrumMaster (active), Product Owner (active als Scrum Team Member)
    • Duration: 3 Hours for a 4 week Sprint.
    • Scrum Process Analysis:
      • How
      • How can we improve ourselves?
    • Inspection priorities :
      • Team communication
      • Relationship between team members
      • Processes and Tools
      • Training issues
      • etc
    Scrum by coPROcess
  • 38. Scrum by coPROcess
  • 39.
    • The Product Backlog answers following questions :
        • What? When? For who?
    Scrum by coPROcess
  • 40. Scrum by coPROcess
  • 41. Scrum by coPROcess
  • 42. Scrum by coPROcess
  • 43. Scrum by coPROcess
  • 44.
    • 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
    Scrum by coPROcess For the TEAM
  • 45.
    • 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
    Scrum by coPROcess For SCRUM
  • 46. Scrum by coPROcess
  • 47. Scrum by coPROcess
  • 48.
    • Transparence
    • Inspection
    • Adaptation
    Scrum by coPROcess
  • 49. Scrum by coPROcess
  • 50. Scrum by coPROcess
  • 51. Scrum by coPROcess
  • 52. Scrum by coPROcess
  • 53. Scrum by coPROcess
  • 54. Scrum by coPROcess
  • 55. Scrum by coPROcess
  • 56. Scrum by coPROcess Sprint Release Future Releases
  • 57. Scrum by coPROcess
  • 58. Scrum by coPROcess
  • 59. Developer Analyst Architect Tester DBA Anyone (not an authority role) Not necessarily a developer. Product Manager Business Analyst Functional Project Manager Business Scrum by coPROcess The Team Scrum Master Product Owner
  • 60. Scrum by coPROcess
  • 61. Scrum by coPROcess
  • 62.
    • 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/ Scrum by coPROcess
  • 63.
    • 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.
    Scrum by coPROcess
  • 64. Scrum by coPROcess
  • 65. Scrum by coPROcess
  • 66. Scrum by coPROcess That was my introduction to Project Management with Scrum
  • 67.
    • Thanks
    Scrum by coPROcess
  • 68. [email_address] Scrum by coPROcess