Difference between revisions of "OOPM:Development:Documentation:IterationPlanning"
(cleared up the point on iteration feature development) |
|||
| Line 15: | Line 15: | ||
=== Feature Development === | === Feature Development === | ||
| − | When doing feature development, for example in our case during the initial prototyping phase, we will split the lot of tasks into small sets of tasks that can easily be accomplished during one iteration. Whilst most feature development tasks may required just one single iteration, multiple iterations can be defined so that more complex | + | When doing feature development, for example in our case during the initial prototyping phase, we will split the lot of tasks into small sets of tasks that can easily be accomplished during one iteration. Whilst most feature development tasks may required just one single iteration, multiple iterations can be defined so that more complex features a/o a resulting larger number of actual work tasks will be split between multiple such iterations in order to keep overall work requirement low incl. also the impact that a single iteration has on the overall product. |
| − | |||
| − | has on the overall product. | ||
| − | + | Therefore, for feature development we will use the issue tracker to capture the features, which themselves are based on our requirements analysis, that we have scheduled for the given iteration. We will then develop against those issues. However, as individual features, the APM calls these <nowiki>IterationFeatures</nowiki>, can be rather complex, we will create multiple work tasks as issues for these features. In the iteration statement we will only refer to the top level iteration features addressed by the given iteration. | |
TBD | TBD | ||
| Line 32: | Line 30: | ||
TBD | TBD | ||
| − | |||
=== Maintenance Development === | === Maintenance Development === | ||
Revision as of 16:04, 8 May 2009
Iteration Planning
As part of our development process, we will be using iteration planning in order to divide the existing work load (aka goals) into smaller portions,
- that can be tracked more easily
- where overall time requirements for the achievement of a goal is reduced to a maximum limit, so that it becomes affordable by all of the participating individuals
- where individual goals of one iteration are reduced so that they can be easily achieved by all of the participating individuals
- TBD
Bases on these iteration plans, aka the iteration statement, we will be coordinating our work.
For that purpose, a template was defined which we will use for authoring of iteration plans, namely Template:OOPM:Templates:Documentation:Development:ReleaseIterationStatement:1.0.
Feature Development
When doing feature development, for example in our case during the initial prototyping phase, we will split the lot of tasks into small sets of tasks that can easily be accomplished during one iteration. Whilst most feature development tasks may required just one single iteration, multiple iterations can be defined so that more complex features a/o a resulting larger number of actual work tasks will be split between multiple such iterations in order to keep overall work requirement low incl. also the impact that a single iteration has on the overall product.
Therefore, for feature development we will use the issue tracker to capture the features, which themselves are based on our requirements analysis, that we have scheduled for the given iteration. We will then develop against those issues. However, as individual features, the APM calls these IterationFeatures, can be rather complex, we will create multiple work tasks as issues for these features. In the iteration statement we will only refer to the top level iteration features addressed by the given iteration.
TBD
Software Feature Development
TBD
Documentation
TBD
Maintenance Development
When doing maintenance development, e.g. fixing issues with the existing releases in continued support or simply fixing issues with the newly developed features in a previously executed feature development phase, we will use a maintenance iteration statement.
Whilst maintenance is often just one iteration, with all the issues' solutions being the produces of such an iteration, multiple such iterations may exist during a single maintenance development phase. See feature development above.
TBD
Software Maintenance Development
TBD
Documentation Maintenance
TBD
