PRINCE2 Project Management perspectives
The objective of this paper is to look at project management from a different perspective.
Are we managing projects or processes? You can learn all of this on a PRINCE2 Course Manchester.
This is probably the smartest question you will have to ask yourself. If we think in terms of processes, we’re still in the middle of the previous segment, but now we’re looking at projects.
There has been much written about the difference between a task and a project. A task is a group of related activities, grouped together under one name. A project is one or more activities taken together, with the ability to create a unique outcome or effect. Applications such as Construction Management, Human Resources Management, Supply Chain Management, and Project Management have all been derived from the standard project management concepts of Tasks and Projects.
We may want to refer back to the middle-age inventories in terms of project management (P3R22. It was again attributed to Market access.com). Those who done this out of school have pretty much accomplished this classification, but there is another clearly better way. Let’s look at a single element of two-step P3R22 (which we will refer to as P3R22 present):
If P3R22 is an objective-driven critical pathway that can be easily measured and monitored, how is it that P3R22 can not be a project? Why are tasks and activities not projects? And by the way, is this true of a pile of cash?
Looking at this in some different terms, in terms of productivity, P3R22 can be thought of as a process. We can think of P3R22 in terms of a series of processes in a hierarchy with a central process, which under the main process, will build products for products such as a sales department, and then again a process for the product they make, such as delivery. Each process in a series does something similar. Logging on to the company’s website can be a process. Then selling is another, and so on. The hierarchical design allows P3R22 to be a process even though the process of a pile of cash is a project.
Obviously this does not mean that a P3R22 process will be synchronous and functioning at its best throughout its duration, and in the end, rather than a product. This is the point, and the objective of a P3R22 process. We can debate whether this type of process is best for a P3R22 project, but until the project is formally completed, its potential cannot be fully used.
The conclusion that was reached from the analysis of the issue of “pushing or pulling” projects is that a P3R22 process can be the basis for a properly organized modern enterprise. If you take what P3R22 has to offer and apply it, it can take us far in our lives. It still remains the most efficient key to understanding enterprise processes and how those processes relate to processes of other entities.
©usspont relieve Ltd 2006
Thinking about an existing project as a series of tasks is a clear-cut definition of variables. So far, nothing else has been mentioned. We can go straight to the structure of a project.
All of the remaining gaps crumble and collapse as the efficacy of this model is demonstrated.
Resources are the necessary resource or assets in a project.
Some processes can not be compartmentalized. For example, a product code contains distinct people, associated with different codes.
Solution is a product. (the “M” in P3R22 means accordingly). This does not matter much if the product is nothing but solution. It can be a product even if there is not requisite resource to do that kind of function. Many projects ( minerals, fresh water and end users) have a system of solutions that do not appear to have any inherent resource (as opposed to a particular process) required to create it.
Need always latest about Project management? Keep eyes on Posting Tree