Here are some more information for Project Standard:

Why Use a Project Management Methodology?

Many Project Managers believe that to enjoy total project management success, you need to manage projects using a formal project management methodology. They say it helps give you direction, it saves you time and it improves the quality of your deliverables. But does it?

Most good managers use a methodology of sorts, whether it be written on post-it notes stuck to their screen, documented in a stack of procedures on their desk, or included in software that they have bought. Regardless of the type of methodology used, there is one common theme - that it typically helps them to manage projects and therefore improve their project success.

What is a Methodology?

A methodology is "a set of methods, processes and practices that are repeatedly carried out to deliver projects". The key concept is that you repeat the same steps for every project you undertake, and by doing that, you will gain efficiencies in your approach.

What is a Standard?

So what is the difference between a methodology and a standard? A standard is "a collection of knowledge areas that are generally accepted as best practice in the industry".

Standards give you industry guidance, whereas methodologies give you practical processes for managing projects. Standards are not methodologies, and vice versa. The two most popular standards are PMBOK and Prince2.

What should be included?

When you buy a project methodology, it should give you:

- A core set of processes to follow for delivering projects;

- A set of templates to help you build deliverables quickly;

- A suite of case studies to help you learn from past projects;

- An option for customizing the methodology provided;

- The ability to import your existing processes into it.

What a Methodology will not do

A Methodology is not a silver bullet. It will not fix projects by itself or guarantee success and an efficient, effective experienced project manager is still required to deliver projects successfully. Remember that the finest carpenter's tool-box will only be as good as the carpenter.

No methodology will be 100% applicable to every type of project. So you will need to customise any methodology you purchase to ensure that it perfectly fits your project management environment.

Why use a Methodology?

While a methodology is not a silver bullet for projects, it should help you by giving you a clear process for managing projects. After you have customised it to perfectly fit your environment, your methodology should tell your team what has to be completed to deliver your project, how it should be done, in which order and by when.

Using a methodology you can:

- Create a project roadmap;

- Monitor time, cost and quality;

- Control change and scope;

- Minimise risks and issues;

- Manage staff and suppliers.

Of course, you will need to use the elements of the methodology that are most suitable to each project you undertake. When managing smaller projects, you will only want to apply lightweight processes to your project and when managing large projects, you should apply the heavyweight processes to monitor and control every element of your project in depth.

But if you can manage every project you undertake in the same way, then you will gain efficiencies with your approach, work smarter and reduce your stress. You will also give your team a clear understanding of what you expect from them and boost your chances of success.

If you want a methodology to help improve the way you manage projects, you are likely to want:

1) A core set of processes to follow for delivering projects;

2) A set of templates to help you build deliverables quickly;

3) A suite of case studies to help you learn from past projects;

4) An option for customising the methodology provided;

5) The ability to import your existing processes into it.

About the Author

Rob Llewellyn provides project and programme management consultancy to public and private sector organisations across Europe and the Middle East. Find more articles and videos covering similar topics at The Llewellyn Group Blog.

Project: scaling of standard astrophysical objects and distances?

Goal: each group will scale one of the following sets of sizes and distances to the 2ndfloor
walkway in front of the library. The walkway is approximately 375 feet in length.Scale the sizes or separations to the walkway.
1. Earth: separations of major cities choose
about 810
familiar cities (recommend: San
Antonio to , New York, Washington, London, Paris, Moscow, Beijing, Cape
Town, Sydney)

Step 1) Make a list of all the distances you need to scale expressed in feet.

Step 2) Examine the list and find the largest distance you need to scale. Let's call this distance L.

Step 3) Divide 375 by L. This is the scaling factor. Let's call it S. It will be some quantity that is much less than 1. For example if the distance to Washington were the largest number on the list then the scaling factor would be 375/7336824=0.0000511120343080. To facilitate calculations, you should save this scaling factor into the memory of your calculator.

Step 4) Multiply each distance on your list by S. This will produce a new list of numbers where the greatest distance has been scaled to 375 feet and all the other numbers are proportionately less than 375.

Hope this helps.

New project to identify best approaches to improve ag in developing countries
The International Food Policy Research Institute launched a new project, Global Futures for Agriculture, to improve agricultural productivity and environmental sustainability in developing countries. Focused on evaluating promising technologies, investments, and policy reforms, the effort is supported with major funding from the Bill and Melinda Gates Foundation. High global food prices in 2008 ...

Thanks for visiting!