Difference between revisions of "User:Carsten.klein"
From Apache OpenOffice Wiki
(→Notice) |
|||
| Line 1: | Line 1: | ||
| − | |||
== Notice == | == Notice == | ||
Most of the below presented is actually more of a notice to myself than for actual public consumption. Be warned. | Most of the below presented is actually more of a notice to myself than for actual public consumption. Be warned. | ||
| + | |||
| + | == TODO == | ||
| + | |||
| + | ; Releaseplanning and Iterationplanning | ||
| + | : In accordance with the APM we should definitely go the route of ahead release planning and iteration planning | ||
| + | : what basically means that, that after we have captured all of the requirements in the requirements analysis document, | ||
| + | : we define the Release 1.0.0 stable stable features. From these features we will then derive the features to be implemented | ||
| + | : during the multiple iterations, the so-called iteration features. From these features then we will create the actual | ||
| + | : tasks that then will be managed in the central project plan. | ||
| + | : This requires that the currently defined [[Template:OOPM:Templates:Documentation:Development:ReleaseIterationStatement:1.0]] | ||
| + | : needs to be revised and extended see [[User_talk:Carsten.klein]] Launchpad for more information. | ||
== Offline Notices == | == Offline Notices == | ||
| Line 24: | Line 34: | ||
: based on processes/workflows, utilizing a processing engine in the backend, like for example the JBPM | : based on processes/workflows, utilizing a processing engine in the backend, like for example the JBPM | ||
* defining a basis for getting the real requirements analysis, based on a domain based analysis, up and running | * defining a basis for getting the real requirements analysis, based on a domain based analysis, up and running | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 05:40, 8 May 2009
Contents
Notice
Most of the below presented is actually more of a notice to myself than for actual public consumption. Be warned.
TODO
- Releaseplanning and Iterationplanning
- In accordance with the APM we should definitely go the route of ahead release planning and iteration planning
- what basically means that, that after we have captured all of the requirements in the requirements analysis document,
- we define the Release 1.0.0 stable stable features. From these features we will then derive the features to be implemented
- during the multiple iterations, the so-called iteration features. From these features then we will create the actual
- tasks that then will be managed in the central project plan.
- This requires that the currently defined Template:OOPM:Templates:Documentation:Development:ReleaseIterationStatement:1.0
- needs to be revised and extended see User_talk:Carsten.klein Launchpad for more information.
Offline Notices
Since I currently do not have any direct internet access at my home office, I will provide here a schedule of when I am not able to continue my work on the OOPM project on a more regular basis * 2009-04-11 - 2009-04-19
Current Work
Currently I am working on getting the OOPM project up to speed by
- developing an infrastructure incl. templating in the wiki for future documentation purposes
- making up an initial architecture proposal for the OOPM application, or rather "the solution", based on former research done for a similar project
- of mine, called the hpm, a hierarchical, multi project management solution, featuring inter-project dependencies and so on, which is inherently
- based on processes/workflows, utilizing a processing engine in the backend, like for example the JBPM
- defining a basis for getting the real requirements analysis, based on a domain based analysis, up and running
