Hello All,
I will like to find out if you have any experiences to share around developing a software product delivery plan in an Agile environment? It will be great if you also have templates or samples to share to capture some inspiration / ideas.
Thanks
Jay
Software Product Delivery Plan for an Agile project
Planning and estimating in the agile world depend on a single key metric: the development team’s velocity, which describes how much work the team can get done per iteration.
Release deadlines are often fixed, imposed externally by such things as tradeshows, accounting pressures, or contractual obligations. But since the goal is to get working software into the users’ hands as quickly as possible in order to make “course corrections” as soon as possible, every effort is made to keep release software development cycles as short as possible.
Agile release cycles should certainly be kept shorter than a year, and are often as short as 6 months or 3 months. A release is, in turn, made up of iterations. For a given project, iteration length will typically be fixed at a length somewhere between a week and a month. If the release is in 6 months and iterations are going to be 2 weeks each, the release will consist of 13 iterations.
Release deadlines are often fixed, imposed externally by such things as tradeshows, accounting pressures, or contractual obligations. But since the goal is to get working software into the users’ hands as quickly as possible in order to make “course corrections” as soon as possible, every effort is made to keep release software development cycles as short as possible.
Agile release cycles should certainly be kept shorter than a year, and are often as short as 6 months or 3 months. A release is, in turn, made up of iterations. For a given project, iteration length will typically be fixed at a length somewhere between a week and a month. If the release is in 6 months and iterations are going to be 2 weeks each, the release will consist of 13 iterations.
jayashree thanks for your comment. Your contribution has been very useful. For our project, we as a team have decided to keep each iteration (Sprint) to two weeks and once we have a first release subsequent releases will be one-month intervals. Hence we deliver two iterations then a release takes place. What are your thoughts around these?