Exploring trends and developments
in project management today.

Project Smart Logo

Getting Your Project In Sight

By Dr. Keith Mathis
A businessman looking through binoculars

Have you ever had a project that took longer than was expected, cost more, or ended up totally different than the original plan? You're not alone. Most projects sway from the initial idea, but they shouldn't and don't have to. By keeping the proper scope of your project, you will be able to finish on time, on budget, and with fewer headaches.

The scope of the project is the span of work to be completed when the project is finished. It is the customer's desired goal. The scope is the most important element to understand about any project. All planning and allocation of resources are anchored to this understanding.

When determining the scope of your project, there are some helpful questions you can ask.

  • What will be covered in the project?
  • What will not be covered in the project?
  • Where will the project end up?
  • What is the project going to achieve?
  • What will the project do after completion?
  • What does the project look like after it is finished?
  • How will the project perform after it is completed?

Answering these questions will make it easier to establish what direction your project is to go. If the path of the project is not clear, the scope may become skewed. Some examples of skewing the scope are: defining the scope with limited detail, documenting with language which is hard to measure, scope is misunderstood or not clear to project team, or the scope is not communicated thoroughly.

Once you have ascertained the scope, you must freeze it. Freezing the scope is locking the scope of the project so the planning process can be completed. This must be done as early as possible to reduce the rate of failure. To be successful, a commitment from project sponsors, managers and the entire team is required. Freezing can result in faster projects and higher productivity.

Even after the scope has been frozen, there may be some tolerance allowed. Tolerance can be defined as how much a scope or a section of the project can depart or vary from the defined plan, budget, quality, process or performance. To assist in proper tolerance, it is important to develop a scale for rating tolerance deviation. However, it is possible for scopes or projects to have zero tolerance.

There are six prerequisites for scope management.

  1. Prescope concept. The overview of how the project must function or what objectives should be met. It is loosely setting the parameters of the scope. In most cases it will change and shift in this stage.
  2. Scope definition. Nails down the scope specifics. It gives quantitative and qualitative details.
  3. Labour authorisation. Project and human capital is approved for project advancement. Human resources is designated and scheduled for this level of work.
  4. Scope communication. Communicating the project upline to upper management or internally to the project team.
  5. Control management. Driving the project forward. Control management includes levelling resources of time and human resources for better productivity.
  6. Project closedown. Bringing the project to an end. All of the components of the project are brought together for final hand-off to the customer. Document all details for future references.

Having a draft plan of the project is very beneficial. You are able to put your thoughts in order and allow them to evolve. While making the plan, you can brainstorm ideas with your team and think through the process over time. You can adjust the structure of the plan and make it more concise. Oftentimes, people will neglect making a draft plan because they are rushed to get a plan so drafts are considered a waste of time. People want to have a plan in place in the shortest time possible. People think that draft plans make you sound unsure and hesitant. None of these excuses are valid. While making a draft plan does require a little more time at the beginning of a project, their benefits far outweigh the time spent figuring out the direction of the project without a plan.

What about when changes need to be made? Let's face it. No matter how much planning we do and even if we freeze the scope, there will be changes to deal with.

Dr. Keith Mathis, founder and CEO of The Mathis Group External Link specialises in Project Management, Management Leadership, and Marketing training for private businesses and government agencies of all kinds. He offers 33 Project Management courses, is a Project Management Professional, is certified by the Project Management Institute and will customise every training session to your individual company's needs. The Mathis Group also sponsors www.pmiexpert.com External Link which is a powerful project management resource with free reports, podcasts, videos, and a monthly newsletter. He also offers customised management training and coaching on any subject with prolific communication and professionalism.

Comments page 0 of 0
Click here to add a comment
There are currently 0 comments to display.

 

Article Categories

Related Articles

Best Practices for Scope Management
The knowledge area of Scope Management is all about making sure that the project includes only the work required to complete the project successfully. To be effective at scope management, you must learn to control what is and what is not in the scope of the project. Included in this article are five best practices for successful scope management.

Improve Project Success with Better Scope Management
The Project Management Institute Project Management Body of Knowledge (PMBOK) defines product scope as the features and functions that are to be included in a product or service. It defines project scope as the work that must be done to deliver a product with the specified features and functions. Project scope management is defined as the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully.

Managing Project Scope
Ok, you're about to kick-off a project you're managing. The scope and budget are set, the team knows what they're delivering, and everyone is ready to begin. You're confident that hours have been allocated appropriately, but you also know how easy it is for scope to slip away from you - you need to keep a good handle on this project to ensure the team doesn't squander their hours and push the project over budget. In this article, I'll review some solid tactics you can employ to progressively manage your project budget and maintain total visibility from beginning to end.

Dealing with "Scope Creep" in Software Development Projects
Scope creep is a significant risk in software development projects. We discuss why this is so, and how to avoid or at least mitigate the risk. New software is usually developed as a result of a customer identifying a need. The next step is to specify how the software will meet that need; specifically, what functionality will be developed.

21 Ways to Excel at Project Management
The popular project management eBook now fully updated and available as a website for the first time.