Regardless is you work within a waterfall, RUP, Agile, Lean or any other methodology you have iteration periods. Every methodology call them differently, but they are all the same: a structured and somewhat planned period of time.
Rather than throwing in different names for these periods, like sprints or delivery cycles, we simply call them: "Iteration Periods". This way we can talk about this across the organization and everyone will know what you are talking about, or at least how that translate to their reality.
Iteration periods all follow the same basic structure:
- You take a moment to evaluate the previous iteration period
- You define work that you would like to focus on for the next iteration period.
- You ensure that the need of that work is described so that the people in charge of making reality of it feel comfortable taking over responsibility.
- You agree on the scope of the next iteration period, and together you start the new iteration period.
Depending on the methodology these steps may be more or less defined. For example in a Waterfall methodology the scope is well-defined with clear requirements. In an Agile Kanban methodology you focus less on scope and more on available time for say the next month of work. It is still the same four core activities you do: Evaluate, Define, Accept and Proceed.
Recommended Comments
There are no comments to display.
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now