I'm not a fan of the term Sprint or Iteration for the mobilization of a project or product release as it often can take longer than the usual (1-4 weeks) duration of a sprint or iteration.
I prefer to call it a mobilization or inception phase and a lot depends on whether we are talking about a new product or an existing one.
In general, you'd see activities like:
- Define high-level scope and approach
- Secure funding
- Form team
- Create backlog
- Set up environments
- Develop test strategies
I highly recommend you avoid numbering the first sprint as zero. Many people are uncomfortable with the idea of a zero sprint precisely because it seems to imply the first sprint may be something less productive than later ones. It's not worth starting off with any bad feeling about such a trivial point: just start with Sprint One!
Begin with the highest level backlog items possible, for example around identifying goals, agreeing terms. If you don't already have the right PO or the right team as a whole then make identifying the right team one of the items in sprint 1. Keep sprint 1 short. Don't be tempted to make it overlong since it may well be counter-productive to plan much more than a week ahead at the beginning of a new piece of work. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
What have you set for your sprint goal? This should drive the value you expect to create, even if it's only building team dynamics. Saving Changes...
I agree with Kiron and Veronica. Those are likely the majority of activities. Saving Changes...
Latha Thamma reddiSr Product and Portfolio Management (Automation Innovation)| DXC TechnologyMckinney, Tx, United States
I too agree with Kiron and Veronica. Saving Changes...
Houssam AOUINADirector of PM/PMO| ICFGabes, Gabes, Tunisia
Hello everyone,
One important activity in iteration 0 is mitigating already identifed risks and integrating risk responses in the product backlog Saving Changes...
