Search Website:

Project Management

Project Methodologies - Not A Silver Bullet

When researching information for important projects, always cross check your work with multiple sources to ensure you receive a diverse selection of information on the subject matter. We do our best to ensure the content contained on this site is as accurate as possible, however things like statistics and time sensitive material may become outdated rather quickly. So if your research is for a school project or term paper, or any other reason that requires complete correctness the Article.vbxml.net website's Project Management category and the Project Methodologies - Not A Silver Bullet article is a great place to start due to our volume of information and broad range of resources, however "always" cross check facts and opinions to ensure corectness.

Article.vbxml.net is dedicated to providing reviews, learning materials, answers to questions, home work help, articles, assignment resources and we pride ourselves on offering a diverse resource completely free.. Because everyone loves free stuff, myself included. So, with that said i hope we helped you in your research and if so feel free to bookmark us and come back again!

Over the last few years there has been much emphasis on project management methodologies such as Prince2. The introduction and roll out of these structured techniques helps set expectations amongst the wider community about what the project manager will do, and the manner in which communication will take place.
For instance the project stakeholders will not be surprised to see a project manager having a set of documents including
� Business Case,
� Project Initiation Document,
� Product flow chart
� Product descriptions
� Highlight reports
� Risk Log.

The development of the standard processes is obviously helpful as these, together with standard templates for the documents used, help many project issues to be anticipated and worked around. In order to be credible the methodologies need to cope with the most complex situations (e.g. Building the Olympic venues for London 2012)

The size and scope of some of the methods can give rise to serious issues as the project manager seeks to decide which elements from the methodology can be treated as optional and tries to downscale the approach to smaller projects. The level of detail or the number of stages of plans is all a matter of
judgement, as is the appropriate membership of a supervisory board within a Prince2 approach. Sometimes this reduction can be triggered by external time commercial and time pressures with people asking why you don't stop creating documents and get the team to concentrate on actually producing something; but it can also be decided by the personnel available to provide the supervisory roles and structures envisaged.

The project manager and the team
The role of the project manager and the team in making sure that the documents and controls are of appropriate quality can also sometimes be given insufficient attention.
� It is difficult to know when a risk log is complete. This log is sometimes compiled using brainstorming or other collaborative techniques, but the obvious need to have few un-mitigated risks can lead to 'game playing'.
� Deciding on the work breakdown structure and the product interdependencies can be really challenging.

As project methodologies have become more prevalent, the author has noticed a tendency for the subject knowledge of project managers to be treated by some as less important. The project manager may be more of a generalist who understands the process of project management rather than an individual who has experience of the particular challenges arising from the activities involved ( e.g. software development, building an airport ). There is little substitute for the experience that allows a project manager to judge when a small issue is one that will remain small or could grow into a issue threatening the complete project ( or even programme ). This isn't to say that software project managers need to know how to programme for example; but if for instance they don't understand the difference between representative and unrepresentative test harnesses for unit testing then the system integration could be appalling
painful.

The team obviously have a vital role to play but the team can feel inhibited from telling their boss that he or she is wrong. Even if the message is delivered it can be discounted, or confused with a lack of discipline. Independents can play a valuable role uncovering these and other challenges that the project may face.

Quite apart from the challenges that arise from the need to define management deliverables there are often serious issues with the estimates and assumptions made as part of specialist deliverables that are to be delivered through the project. These assumptions are of critical significance to the whole project and often need a detailed technical and business review to bring them to light. The technical staff within a project may not be aware their interpretation of the business requirements has embedded unsafe assumptions.

Examples of some unsafe assumptions that the author has uncovered during past project reviews are:
� Expecting the client to synchronize identifiers between systems on a regular basis.
� Misunderstanding the speed of response required to support call centre staff when designing a complex integration to back office systems.

Project reviews
More recently much attention has been given to 'gateway reviews'. In the UK the OGC have published a gateway review process that organisations may have adopted. It is worth recognising, however, what these reviews do well, and what they omit. The reviews focus on 'buy' rather than 'build', and they ask whether the project management controls are working and the project will deliver the benefits to its stakeholder community. The reviews do NOT focus or consider which assumptions may make the project outputs meaningless. This is assumed to be happening as part of the project management process. A review that actually looks at the real deliverables can be valuable to make sure that the project will still deliver something.

Conclusion
So whilst project management methodology is rightly seen as a means to avoid some of the more obvious pitfalls that have been seen in projects, practioners should be wary of assuming that the adoption of a particular methodology will be a miracle cure for all projects.

Once the views of the team and other stakeholders have been gathered it is worth getting independent review to assess your plan and the assumptions. Periodic refresh as the project unfolds can be worthwhile, depending on the extent of change experienced during the delivery period.

Articles: http://article.vbxml.net

From the Encyclopedia: Economics - Health - Law Issues - Spyware and Virus - Web Hosting and Servers - Dental

The article above titled Project Methodologies - Not A Silver Bullet may be published on your website, simply use the "Website Version" link to the right to obtain the article to paste in to your site. Article.vbxml.net is an article repository housing nearly 45,000 different articles on various subjects, so feel free to browse around for other quality articles.

Information is a valuable commodity, reading and learning from such resources helps to obtain a better understanding on the Project Management topic. With an understanding, you are able to make informed decisions.

