We regard Processes as the bedrock for successful Project Management. Why? I think W. Edwards Deming said it best:
"If you can't describe what you are doing as a process, you don't know what you're doing"
Our Project Plans should describe how we intend to leverage and operate our organisation's Standard Processes - which should (hopefully) exist above and beyond the Project. And not just our Project Management Processes (Schedule/Cost Management etc) but the technical delivery aspects also.
So what's in a Process? A set of defined standard tasks which work together for a specific purpose, each of which have:
Processes permeate all PPM approaches in the industry, be it PMBOK, PRINCE2, M_o_R etc; at PHC we have experience and/or certifications in the many of these and work to leverage these to help you. Our Project Templates, when released, will align to these Industry Standard Processes to make your life easier - and your Projects more successful.
What is your experience of Processes? Can you think of any other things that need to be defined in a Process? I have had one idea I've been kicking around in my head...
Stay Healthy! Project Health Check - projecthealthcheck.org
To understand why do Projects Fail and what we need to do differently to stop it happening again.