You should already know that you have a project and you can do some planning to get things done – From the previous post – Project Management 101.
Now moving swiftly along…
There are many standards and approaches available to manage projects: (From wikipedia)
Approaches
- The traditional approach
- PRINCE2
- PRiSM (Projects integrating Sustainable Methods)
- Critical chain project management
- Event chain methodology
- Process-based management
- Agile project management
- Lean project management
- Extreme project management
International Standards
There have been several attempts to develop project management standards, such as:
-
GAPPS, Global Alliance for Project Performance Standards – an open source standard describing COMPETENCIES for project and program managers.
-
HERMES method, Swiss general project management method, selected for use in Luxembourg and international organizations.
-
The ISO standards ISO 9000, a family of standards for quality management systems, and the ISO 10006:2003, for Quality management systems and guidelines for quality management in projects.
-
Association for Project Management Body of Knowledge
-
Team Software Process (TSP) from the Software Engineering Institute.
-
Total Cost Management Framework, AACE International’s Methodology for Integrated Portfolio, Program and Project Management.
-
V-Model, an original systems development method.
-
The Logical framework approach, which is popular in international development organizations.
-
IAPPM, The International Association of Project & Program Management, guide to project auditing and rescuing troubled projects.
For clarity sake we will only delve into one of these “flavours” of project management – Project Management Institute (PMI). The most important next step in your discovery of what project management is revolves around phases.
The phases are intended to allow us mortal beings to group things together logically that will allow us the greatest chance of succeeding. We have to remember that some learning and bitter experiences have contributed to the knowledge that constitutes the groupings.
Initiation
You have to know a few things before you really start to attack a project. These things are absolutely vital to the success of the project.
- What MUST the project achieve (not from the project’s view, but from the client’s view).
- How much funds is available to achieve what (and how will you be able to get it – what does the project have to do)?
- Who are the people involved (probably the list of stakeholders already identified in Project Management 101)?
- Get written signed approval of your understanding of what the project has to achieve (project charter).
Planning and Design
We have discussed planning before, why again now? In Project Management 101 we explained planning to give you enough detail to define the project. In this phase you will have to plan to achieve the results… You have to plan to an “appropriate level of detail” to allow you to manage project risk by estimating the time, resources, cost and other factors that will affect the chances of delivering the project successfully. (more on project planning)
Executing
Do the work that you said that you were going to do in the planning phase. This is where the tyre hits tar, things get serious and things will have to happen…
- People will have to know who does what when, why and for how long…
- They have to work hard (I can almost guarantee you that you will not have enough time or people to get all the stuff done),
- They will have to be accurate and precise (cannot re-do stuff here),
- You will have to do it cheaply (yes, I know – haha).
Monitoring and Controlling
You have to constantly evaluate what people are doing…
- Is it in line with what has been specified?
- How do we overcome this unanticipated problem?
- If we lose time doing this, how do we get it back?
- If that thing now cost more than what we were told, how do we recover the extra expenditure?
- If we pay more for a better person, will we save enough time to make it worth our while?
- How does the client perceive all the activity?
Closing
One of three things will cause a project to close:
- Achieved all of the project deliverables (YAY….. )
- Stopped due to requirements shift (the reason why the project existed has changed or disappeared)
- Will never reach the project deliverables (many reasons within and external to project can cause this)
Remember any project you can walk away from…
To give you some idea of how projects will tax you as they move through the phases, the line drawing below is a good approximation of how most projects behave.
Phew… Glad that’s over with… So I’m a fully-fledged project manager now?
Well yes and no…
To be a project manager you have to know a little bit of each of these:
The nine knowledge areas are:
- Project Integration Management
- Project Scope Management
- Project Time Management
- Project Cost Management
- Project Quality Management
- Project Human Resource Management
- Project Communications Management
- Project Risk Management
- Project Procurement Management
We will look at this next time…
Have a fantastic day…
Related articles
- Project Management Templates Review Released to Help Professionals… (prweb.com)
- Is it Possible to Do More Project Management with Less? (fearnoproject.com)














Hi Anton,
I’m not sure whether PRISM should be considered a project management approach. Also, where is the PMBOK?
Hi,
Thank you for the comment.
I agree that it may be ambitious to call PRISM an approach but I showed the content the way is is portrayed by Wikipedia.
PMBOK is explored during the remainder of the post and they list it as a standard.
I hope that you could enjoy the rest of the article though…
Have a great day
PRiSM is most definately an approach. See the whole process flow http://www.greenprojectmanagement.org/prism
Project management is always overlooked, Having a good relationship with your team is essential. It allows clear communications both ways. And lead by example is also important. – my two cents