We have also located 10 other articles related to this one, so we have listed them below along with this weeks hottest sections, so if Project Methodologies - Not A Silver Bullet didn't suit what you were looking for or if you have more questions check out the menu links below to browse around. Also our Business and Home Business sections have been mentioned in official offline school resources for Business Study papers, so these are worth checking out as well as the Project Management you are currently viewing.Over the last few years there has been much emphasis on project management methodologies such as Prince2. The introduction and roll out of these structured techniques helps set expectations amongst the wider community about what the project manager will do, and the manner in which communication will take place.
For instance the project stakeholders will not be surprised to see a project manager having a set of documents including
� Business Case,
� Project Initiation Document,
� Product flow chart
� Product descriptions
� Highlight reports
� Risk Log.

The development of the standard processes is obviously helpful as these, together with standard templates for the documents used, help many project issues to be anticipated and worked around. In order to be credible the methodologies need to cope with the most complex situations (e.g. Building the Olympic venues for London 2012)

The size and scope of some of the methods can give rise to serious issues as the project manager seeks to decide which elements from the methodology can be treated as optional and tries to downscale the approach to smaller projects. The level of detail or the number of stages of plans is all a matter of
judgement, as is the appropriate membership of a supervisory board within a Prince2 approach. Sometimes this reduction can be triggered by external time commercial and time pressures with people asking why you don't stop creating documents and get the team to concentrate on actually producing something; but it can also be decided by the personnel available to provide the supervisory roles and structures envisaged.

The project manager and the team
The role of the project manager and the team in making sure that the documents and controls are of appropriate quality can also sometimes be given insufficient attention.
� It is difficult to know when a risk log is complete. This log is sometimes compiled using brainstorming or other collaborative techniques, but the obvious need to have few un-mitigated risks can lead to 'game playing'.
� Deciding on the work breakdown structure and the product interdependencies can be really challenging.

As project methodologies have become more prevalent, the author has noticed a tendency for the subject knowledge of project managers to be treated by some as less important. The project manager may be more of a generalist who understands the process of project management rather than an individual who has experience of the particular challenges arising from the activities involved ( e.g. software development, building an airport ). There is little substitute for the experience that allows a project manager to judge when a small issue is one that will remain small or could grow into a issue threatening the complete project ( or even programme ). This isn't to say that software project managers need to know how to programme for example; but if for instance they don't understand the difference between representative and unrepresentative test harnesses for unit testing then the system integration could be appalling
painful.

The team obviously have a vital role to play but the team can feel inhibited from telling their boss that he or she is wrong. Even if the message is delivered it can be discounted, or confused with a lack of discipline. Independents can play a valuable role uncovering these and other challenges that the project may face.

Quite apart from the challenges that arise from the need to define management deliverables there are often serious issues with the estimates and assumptions made as part of specialist deliverables that are to be delivered through the project. These assumptions are of critical significance to the whole project and often need a detailed technical and business review to bring them to light. The technical staff within a project may not be aware their interpretation of the business requirements has embedded unsafe assumptions.

Examples of some unsafe assumptions that the author has uncovered during past project reviews are:
� Expecting the client to synchronize identifiers between systems on a regular basis.
� Misunderstanding the speed of response required to support call centre staff when designing a complex integration to back office systems.

Project reviews
More recently much attention has been given to 'gateway reviews'. In the UK the OGC have published a gateway review process that organisations may have adopted. It is worth recognising, however, what these reviews do well, and what they omit. The reviews focus on 'buy' rather than 'build', and they ask whether the project management controls are working and the project will deliver the benefits to its stakeholder community. The reviews do NOT focus or consider which assumptions may make the project outputs meaningless. This is assumed to be happening as part of the project management process. A review that actually looks at the real deliverables can be valuable to make sure that the project will still deliver something.

Conclusion
So whilst project management methodology is rightly seen as a means to avoid some of the more obvious pitfalls that have been seen in projects, practioners should be wary of assuming that the adoption of a particular methodology will be a miracle cure for all projects.

Once the views of the team and other stakeholders have been gathered it is worth getting independent review to assess your plan and the assumptions. Periodic refresh as the project unfolds can be worthwhile, depending on the extent of change experienced during the delivery period.

Want Project Management Articles delivered Via RSS? Simply click the XML icon above

You are currently viewing articles from - Home | Business | Project Management

You may also find these categories of interest: Medicine - Travel - Outdoors - Stock Market - Business - Finance - Business Opportunities and Diseases - Cookie Stuffing Script

How To Manage Six Sigma Teams - By :
Six Sigma Training 101- Guide To Better Management - By :
Six Sigma Deployment - By :
IDOV Methodology Of Six Sigma - By :
Role Of Six Sigma In Enterprise Cost Reduction - By :
Six Sigma Myths - By :
Guide To Outsourcing - By :
Short Cuts To Six Sigma Success - By :
Defining Six Sigma Projects - By :
Essential Six Sigma Software - By :

Feel free to view the articles listed above, we found them similar to Project Methodologies - Not A Silver Bullet so they may also interest you, some are in the Project Management category or other subcategories.

Select a category to view what we have to offer!

Website Version