Preparing For Sprint One

Like many others, I have used the principles of AgileSoftwareDevelopment for a number of years now. Every time I help set up a new project, I ask myself: What do I need to get into place before I begin the first sprint? (A sprint is a term from the ScrumMethodology which refers to a 2-4 week work period resulting in a fully integrated release.)

Preparing for sprint one will be the theme for the next meeting in DanishAgileUserGroup August 28th at Capgemini in Copenhagen. I want to see if I can assemble some good preparation patterns and maybe get others to contribute.

Feel free to make a contribution. Please state patterns that you have actually tried out yourself and report on your successes (or failures).

-- HenrikThomsen.

I have made some categories to get the ball rolling:

At the Copenhagen meeting we did a workshop based on Alistair Cockburn's Reflection workshop: Based on your experiences, what would you keep? What would you try in the next time period? And where did you have ongoing problems? We split the participants into two teams. One team would prepare for kick-off for a newly started project and the other team would convert an existing project into an agile project.

Here are the findings of the two teams:

New project

Keep

Try next time

Problems

Existing project

Keep

Try next time – motivation based approach

Problems


CategoryAgileMethodology


EditText of this page (last edited December 5, 2014) or FindPage with title or text search