Project Management (1)
Project Management (1)
Nuñez, Rodalyn
Morasa, Ericson M.
Alcantara, Deniel N.
PROJECT MANAGEMENT
What is a project?
- A project is a temporary enterprise undertaken to create a unique product or
service.
- A project is a process with a clearly defined start and clearly defined end. It
consists of a set task to achieve an objective, once the objective has been
achieved the project is completed.
Characteristic of a Project:
1. Temporary: Projects have a defined start and end date. Once the project's
objectives are met, the project is completed, and its resources are released.
2. Unique: Each project is distinct and aims to deliver a unique output. Even if
projects share similarities, such as being within the same industry, they will have
unique characteristics and objectives.
3. Scope: Projects have defined scopes that outline the specific deliverables,
objectives, and boundaries of the project. Managing scope is crucial to ensure
that the project stays focused on its objectives.
5. Constraints: Projects are often subject to constraints such as time, cost, and
quality. Project managers must balance these constraints to deliver the project
within the agreed-upon parameters.
1. Initiating: This involves defining the project at a broad level and obtaining
authorization to start the project.
3. Executing: This phase involves coordinating people and resources to carry out the
project plan. It includes directing and managing project execution, ensuring that tasks
are completed according to the schedule and quality standards.
5. Closing: In this final phase, the project is formally completed. This includes obtaining
acceptance from stakeholders, documenting lessons learned, and transitioning the
project's deliverables to the appropriate stakeholders or operational teams.
Project Manager:
Risk Management: Identifying, assessing, and mitigating risks throughout the project
lifecycle.
Quality Management: Ensuring that deliverables meet quality standards and align with
stakeholder expectations.
Problem Solving: Addressing issues and challenges that arise during project execution
in a timely and effective manner.
STRATEGY
- A comprehensive transformation action plan that identifies long-term direction for
an organization and guides resource utilization to accomplish organizational
goals with sustainable competitive advantage.
- Strategy is fundamentally deciding how the organization will compete.
Organizations use projects to convert strategy into new products, services, and
processes needed for success.
- Strategy is implemented through projects.
- Every project should have a clear link to and contribute value to the
organization’s strategic plan, which is designed to meet the future needs of its
customers.
The second dimension is the internal responses to new action programs aimed at
enhancing the competitive position of the firm. The nature of response depends on the
type of business, environment volatility, competition and the organization culture.
The typical sequence of activities of the strategic management process is outlined here;
a description of each activity then follow:
A project portfolio system can go a long way to reduce, or even eliminate, the impact of
these problems.
OPERATIONAL PROJECTS are those that are needed to support current operations.
These projects are designed to improve performance. Some of these projects, given
their limited scope and cost, require only immediate manager approval, while bigger,
more expensive projects need expensive review. Choosing to install a new piece of
equipment would be an example of the latter while modifying a production process
would be an example of the latter while modifying a production process would be an
example of the former. Total quality management (TQM) projects are examples of
operational projects.
STRATEGIC PROJECTS are those that directly support the organization’s long-run
mission. They frequently are directed toward increasing revenue or market share.
Examples of strategic projects are new products, research, and development.
SELECTION CRITERIA
Although there are many criteria for selection projects, selection criteria are typically
identified as financial and non financial.
FINANCIAL CRITERIA
Financial Models - For most managers financial criteria are the preferred method to
evaluate projects. These models are appropriate when there is a high level of
confidence associated with estimates of future cash flows. Two models and examples
are demonstrated here—payback and net present value (NPV).
1. The Payback model measures that time it will take to recover the project
investment. Shorter paybacks are more desirable. Payback is the simplest and
most widely used model. Payback emphasizes cash flows, a key factor in
business. Some managers use the payback model to eliminate unusually risky
projects (those with lengthy payback periods).
The major limitations of payback are that it ignores the time value of money,
assumes cash inflows for the investment period (and not beyond), and does not
consider profitability. The payback formula is
Example Comparing Two Projects Using Payback and Net Present Value Method
PAYBACK METHOD
CHECKLIST MODELS
- The most frequently used method in selecting projects has been the checklist.
This approach basically uses a list of questions to review potential projects and
to determine their acceptance or rejection.
EXAMPLE:
PROJECT CLASSIFICATION
- Experience shows most organizations use similar criteria across all types of
projects, with perhaps one or two criteria specific to the type of project, such as,
strategic breakthrough versus operational.
- The most important criterion for selection is the project’s fit to the organization’s
strategy.
SELECTING A MODEL
- Multiple criteria in project selection
- Senior Management is interested in identifying the potential mix of projects that
will yield the best use of human and capital resources to maximize return on
investment in the long run.
- Factors such as researching new technologies, public image, ethical position,
protection of the environment, core competencies, and strategic fit might be
important criteria for selecting projects.
SOURCES AND SOLICITATION OF PROJECT PROPOSALS
- As you would guess, projects should come from anyone who believes his or her
project will add value to the organization. However, many organizations restrict
proposals from specific levels or groups within the organization. This could be an
opportunity lost. Good ideas are not limited to certain types or classes of
organization stakeholders. Encourage and keep solicitations open to all
sources—internal and external sponsors.
1. Project Scope: Clearly define the boundaries of the project by specifying what is
included and what is excluded. This involves identifying the project's major components,
features, and functionalities. Use techniques like scope statements, work breakdown
structures (WBS), and mind mapping to visualize and communicate the project scope.
● Techniques for Defining the Scope
-Scope Statements
- Breaks down the project's whole scope, including the required effort,
promised deliverables, and intended objectives.
2. Objectives: Establish clear and measurable objectives that describe what the project
aims to achieve. Objectives should be specific, achievable, relevant, and time-bound
(SMART). They should align with the organization's strategic goals and provide a clear
focus for the project team.
3. Deliverables: Identify the tangible outputs or outcomes that the project will produce.
Deliverables can include products, services, documents, reports, or other artifacts that
contribute to achieving the project objectives. Define deliverables in terms of quality,
quantity, and acceptance criteria.
Deliverables are like the "what" of a project. They're the specific things you need to
produce or accomplish to consider the project a success. Think of them as the building
blocks or results that the project aims to deliver.
For example,
any adjustment in budget and/or schedule requires a corresponding adjustment in
scope. This simple concept of a balance between scope,budget, and schedule is
sometimes not fully recognized during early project development as well as during
design and construction
1. Project Initiation
- The initiation phase marks the beginning of a project, with the project
manager defining the scope and objectives.
- During this phase, it’s vital to align stakeholders on common goals and lay
the foundation for a successful project.
- Next, the project manager creates a project charter, outlining the purpose,
goals, and scope of the project. This charter includes the following key
information:
● Project purpose and justification
● Main objectives and deliverables
● Key stakeholders and team members
● Initial schedule and budget estimates
The project manager also conducts a feasibility assessment to determine if the project
is realistic and worthwhile.
2. Project Planning
-During the planning phase, the project manager develops a detailed project plan
and roadmap. This involves determining key scheduling details, resource
allocation, and risks that could impact the project. The goal is to create a
comprehensive map of how the team will execute the work.
3. Project Execution
- During the execution phase, the team puts the project plan into action. The
project manager plays a key role in coordinating resources, including
people, tools, and materials, while also ensuring the team is well-informed
about their individual tasks and timelines.
-During this phase, the project manager identifies any deviations from the plan
and budget, determining the cause to take corrective action. Tools such as status
reports, time tracking, budget reports, risk management plans, and stakeholder
reviews make it easy to see the most important metrics and milestones. To make
changes to the plan, team members should submit a change request for
approval.
5. Project Closure
- The closing phase marks the formal end of a project. During this phase,
the focus is on getting final approvals and sign-offs, conducting a
post-project review, identifying what went well, determining areas for
improvement, and documenting lessons learned. These activities foster a
culture of continuous learning and promote accountability and
transparency.
1. Define Project Objectives: Begin by revisiting and refining the project objectives
established during the project definition phase. Ensure that the objectives are specific,
measurable, achievable, relevant, and time-bound (SMART).
S- SPECIFIC - Goals should be clear and specific, leaving no room for ambiguity. They
should answer the questions of who, what, where, when, and why. Clear specificity
helps in understanding exactly what needs to be accomplished.
T- TIME BOUND - Goals should have a specific timeframe or deadline for completion.
Setting a deadline creates a sense of urgency and helps maintain momentum towards
achieving the goal. It also provides a clear target date for evaluation and review.
2. Create a Work Breakdown Structure (WBS): Break down the project scope into
smaller, manageable tasks and subtasks using a hierarchical structure known as the
Work Breakdown Structure (WBS). This helps to organize and prioritize project
activities, clarify responsibilities, and estimate resource requirements.
5. Develop a Schedule: Develop a project schedule that defines the start and end
dates for each activity and identifies key milestones and deliverables. Use scheduling
tools such as Gantt charts.
.
8. Define Quality Standards: Establish quality standards and criteria that must be met
for project deliverables to ensure that they meet stakeholder expectations and
requirements. Implement quality assurance processes to monitor and evaluate project
performance against these standards.
10. Document the Plan: Document the project plan in a comprehensive document or
project management software platform. Ensure that the plan is accessible to all project
stakeholders and serves as a guiding document for project execution.
11. Review and Finalize: Review the project plan with key stakeholders to ensure
alignment with project objectives, requirements, and constraints. Make any necessary
revisions or adjustments based on feedback before finalizing the plan.