 Project planning/controlling
|
 |
|
|
|
The "classic principles" of project management apply to e-projects, too |
|
 |
|
stdSEM project planning/project controlling |
Arguments such as "the project is so small, so why..." or "it's just not possible to arrive at stable requirements..." are no excuse to just turn your back on project planning and controlling. In e-projects, the main thing is to find a well-balanced approach to project planning and controlling: Simple "to do" lists and the ticking off of completed work packages are often better suited than complex plans that need to be continually updated. It is important in this context to use project planning as a shared medium of communication with the customer. |
|
 |
|
Project Management Support Center
(German) Professional project support, recommendable especially for larger projects |
Setting up project planning in the Definition phase |
|
|
|
|
Start project planning already when drawing up the tender (in the Definition phase). In most cases, it is better to plan only the next few steps in detail (cycles of a release) and provide only preliminary planning for later cycles and further releases at this time (at the beginning of the project).
What is particularly important is to quickly build up a competent core team for development.
Naturally, the client/end customer is involved in defining and prioritizing the requirements. This implies that the client/customer must be involved in the key issues of release planning, the planning of coordination cycles, preparation of the Operations phase, as well as system/acceptance testing.
|
|
|
|
Change Management Setting
up a change management process early on is particularly important with
short release cycles |
|
|
Claim management is important right from the start if the client/end customer is closely involved in activities right from the start |
|
|
|
|
|
|
What steps need to be taken? |
|
|
|
|
On the basis of the "classic" planning approach (first component planning, then planning of work volume, work packages, and staff assignment), the harmonization of specifications regarding the planned deadlines and the key functions is important. Statements made by the client of a "The only thing that is certain is the final deadline" nature must be taken seriously and require a "creative" solution approach (deadlines frequently leverage the prioritization of functions and release planning). Special attention needs to be paid to the planning and controlling of products and services to be supplied by external parties (as this frequently turns out to be a problem during the course of the project). |
|
|
|
|
|
|
|