The Hungry Ant

Thoughts on product development in an agile environment

Wednesday, May 13, 2009

links for 2009-05-13

posted by Dharmesh  

Wednesday, May 13, 2009

Have a maximum of one or two sprint goals

When organising a sprint I would advise that there are only one or two goals. Sprints are not very long and by having few goals the team is never in doubt what needs to be done. It is also satisfying to think that something substantial has been completed. It improves motivation and projects seem to move along faster.

If the team is trying to do 5 big goals divided over 5 sprints it is better to do one goal at a time. It means you can also release early, keeping customers, stakeholders and teams happy.

I tend to write the sprint goals when doing the sprint planning meeting and have it visible next to the sprint backlog. This way everyone is clear on what needs to be done.

posted by Dharmesh  

Wednesday, May 6, 2009

links for 2009-05-06

  • A good source for those that have this ongoing debate in their brain. Python and Ruby are very similar and I will program with either depending on the projects needs , but so far Ruby wins for its elegance, pure coding haiku.
posted by Dharmesh  

Powered by WordPress