• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Scrum 18 months later
 

Scrum 18 months later

on

  • 3,018 views

Where are we 18 months after the teams adopted scrum. Where do we want to go?

Where are we 18 months after the teams adopted scrum. Where do we want to go?

Statistics

Views

Total Views
3,018
Views on SlideShare
2,720
Embed Views
298

Actions

Likes
3
Downloads
113
Comments
1

3 Embeds 298

http://www.betterprojects.net 294
http://translate.googleusercontent.com 3
http://seoautomated.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Scrum 18 months later Scrum 18 months later Presentation Transcript

    • Scrum18 months later
    • Learning framework
      Reference: Kolb Learning Cycle
    • Today’s agenda
      Why scrum?
      What works and what doesn’t?
      Why?
      Team roles and responsibilities
      Team capabilities
      So that we all understand our place in the project. And so that, while at work, we can be as happy and as effective as possible.
    • What gets measured gets done
      The difference between theory and reality
      Why are we using scrum?
    • For the next 10 minutes reflect on your past experiences.
      • Form into groups of 3
      • List all the project you have worked on and rate the team’s effectiveness as
      • Winners
      • Losers
      • Borderline
      • For each project what were the top 2-3 things that contributed to the success or failure of that project?
      • Highlight the common themes across your portfolio
      • Make a short-list of Dos and Don’ts for the rest of the team
    • Product Backlog = Focus, Next most important thing, Value first, Inventory management
      Story points = Sufficient Estimates, Avoids precise mistakes
      Sprints = Time boxed, End to end requirements to delivery
      Sprint plan = Commitment, Just in time planning, Last responsible moment, Work in progress (WIP) limits
      Stand-up = Team communications, Impediments and escalations, Focus on outcomes
      Burn down chart = A view of the team’s progress in the sprint, highlighting issues
      Sprint Review = Feedback from the customer, (Who is the customer? Hint: customers pay money.)
      Velocity = A view of how much work the team can get done, indicated milestones and release dates
      Burn up charts = A view of how much product has been built and how much is yet to be done
      Retrospective = Continuous learning, Focus on most important issues first (WIP limits), Manage via backlog?
      Roles = Accountability, All in, Single wring-able neck
      What’s different about scrum?
    • Source: http://www.targetprocess.com/blog/2008/09/waterfall-got-you-down-with.html
    • Source:http://www.scrumalliance.org/articles/133-challenging-inertia-through-scrum
    • How does you experience fit with scrum and the agile manifesto?
      Back into your group
      • Can you map your Do and Don’t recommendations into the scrum framework?
      • What is scrum missing?
    • Scrum and the Dos and Don’ts
      Product Owner
      Team Member
      Scrum Master
      Backlog,
      Burndown
      Built product
      1
      1
      2
      3
      2
      3
      Do this
      Don’t do this
    • How do values drive effectiveness?
      Manifesto
    • We are uncovering better ways of developing software by doing it and helping others do it.
      Through this work we have come to value:
      That is, while there is value in the items on the right, we value the items on the left more.
    • Principles behind the manifesto
    • Our highest priority is to satisfy the customerthrough early and continuous deliveryof valuable software.
      Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
      Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
      Business people and developers must work together daily throughout the project.
      Build projects around motivated individuals. Give themthe environment and supportthey need, and trust them to get the job done.
      The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
      Working software is the primary measure of progress.
      Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
      Continuous attention to technical excellence and good design enhances agility.
      Simplicity--the art of maximizing the amount of work not done--is essential.
      The best architectures, requirements, and designs emerge from self-organizing teams.
      At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly
    • What do we value
      • Do your values align to the values in the Agile Manifesto?
      • Are you living the values?
      • What are the gaps?
      • (Make a short list of the important ones)
      • Let’s review what we captured so far
      • The Do’s and Don’ts of projects
      • Does Scrum cover the ground?
      • What are the gaps?
      • Do I agree with the agile values?
      • Am I living them?
      • What can we do about this?
    • Roles and responsibilities on our program
    • Generalizing specialist
    • Our lovely little team
    • And the people we work with
    • What’s my role
      Work with your team at your table
      • Create a list of skills you can all bring to the project
      • Aggregate the many skills into a short capability statement
      • Share this with the rest of the team
      • Capture it in one sheet for the greater team
    • Next frontier
      Kanban/Lean
      [& the limited wip society]
      Agile
      Lean
    • Kanban
      Visualize the Workflow
      Limit Work-in-Progress
      Measure Flow
      Make Process Policies Explicit
      Use Models to Evaluate Improvement Opportunities
    • Individuals and interactions
      Process and tools
      Working product
      Comprehensive documentation
      To what extent do you agree with the values of the agile manifesto?
      Customer collaboration
      Contract negotiation
      Responding to change
      Rigidly following a plan
    • Individuals and interactions
      Process and tools
      Working product
      Comprehensive documentation
      To what extent do you practice values of the agile manifesto?
      Customer collaboration
      Contract negotiation
      Responding to change
      Rigidly following a plan


    • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
      Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
      Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
      Business people and developers must work together daily throughout the project.
      xx
      Build projects around motivated individuals. Give themthe environment and support they need, and trust them to get the job done.
      The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
      Working software is the primary measure of progress.
      xx
      Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
      Continuous attention to technical excellence and good design enhances agility.
      xx
      Simplicity--the art of maximizing the amount of work not done--is essential.
      xx
      The best architectures, requirements, and designs emerge from self-organizing teams.
      xx
      At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly
      Which of these principles do you love and which do you hate?
      No halfway here. Pick one or the other.
      The principles of the Agile Manifesto - www.agilemanifesto.org


    • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
      Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
      Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
      Business people and developers must work together daily throughout the project.
      xx
      Build projects around motivated individuals. Give themthe environment and support they need, and trust them to get the job done.
      The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
      Working software is the primary measure of progress.
      xx
      Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
      Continuous attention to technical excellence and good design enhances agility.
      xx
      Simplicity--the art of maximizing the amount of work not done--is essential.
      xx
      The best architectures, requirements, and designs emerge from self-organizing teams.
      xx
      At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly
      Which of these do you practice?
      The principles of the Agile Manifesto - www.agilemanifesto.org