About Me

My photo
I am a Software Architect and Developer based in Bangalore, India. I have experience in building (scalable) applications using Java, JSP, JSF, JBoss Drools, Spring Framework, Hibernate, Ajax, JavaScript, MySQL, NoSQL (HBase, Project Voldemort). I am also a fan of Ruby on Rails, and have done some experimental work with it.

Wednesday, November 19, 2008

Scrum Adoption

I have initated adoption of Scrum in my team. To start with, we are trying to bring Scrum way of doing things in release and iteration planning.

We have had 2-week iterations in our project, and we have been having a release every 2 months. However, I felt that we have not been planning the work for iterations very effectively.

Now we have started to do following:

  1. Do a story point estimate of high level deliverables (Stories) for the 2 month phase of the project.
  2. Split the stories based on story points across the three 2-week iterations which we will have in 2 month release. One of the goals of allocating stories to various iterations is to ensure that we have equal distribution of story points across iterations.
  3. Break-up the stories selected for current iteration into tasks. For this, we create tasks on post-it notes, estimate each task in ideal hours, and then put it on task board.
  4. Team signs-up for tasks and moves them from "Not checked-out" to "Checked-out" status in Task boards.
  5. We have daily standup at afternoon 2.30PM. We discuss the status, plan for the day and also, move the completed tasks to "Done" status.
  6. We are doing pair-programming selectively wherever there is a need for knowledge exchange or tasks which we think need could be done faster if two members looked at it.

Yesterday, I presented the Scrum to the team. The slides were based on Mike Cohn's slides. While preparing for the presentation, I had a chance to read the Harvard Business Review , The New New Product Development Game, by Hirotaka Takeuchi and Ikujiro Nonaka. It's a great paper and I liked the parts where they talk about "Self-organizing teams" and "Multilearnings".

No comments: