• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Life B4 and After Scrum
 

Life B4 and After Scrum

on

  • 1,610 views

Presented at Scrum Gathering Brazil 2009

Presented at Scrum Gathering Brazil 2009

Statistics

Views

Total Views
1,610
Views on SlideShare
1,385
Embed Views
225

Actions

Likes
1
Downloads
1
Comments
0

5 Embeds 225

http://www.i9web.com.br 201
url_unknown 13
http://www.linkedin.com 8
http://www.slideshare.net 2
http://www.lmodules.com 1

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

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

    Life B4 and After Scrum Life B4 and After Scrum Presentation Transcript

    • The life before and after Scrum
      Michel Goldenberg CSM/CSP
      Payam Afkari CSM
    • About this presentation
      This presentation talks about some cases showing the processes in the IT team before Scrum;
      How Scrum was implemented;
      Some problems that appeared during the implementation and how they were solved;
      What Scrum changed in the IT teams.
      2
      www.scrumusergroup.ca
    • Michel Goldenberg
      Agile Coach acting in Montréal area;
      Over 10 years of experience in IT;
      Expertise: Coaching people and implementing Scrum in big corporations.
      Cofounder of Montreal’s Scrum user group
      3
      www.scrumusergroup.ca
    • Payam Afkari
      Scrum Master and Business analyst in montreal area
      Close to 10 years in IT.
      Cofounder of Montreal’s Scrum user group
      4
      www.scrumusergroup.ca
    • The waterfall approach
      Etude opportunite
      Preliminary analysis
      Architecture
      Developpement
      testing
      Implementation
      Request for Change
      Add pictures
      www.scrumusergroup.ca
      5
    • The waterfall approach
      Requirement Gathering
      and analysis
      Client see for the first time
      System design
      Implementation
      testing
      Deployment
      Yes
      Maintenance
      Client
      approval
      RFC
      No
      New functionality
    • Used functionality
      www.scrumusergroup.ca
      7
    • From plan driven to value driven dev
      www.scrumusergroup.ca
      8
    • Scrum Framework
      Analysis
      www.scrumusergroup.ca
      9
    • www.scrumusergroup.ca
      10
    • Scrum Framework (vision)
      Analysis
      www.scrumusergroup.ca
      11
    • Vision
      Before: Client came with his vision and wanted his solution.
      After : the team works with the client to validate the needs and to come up with a better vision and solution
      www.scrumusergroup.ca
      12
    • Scrum Framework (Release planning)
      Analysis
      www.scrumusergroup.ca
      13
    • Release planning (Before)
      Project manager creates the plan and all the activities that he thinks is necessary.
      The activities are assigned to members .
      The release date is scheduled (imposed).
      Every body think they know their job for the project.
      www.scrumusergroup.ca
      14
    • Release Planning (After )
      A product backlog is created with the help of the client (product owner, PO);
      The PO prioritize the product backlog items;
      Team has an idea of what should be done;
      A release date can be proposed, based on the performance (velocity) of the team.
      www.scrumusergroup.ca
      15
    • Release planning - Challenges we went through
      Project manager wants to take control;
      Work on task instead of activities;
      Moving from a service provider to a partnership with the client;
      Identify a PO;
      Getting the client (PO) to work with the team;
      Client wants to sign a contracts;
      Client is hesitant.
      www.scrumusergroup.ca
      16
    • Release planning
      Release Plan
      Sprint 1
      Sprint 2
      Sprint 3 - 8
      Release planning
      www.scrumusergroup.ca
      17
    • Scrum framework (Sprint planning)
      Analysis
      www.scrumusergroup.ca
      18
    • Sprint planning (Before)
      Activity planning done by the Project manager.
      No such thing as sprint.
      No negotiation.
      www.scrumusergroup.ca
      19
    • Sprint planning (After)
      Team works with the client to prioritize the items that would be done in this sprint;
      Items broken into tasks;
      Evaluating the tasks;
      Commitment to deliver the sprint;
      Lots of room for negotiation.
      www.scrumusergroup.ca
      20
    • Sprint planning - Challenges we went through
      Explaining the value of Scrum;
      Changing the team spirit;
      Used to being told what to do;
      Trusting each other;
      Make developers to talk together;
      Working together.
      www.scrumusergroup.ca
      21
    • Sprint planning
      Sprint 1
      Sprint planning
      Story
      Story
      Sprint Plan
      Story
      Ongoing
      Done
      Planned
      Task
      Task
      Story
      Task
      Task
      Task
      Task
      Task
      Task
      Task
      Task
      Task
      Task
      Task
      Task
      www.scrumusergroup.ca
      22
    • The sprint backlog
      www.scrumusergroup.ca
      23
    • Scrum framework (sprint)
      Analysis
      www.scrumusergroup.ca
      24
    • Sprint (Before)
      No such thing as sprint;
      www.scrumusergroup.ca
      25
    • Sprint (After)
      Fewer features;
      Better quality;
      Suitable for the client;
      Easier to manage;
      Faster feedback;
      Team spirit.
      www.scrumusergroup.ca
      26
    • Sprint - Challenges we went through
      Not every one ready for sprinting;
      Members still need to be told what to do;
      Hero personality;
      Zero personality;
      Collaboration between team member;
      Team effort vs individual effort;
      Team commitment vs individual commitment.
      www.scrumusergroup.ca
      27
    • Scrum framework (Daily Standup)
      Analysis
      www.scrumusergroup.ca
      28
    • Daily Standup (Before)
      Not really daily standup;
      Not for the benefice of the team but rather for the PM management status;
      Scheduled and driven by the PM.
      www.scrumusergroup.ca
      29
    • Daily Standup(After)
      For the team;
      By the team;
      About the team;
      For a better product.
      www.scrumusergroup.ca
      30
    • Daily Standup - Challenges we went through
      PM trying to take control.
      PM interrupting the team.
      Members not speaking freely.
      Focus on what was done yesterday and what will be done today.
      Keep it short.
      Keep other discussion for later.
    • Scrum framework (Product Increment)
      Analysis
      www.scrumusergroup.ca
      32
    • Product increment (Before)
      www.scrumusergroup.ca
      33
    • Product increment (After)
      Team decide of the definition of Done;
      This definition helps up having a potentially shippable product;
      When ever the PO find it satisfactory, it can be shipped.
    • Product Increment - Challenges we went through
      • Definition of Done.
      • Focus on the story, even if the functionality is not complete.
      • Developer reaction, not adding to much fine tuning.
    • Framework(Sprint review)
      Analysis
      www.scrumusergroup.ca
      36
    • Sprint review (Before )
      www.scrumusergroup.ca
      37
    • Sprint review (After )
      Demo of working functionnality
      Assist client with future functionality decision
      Add/remove functionality
      Change priority
      Burndown chart
      Statistics/metrics
      Risk/Issues
      www.scrumusergroup.ca
      38
    • Sprint review (Challenges )
      Clients attitude. That’s what I want;
      Organising the presentation with the client’s busy schedule;
      Client’s feedback: Focus on important things;
      Client expectation (not finished functionality?);
      Controlling developers (planning bugs for next sprint).
    • Scrum framework (Sprint retrospective)
      Analysis
      www.scrumusergroup.ca
      40
      • At the end of the project when there is one.
      Sprint retrospective - Before
      www.scrumusergroup.ca
      41
    • Sprint retrospective - After
      Retrospection is the heart of Scrum – creating and responding to change about how the team will perform;
      Retrospective can occur anytime the team feels they need one.
      www.scrumusergroup.ca
      42
    • Questions
      www.scrumusergroup.ca
      43