Defining The Project's Goal
Stephen Brown <[email protected]> Sat, 08 Dec 2007 11:45:19 +0100
| Newsgroups | gmane.org.osaf.design |
|---|---|
| Message-ID | <[email protected]> |
What would also be nice is a way to define an end point to a task, event or message item such that we all know when it has reached its end. Along with creating start and stop times, what is needed isa way to manage the goals (aka milestones) of the project. We can sort of do that now in the notes field but there is no accountability associated with that. I would rather have the ability to produce milestones in addition to my "notes" or text field associated with a task or event. This would permit a percentage completion calculation based upon a mathematical count of the real work items (milestones) within the goal, not that mythical percentage completed beast that Outlook has for its task management. For example, if completion means a) draft the letter, b) send it to the supplier c) get price d) arrange meeting with supplier e) issue purchase order f) received and installed = completed. This collection of project tasks and events has 6 core milestones. There may be many more items added by the team but as long as these milestones are met, we all collectively know how far along we are. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design