User Tools
milestones_and_schedule
Differences
This shows you the differences between two versions of the page.
|
milestones_and_schedule [2014/01/03 16:33] hutch |
milestones_and_schedule [2014/03/17 14:03] (current) schultz |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Milestones, Schedule and Ownwership ====== | + | ====== Milestones, Schedule and Ownership ====== |
| - ** Milestones ** You will need to break your project down into a set of milestones. A project is broken down into a series of milestones in order to gauge progress and to break the project down into pieces that can be executed in parallel, as much as possible. Each milestone must be concisely described as a series of carefully-described tasks that can be executed by the responsible individual(s) with little or no need for further clarification. Milestones should be defined so that they have little interaction with each other and so that they follow the natural order required to complete the project. Note that testing and verification steps are an essential part of nearly all milestones. Once all of the milestones have been completed, the project should be completed. | - ** Milestones ** You will need to break your project down into a set of milestones. A project is broken down into a series of milestones in order to gauge progress and to break the project down into pieces that can be executed in parallel, as much as possible. Each milestone must be concisely described as a series of carefully-described tasks that can be executed by the responsible individual(s) with little or no need for further clarification. Milestones should be defined so that they have little interaction with each other and so that they follow the natural order required to complete the project. Note that testing and verification steps are an essential part of nearly all milestones. Once all of the milestones have been completed, the project should be completed. | ||
| - ** Schedule ** The milestones must be tied to a schedule that you will carefully monitor during the completion of your project. | - ** Schedule ** The milestones must be tied to a schedule that you will carefully monitor during the completion of your project. | ||
| - | - **Ownership:** Each milestone must be assigned to and owned by **one** person. They are responsible to see that the milestone is completed by the prescribed date. In cases where a milestone consists of multiple tasks that will be completed by multiple individuals, the owner of the milestone must ensure that each of the tasks are completed on time. | + | - **Ownership:** Each milestone must be owned by **one** person. They are responsible to see that the milestone is completed by the prescribed date. In cases where a milestone consists of multiple tasks that will be completed by multiple individuals, the owner of the milestone must ensure that each of the tasks are completed on time. |
| **Notes:** | **Notes:** | ||
| Line 9: | Line 9: | ||
| - Each milestone must contain a test/demo that, when executed, easily determines if the milestone was successfully completed. Important: this test/demo should be a go/no-go test. The outcome is pass/fail. | - Each milestone must contain a test/demo that, when executed, easily determines if the milestone was successfully completed. Important: this test/demo should be a go/no-go test. The outcome is pass/fail. | ||
| - The schedule can be described using a graphical-drawing program, a spreadsheet, etc. | - The schedule can be described using a graphical-drawing program, a spreadsheet, etc. | ||
| + | |||
| + | ===== System Overview ===== | ||
| + | {{:full_system.jpg?600|}} | ||
| + | |||
| + | ===== Milestones ===== | ||
| + | - Quick pass off | ||
| + | - Pass/fail | ||
| + | |||
| + | ====== Milestones ====== | ||
| + | |||
| + | [[Milestone 1]] | ||
| + | |||
| + | [[Milestone 2]] | ||
| + | |||
| + | [[Milestone 3]] | ||
| + | |||
| + | [[Milestone 4]] | ||
| + | |||
milestones_and_schedule.1388791983.txt.gz · Last modified: 2014/01/03 16:33 by hutch
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 3.0 Unported
