Change Management Plan Template Pmbok Project Change Management Plan Template: Fill & Download for Free

Good question - In my opinion, the most common denominator behind what is called “The Nine Deadly Sins of Project Management” is failing to fit the methodology and the project management approach to the nature of the project.Many project managers use a “cookbook approach to project management” that is based on:Force-fitting all projects to a standard plan-driven project management methodologyUsing standardized checklists based on PMBOK and other sources for project management and risk managementUsing fill-in-the-blanks document templates for creating project documentationThese project managers typically get lost in the “mechanics” of doing project management and become absorbed in completing documentation and other project artifacts and lose sight of the primary goal of making the project successful.In my latest book on Agile Project Management, I use the analogy of a project manager as a “cook” versus a “chef”. I think that analogy fits pretty well.“A good ‘cook’ may have the ability to create some very good meals, but those dishes may be limited to a repertoire of standard dishes, and his/her knowledge of how to prepare those meals may be primarily based on following some predefined recipes out of a cookbook.”“A ‘chef’, on the other hand, typically has a far greater ability to prepare a much broader range of more sophisticated dishes using much more exotic ingredients in some cases. His/her knowledge of how to prepare those meals is not limited to predefined recipes, and in many cases, a chef will create entirely new and innovative recipes for a given situation. The best chefs are not limited to a single cuisine and are capable of combining dishes from entirely different kinds of cuisine.”The way that we do traditional plan-driven project management hasn’t changed significantly since the 1950’s and 1960’s and we live in a different world today that is putting a severe strain on a traditional plan-driven project management approach.Technology is rapidly-changing, projects are more complex, and there is a much higher level of uncertainty particularly in software projectsCompetitive pressures in many companies are requiring more emphasis on creativity and innovation to maximize the business value that projects produce rather than the traditional emphasis on planning and control to maximize predictability of costs and schedulesThat calls for a higher level of skill and we can no longer take a “cookbook” approach to force-fit all projects to a standardized plan-driven project management approach.Chuck CobbAuthor of "The Project Manager's Guide to Mastering Agile"Check out: Agile Project Management Training Online for Project Managers

PMI Prince 2 No Pre Project process ‘Starting up a project' is Pre project process Theoretical Practical PM role PM Holds the responsibility and accountability for the success of project PM is a middleman between the project and its control board. If something going beyond his limit , PM has to raise the problem to the board (upper management). Then they make a decision and return it back to PM for execution. Role PMP Focuses on the project manager's role PRINCE2 defines the roles of everyone involved in a project Focus Centers on the skills and knowledge that are required of a Project Manager as outlined in PMI’s PMBoK guide. Prince 2 is specifically focused on a framework within which to manage projects in order to achieve a successful outcome. Explains Knowledge- what you should know Methodology- what you should do Inputs On Guide-Directes in techniques of project management Manual-Step by step guidence on how to run project Tells you Descriptive- the good practices(Standard) Prescriptive - what to do ( detailed process,templates. ) Helps in Answers HOW questions Answers WHAT, WHEN, and WHOM questions Contents PMP is Knowledge based – Tools & Techniques and best practices that can be applied when managing projects. PRINCE 2 is Process based – defines What, How , When , and who can do series of management processes. It dictates right process to follow Contents More detailed; explains more concepts and processes and in details. Less detailed, gives you general idea. Contents More versatile; and covers more concepts and ideas. uses easy terminology and simple concepts Contents Discusses almost every aspect of project management. Gives you strict directions (especially in Roles and Responsibilities charts) PMBOK says little about configuration management PRINCE2 offers a complete configuration management approach PMBOK just talks of the need for it PRINCE2 offers a complete change control approach Project Plan Project Plan ,Stage Plan and Team Plans Activity Based planning (Product detailing till WBS level @ Plan) Product-based Planning(Product Descriptions and Product Flow Diagram) procurement, pre-assignment or negotiation for team members Not Included In prince 2 Staff Acquisition covered in human resource management Not Included In prince 2 Org Structure Not much Inpouts on Organisation and RACI Organisation structure and RACI is clearly defined in Prince 2 Team Development team building,personal training, reward andrecognition systems Not covered Scope Scope is covered with more depth in Prince 2 (Product based planning,Product description etc) Coverage PMBOK covers from Start to finish of project Prince 2 Pre Project to Post Project

How much is you team aware about Project Management ?Do you have a dashboard in your office you can use and a meeting area ?i am assuming you are starting with the idea of doing things rightYou will I’ll need to provide your team with an Induction awareness course about Project Management explaining Why it is been usedgo to your core processes you see essential at this time like Risk Managemrnt, Com’s Managememnt , Scope Mansgement and Issues escalation and corresponding templatesissue a Project Plan document and share with team an stakeholders , review approve by sponsor and board of possibleSketch your time plan / project waterfall on the dashboard ; Task Name , Task owner, duration , dependencies , milestone and makes it as simple and clear as possibleOn the dashboard sketch the Risk Register to be updated as needed and change control register tooSet the essential meeting schedule at this this time period , weekly progress review meeting , customer / stakeholders meeting, Sponsor meeting and reporting dates.7. Assume your Project Management roles and responsibilities reference in the PMBOK incl. reference and control.Make sure you have all needed templates ready as part of the processes and share with all team and stakeholders and maybe sponsor.8- Record I’m your project file manual documents and like Meeting Minutes, updates Risk Register, project schedule , ,change requests and mitigation , training material etc… for reference when needed and being able to follow up when neeede9- Check shard Internet based management tools amd possibility for use to introduce replacing the on- hands work10- Right the Project ManagementMahemrnt Office policy amd distributiveGood Luck,Ahmed Kamel