Planning horizon definition project management manual#
Therefore, this manual includes a simple example and shows how you can use the indented list to help you get started. Perhaps the main reason for this is that Project Managers don’t get time to cover this in the training.
The Product Breakdown Structure makes it easy to discuss the scope and requirements with the Senior User.įew Project Managers use the Product-Based Planning technique, especially the Product Breakdown Structure technique, which is a pity, as it is very useful. It is very easy for a project to start off as a simple project, but when you start to draw out the requirements in a Product Breakdown Structure, it shows exactly what this so-called simple project involves. One of the first things in planning is to try and get an idea of scope. You will find an example of a product checklist later in this Theme. This is easy to create, maintain and read and, most importantly, it is a good way to communicate with stakeholders that need this information. You could ask the Executive how they want to receive this status information (ask about previous projects).Ī good planning/tracking/reporting tool is the product checklist. , as they are not interested in reading a 20- to 30-page document. One good thing to keep in mind is how you will communicate the Project Plan to the So the Stage Boundary process can be used to create Product Descriptions for new products that will be created in the next stage. This is possible with some projects, but with many IT projects, a more relaxed approach is required and each stage can be an iteration. PRINCE2 might give the impression that you need to know everything upfront before you create the Projectįor all products. Project Managers who work in a Program Environment will be able to take advantage of how projects have been done in the past and get examples of how Project Plans are to be created.
0 kommentar(er)
