PMBOK!
Is that a word, or am I stuck on the use of acronyms for texting my friends? No, actually, it's a phrase used extensively in the Project Management industry. It stands for "Project Management Body Of Knowledge". It's a standard (ANSI, IEEE) established by the Project Management Institute (PMI) and is internationally recognized set of processes for managing a project. Very similar to the SDLC (Software Development Live Cycle) processes.
The PMBOK is utilized by many major organizations, such as Boeing Aircraft, Fujitsu, and thousands of others. Just like the Software Development Life Cycle, the PMBOK defines a set of steps that need to be followed for insuring that a project is clearly defined, managed, and completed.
Why Use PMBOK?
Now just why would someone, or a team, want to utilize the steps defined in PMBOK? Here are some good reasons:
* It is an established and widely accepted standard. Meaning that you would be following the best and proven course of action toward having a successful project.
* It provides a path and course to follow from beginning to end. This helps to prevent not identifying expectations, requirements, or issues that could affect a timely delivery of a project.
* It not only identifies the steps, but also the level of knowledge needed for the project, and the types of tools that should be in place for managing the project.
* It provides a method for wrapping your arms around a project and clearly identifying the scope, the requirements, the time frames, resources, and the associated costs.
Why Not Use PMBOK?
Overkill is the biggest reason. If your project is only a week worth of work, why spend an additional week laying it out under the PMBOK standards? If all you need to do is hang a picture on the wall, you don't drag in the 200 pound tool rack on wheels! But knowing where to draw the line is where experience and skill comes into play.
What if your project requires several developers and will last 3 months? Would it be wise to follow PMBOK for the project? Absolutely! However, you would want to adapt the process to the scope of the project. An additional week of project management for such a project could end up saving you and your customer weeks or even a month or more of resources and expense.
The PMBOK Process
So just what are the steps involved with using PMBOK? Here's a brief overview:
* Initiating:
o Approval for the project.
o Get commitment from the customer and your team.
o Define the overall direction and gather requirements.
o Secure the necessary resources for the duration of the project.
o Validate that the project conforms to the customer's business
.
* Planning
o Define the project scope - specifications.
o Define the objectives and deliverables - specifications.
o Create the project schedule and allocate the resources.
o Establish a method for sharing information throughout the project.
o Define all the required steps and activities for accomplishing the project.
o Sequence the defined steps and activities - Project plan.
o Estimate the total effort required.
o Define the potential risks and possible risk avoidance processes.
o Define the estimated costs involved.
o Obtain funding for the project.
* Execution
o Coordinate the resources and activities.
o Coordinate the Quality Assurance.
o Communicate status to all involved parties as needed.
o Stick with the plan!
* Monitor & Control
o Manage the team and the customer.
o Measure the progress, maintain motivation.
o Respond to issues, take corrective measures, escalate, and resolve.
o Communicate, communicate, communicate!
o Manage the risks.
* Completion
o Complete the defined activities.
o Gather results, compare against initial plan.
o Appraise performance of resources. Note for future projects.
o Close and deliver the project.
This is not completely a top down sequence of processes. The Execution and Monitor & Control processes continue to work with each other through the duration of the project. If a Change Request comes in, or there is a change in the business requirements (new management?), then you might even need to go all the way back to the Planning phase and readjust the plan, resources, and costs.
Where Can You Get More Information?
By doing a Google search on "PMBOK" or "PMI", you'll get a wealth of links. Most of these will point to the Project Management Institute (www.pmi.org). You can also find books on Amazon.com for PMBOK.
To be a successful developer, you need to at least have a good understanding of how to manage and implement a complex project. Using a SDLC or PMBOK guideline will go a long way toward helping you to have a successful project.
Is that a word, or am I stuck on the use of acronyms for texting my friends? No, actually, it's a phrase used extensively in the Project Management industry. It stands for "Project Management Body Of Knowledge". It's a standard (ANSI, IEEE) established by the Project Management Institute (PMI) and is internationally recognized set of processes for managing a project. Very similar to the SDLC (Software Development Live Cycle) processes.
The PMBOK is utilized by many major organizations, such as Boeing Aircraft, Fujitsu, and thousands of others. Just like the Software Development Life Cycle, the PMBOK defines a set of steps that need to be followed for insuring that a project is clearly defined, managed, and completed.
Why Use PMBOK?
Now just why would someone, or a team, want to utilize the steps defined in PMBOK? Here are some good reasons:
* It is an established and widely accepted standard. Meaning that you would be following the best and proven course of action toward having a successful project.
* It provides a path and course to follow from beginning to end. This helps to prevent not identifying expectations, requirements, or issues that could affect a timely delivery of a project.
* It not only identifies the steps, but also the level of knowledge needed for the project, and the types of tools that should be in place for managing the project.
* It provides a method for wrapping your arms around a project and clearly identifying the scope, the requirements, the time frames, resources, and the associated costs.
Why Not Use PMBOK?
Overkill is the biggest reason. If your project is only a week worth of work, why spend an additional week laying it out under the PMBOK standards? If all you need to do is hang a picture on the wall, you don't drag in the 200 pound tool rack on wheels! But knowing where to draw the line is where experience and skill comes into play.
What if your project requires several developers and will last 3 months? Would it be wise to follow PMBOK for the project? Absolutely! However, you would want to adapt the process to the scope of the project. An additional week of project management for such a project could end up saving you and your customer weeks or even a month or more of resources and expense.
The PMBOK Process
So just what are the steps involved with using PMBOK? Here's a brief overview:
* Initiating:
o Approval for the project.
o Get commitment from the customer and your team.
o Define the overall direction and gather requirements.
o Secure the necessary resources for the duration of the project.
o Validate that the project conforms to the customer's business
.
* Planning
o Define the project scope - specifications.
o Define the objectives and deliverables - specifications.
o Create the project schedule and allocate the resources.
o Establish a method for sharing information throughout the project.
o Define all the required steps and activities for accomplishing the project.
o Sequence the defined steps and activities - Project plan.
o Estimate the total effort required.
o Define the potential risks and possible risk avoidance processes.
o Define the estimated costs involved.
o Obtain funding for the project.
* Execution
o Coordinate the resources and activities.
o Coordinate the Quality Assurance.
o Communicate status to all involved parties as needed.
o Stick with the plan!
* Monitor & Control
o Manage the team and the customer.
o Measure the progress, maintain motivation.
o Respond to issues, take corrective measures, escalate, and resolve.
o Communicate, communicate, communicate!
o Manage the risks.
* Completion
o Complete the defined activities.
o Gather results, compare against initial plan.
o Appraise performance of resources. Note for future projects.
o Close and deliver the project.
This is not completely a top down sequence of processes. The Execution and Monitor & Control processes continue to work with each other through the duration of the project. If a Change Request comes in, or there is a change in the business requirements (new management?), then you might even need to go all the way back to the Planning phase and readjust the plan, resources, and costs.
Where Can You Get More Information?
By doing a Google search on "PMBOK" or "PMI", you'll get a wealth of links. Most of these will point to the Project Management Institute (www.pmi.org). You can also find books on Amazon.com for PMBOK.
To be a successful developer, you need to at least have a good understanding of how to manage and implement a complex project. Using a SDLC or PMBOK guideline will go a long way toward helping you to have a successful project.
Sourcing for project management tool, contact Alenu Now! at (65) 6884 5030.
A PR article by Dougles Chan - Search Engine Guru - The best SEO company in Singapore and globally. Contact Dougles Chan @ +(65) 9388 0851 or email to dc@dougleschan.com for more information on how to make your website to be the top in Google.
No comments:
Post a Comment