Scope, Time, Quality and Budget
Scope, Time, Quality and Budget
Defines a path: A project needs to run straight forward. A clear path mapped out from start to finish
ensures the outcome meets the goals of your project.
Establishes a schedule: Without a schedule, a project has a higher probability of delays and cost
overruns. A sound schedule is key to a successful project.
Enforces teamwork: A project brings people together to share ideas and provide inspiration.
Collaboration is the cornerstone to effective project planning and management.
Maximizes resources: Resources, whether financial or human, are expensive. By enforcing project
management disciplines such as project tracking and risk management, all resources are used efficiently
and economically.
Streamlines processes: To streamline means to weed out the unnecessary steps and processes that get
in the way of efficient project decisions and results. With a project management plan in place from the
very outset, time is used in a productive manner.
Controls cost: Some projects can cost a significant amount of money so on-budget performance is
essential. By implementing fundamental project management strategies, you reduce the risk of budget
overruns.
Assures quality: A strong team and a mature methodology helps identify potential risks which increases
quality and productivity. The end result? A high-quality product or service and a very happy client.
Project management sounds so easy, right? Just keep a project on track and all is good. But alas, its just
not that simple.
The fundamentals of managing a project from start to finish require a team of individuals with different
talents and skills. Those people are responsible for planning and executing the project objectives and
that takes more than just labor and materials. A sound project plan can mean the difference between
success or failure.
Thats reason enough for colleges and universities to offer degree programs in project management. Its
a hard skill to master, but well worth learning. And heres why:
A disciplined project management process is important to any project. Project managers are expected to deliver
results, on time (if not sooner) and on budget. Solid project planning reduces the risks associated with any project
you take on. Here are ten reasons why theres a need for project management:
Why Is There A Need For Project Management?
1. CONTROL SCOPE CREEP AND MANAGE CHANGE
Small changes in demands occur on every project. They come from management, the customer, your project team,
suppliers, or other stakeholders. Individually, they may appear acceptable, but collectively these project demands
can add up to a significant project expansion (referred to as scope creep) that can overrun your budget. With
project management, if the manager effectively manages the scope of their project, they have a better than even
chance of effectively managing project resources time, money, etc. and managing change.
2. DELI VER PROJECT RESULTS ON TI ME AND ON BUDGET
The project management process starts with a well thought out business case justification that usually includes some
type of cost calculation associated with Return On Investment (ROI). Once these measures are established, it is up
to the project manager to ensure that on-time, on-budget performance is maintained; otherwise, the project will never
produce the expected results. Thats what good project management is all about, and why theres a need for project
management.
3. FOCUS THE PROJECT TEAM ON THE SOLUTI ON
The project team can easily drift off topic and spend too much time on the wrong tasks. A good project
manager keeps the project team focused by using a clear and concise project charter, resolving barriers, or shielding
the team from unnecessary interference.
4. OBTAI N PROJECT BUY- I N FROM DI SPARATE GROUPS
As President Lincoln once said, Public sentiment is everything. With it, nothing can fail; without it, nothing can
succeed. A good project manager uses the tools in the initiation phase of project management to collect user
requirements, project constraints, and a feasibility study to build a strong business case justification. Using input from
various sources, the project manager overcomes dissent and obtains buy-in by communicating the project benefits as
the different stakeholder groups see them.
5. DEFI NE THE CRI TI CAL PATH TO OPTI MALLY COMPLETE YOUR
PROJECT
Every project is made up of a series of connected activities, each of which has its own constraints. The project
manager identifies the critical path of activities the optimal sequence of actions that best ensure the projects
successful completion.
6. PROVI DE A PROCESS FOR ESTI MATI NG PROJECT RESOURCES, TI ME, AND COSTS
Using project management software, previous project experiences, and a solid project initiation phase can provide
the discipline needed to reduce project estimating errors, increasing the likelihood that the project will finish on time
and on budget.
7. COMMUNI CATE PROJECT PROGRESS, RI SKS, AND CHANGES
As a project progresses, stakeholders must be kept informed of the outcomes, changes, stumbling blocks, or
successes that the project experiences. The need for project management exists partly because it creates a
project communication plan to address these communication issues, provide a format, and lay out a process for
execution.
8. SURFACE AND EXPLORE PROJECT ASSUMPTI ONS
All projects are based on assumptions to some extent. A good project manager delves into user requirements,
project constraints, and management expectations to understand whatis said and what is not said. Relying on too
many unconfirmed assumptions can invalidate a project schedule or, worse, sink the project.
9. PREPARE FOR UNEXPECTED PROJECT I SSUES
Every project runs into unforeseen issues, such as changes in market conditions, and is hit with random
cause variability. Experienced project managers plan for the unexpected by lining up alternative courses of action.
10. DOCUMENT, TRANSFER, AND APPLY LESSONS LEARNED FROM YOUR PROJECTS
The last phase of project management focuses on closing out the project. The project manager reviews how well
each prior phase project initiation, project planning, project execution, and project monitoring and control was
performed. As part of good knowledge management, all project review notes should be dissected and analyzed for
patterns, trends, and opportunities for improvement. These lessons learned should be documented and
communicated to other project managers before starting the next project.
REASONS WHY THERE S A NEED FOR PROJECT MANAGEMENT
1. Control scope creep and manage change;
2. Deliver project results on time and on budget;
3. Focus the project team on the solution;
4. Obtain project buy-in from disparate groups;
5. Define the critical path to optimally complete your project;
6. Provide a process for estimating project resources, time, and costs;
7. Communicate project progress, risks, and changes;
8. Surface and explore project assumptions;
9. Prepare for unexpected project issues; and
10. Document, transfer, and apply lessons learned from your projects.
RELATED CONTENT
Intiation:
develop a high level plan and risk assessment
RISK
Budget
Schedule Items
Performance
Development Technology
User Attributes
Business Change
Cost or Financial
Vendor or Contractor
Human Resources
Politics
Acts of God
Requirements
analyzing the project sponsors strategic requirements
Planning:
kick off a new project and establishes an accurate plan and
schedule. The infrastructure that is established during the planning
phase is critical to effectively manage the projects success.
communications and reporting expectations will be developed and
presented to the project team
Executing:
Project Management is 20% planning and 80% tracking and
control
Executing, monitoring and controlling project progress is
important to detecting issues, problems and solutions early
enough to quickly get the project back on schedule so the
objectives are still met
CLOSING:
all project activities are completed and all deliverables
are finalized.
Performance Evaluations
Lessons Learned
Project Evaluation
Delivery of Final Documentation
Project Sign-Off
Customer Satisfaction Survey