Showing posts with label Scrum. Show all posts
Showing posts with label Scrum. Show all posts

Friday, November 5, 2010

First Sprint in Review

Wow it is hard to believe that it has been two weeks and we have finished our first Sprint.  Here is how it came out.

Committed Tasks
We completed all but a couple of the tasks we committed in the Sprint.  We under estimated the few learning curves that were introduced by our new environment which caused delays early in the Sprint.

Review (Demo)
Everyone demonstrated the features that they worked on during the Sprint.  We all knew what to expect because we were all involved in the planning process.

Retrospective
We noticed a few things that we would change in the next Sprint.

  1. Use the Work Remaining field on the TFS Tasks to help us better gauge progress and future planning.
  2. When UI elements are "done", gather the team for a quick demo.
    • We want to collect input early to provide a better polished product at the end of the Sprint.

The formal structure and Daily Scrum is welcomed by the team.  If you are not already using an agile process like Scrum, give it a try - you will be surprised with the results.

Monday, October 25, 2010

New Project - Welcome Scrum

Before today, we were working in an informal agile process with fairly short development cycles. We work as a team but often developers would be unaware of new features that others were working on. A big problem with this is that it makes it difficult for another team member to pick up where someone left off.

Enter our new project, code name Nucleus.  Dave and I have been planning for a few months the vision and features of the project and we formally kicked it off today - Hooray!  We were introduced to a new project process called Scrum through Visual Studio 2010 and Telerik's Team Pulse product.  Scrum is an agile practice that gets the entire team involved in nearly the entire process from planning to tasks to conducting demos of the work completed.

With our first stab of Scrum, we will start with the following 2 week Sprint Schedule.
  • Day 1: Sprint Planning Meetings
    • Part I (4 hours max): Participants include Product Owner and Scrum Master
      • Determine focus of the Sprint and flag possible Sprint Backlog items
    • Part I (4 hours max): All Team Members participate
      • Discuss in detail each flagged Sprint Backlog item
        • Use Scrum Poker to estimate effort
      • Determine actual Sprint Backlog and assign work to team members
  • Day 2-10Daily Sprint Meeting (15 minute max)
    • Team members answer:
      • What have you done since the last meeting?
      • What will you do from now until the next meeting?
      • Is there anything holding up your work?
  • Day 6Requirements Planning (4 hour max)
      • Participants include Product Owner and Scrum Master
        • Add and edit the Product backlog
        • Additional stakeholders may be invited
  • Day 10: Sprint Review and Retrospective (4 hour max)
    • Demo functionality added from the Sprint.
    • Reflect on the Sprint to determine what worked, what didn't work and what would we change in the next Sprint.
Additionally we sprinkled into Sprint a few formal code reviews.

We had an outstanding Day 1 in our first ever Sprint.  We played a little Scrum Poker, talked about backlog items and by the end of the day we all had our tasks outlined for the rest of the Sprint.

Links