Posted by: Rajesh Kanaparti | March 15, 2008

Scrum, an agile process of playing software development game

So in the last post I talked about roles that are played in scrum and there responsibilities and the kick off meeting. Kick off meeting is where the work that has to be done in the next sprint is decided. A sprint is typically a 30 day iteration where the work to be done is fixed and no new work is going to be added or re-prioritized.

The kick off meeting is typically going to be all day.For the first 4 hours, the product owner is going to prioritize the items from the product log and identifies what items need to be completed in next sprint.The next 4 hours, the team gives there rough estimates on the items that the product owner wants for the next 30 days. If the estimated time is going to take more time than 30 days, then the items are prioritized and the lower priority items are pushed back to product backlog. Here you go this is how you get the sprint backlog on which the team is going to work and the scrum master will track. Once again, the team is going to work only on the items , no new features are going to be added or no prioritization. Also as a practice of IID ( Iterative Incremental development), the time-box for the sprint is fixed and it cannot be changed.Another note, when estimating the work and time required for features, the estimates must include time for analysis, design, development, testing, and documentation. No item can be accepted as complete without completing all the above items.

The idea is at end of the sprint, the product should be stable and should be able to release to production if needed to be released. Just think some of the advantages of achieving the ability to release. Client can see the product in short iterations and they have the chance to come up with feedback or cut features or add features that increase ROI for the next coming sprint. This is what is missing in waterfall methodology.

Well now you have an idea of what is achieved in sprint kick of meeting. In the next post, I will talk about how the scrum master is going to track the progress of work being done to complete the items accepted for this sprint.

Advertisements

Responses

  1. One comment about the purpose of Sprint Planning 1 and 2. It is a common misunderstanding to believe that Sprint Planning 1 is about estimation of Backlog Items. The purpose of this meeting is to have a detailed analysis session: You generate the requirements, the test cases, the user acceptance tests, etc in this session. The commitment of the development team is based on their detailed knowledge about what to do.

    Purpose of Sprint Planning 2: The design – you sit together and you work out every step that needs to be done, by acutal designing and planning how to do the stuff.


Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s

Categories

%d bloggers like this: