Planning Phase: Development Lifecycle Models, Matching Lifecycles To Projects, Project Plans, Work Breakdown Structures (WBS)

Lecture 5
Planning Phase: Development lifecycle models,

matching lifecycles to projects, Project plans,
Work Breakdown Structures (WBS)
1
5 Phases of Project Management
• According to PMI, “project management is the

application of knowledge, skills, tools, and
techniques to a broad range of activities in order to
meet the requirements of a particular project.”
• There are five phases of project management and if
the lifecycle provides a high-level view of the project,
the phases are the roadmap to accomplishing it
2
3
Phase 1: Project Initiation
• This is the start of the project, and the goal of
this phase is to define the project at a broad
level. This phase usually begins with a
business case. This is when you will research
whether the project is feasible and if it should
be undertaken. If feasibility testing needs to
be done, this is the stage of the project in
which that will be completed
4
Phase 2: Project Planning
• This phase is key to successful project
management and focuses on developing a
roadmap that everyone will follow. This phase
typically begins with setting goals. Two of the
more popular methods for setting goals are
S.M.A.R.T. and CLEAR
5
Phase 3: Project Execution
• This is the phase where deliverables are developed and completed. This often feels like the
meat of the project since a lot is happening during this time, like status reports and meetings,
development updates, and performance reports. A “kick-off” meeting usually marks the start
of the Project Execution phase where the teams involved are informed of their
responsibilities. Tasks completed during the Execution Phase include:
• Develop team
• Assign resources
• Execute project management plans
• Procurement management if needed
• PM directs and manages project execution
• Set up tracking systems
• Task assignments are executed
• Status meetings
• Update project schedule
• Modify project plans as needed
6
Phase 4: Project
Performance/Monitoring
• This is all about measuring project progression
and performance and ensuring that everything
happening aligns with the project
management plan. Project managers will use
key performance indicators (KPIs) to
determine if the project is on track.
7
A PM will typically pick two to five of these
KPIs to measure project performance:
• Project Objectives: Measuring if a project is on schedule and budget
is an indication if the project will meet stakeholder objectives.
• Quality Deliverables: This determines if specific task deliverables
are being met.
• Effort and Cost Tracking: PMs will account for the effort and cost of
resources to see if the budget is on track. This type of tracking
informs if a project will meet its completion date based on current
performance.
• Project Performance: This monitors changes in the project. It takes
into consideration the amount and types of issues that arise and
how quickly they are addressed. These can occur from unforeseen
hurdles and scope changes.
8
Phase 5: Project Closure
• This phase represents the completed project. Contractors hired to work
specifically on the project are terminated at this time. Valuable team
members are recognized. Some PMs even organize small work events for
people who participated in the project to thank them for their efforts.
Once a project is complete, a PM will often hold a meeting – sometimes
referred to as a “post mortem” – to evaluate what went well in a project
and identify project failures. This is especially helpful to understand
lessons learned so that improvements can be made for future projects.
• Once the project is complete, PMs still have a few tasks to complete. They
will need to create a project punchlist of things that didn’t get
accomplished during the project and work with team members to
complete them. Perform a final project budget and prepare a final project
report. Finally, they will need to collect all project documents and
deliverables and store them in a single place.
9
Development lifecycle models
1. The Waterfall Model
2. Incremental Process Models
3. Evolutionary Process Models
4. Concurrent Models
5. A Final Word on Evolutionary Processes
10
Figure 2. The Waterfall Model
Figure 3. The V- Model

11
Figure 4. The Incremental Model
12
Figure 5. The Prototyping Model
13
Figure 6. The Spiral Model
14
Figure 7. The Concurrent Model
15
Project plan
• A project plan answers the following basic questions regarding
the project:
• Why? - What is the task related to the project? Why is the
project is being sponsored?
• What? - What are the activities required to successfully
complete the project? What are the main products or
deliverables?
• Who? - Who will take part in the project and what are their
responsibilities during the project? How can they be organized?
• When? - What exactly is the project schedule and when can the
milestones be completed?
16
Project plan
How to write a project plan in 10 simple steps:
• Understand the scope and value of your project plan.
• Conduct extensive research.
• Ask the tough questions.
• Create your project plan outline.
• Talk with your team.
• Write your full project plan.
• Execute your plan in TeamGantt.
• Publish your plan.
17
Work breakdown structure (WBS)
• A work breakdown structure (WBS) is a key project deliverable
that organizes the team's work into manageable sections. The
Project Management Body of Knowledge (PMBOK) defines
the work breakdown structure as a "deliverable oriented
hierarchical decomposition of the work to be executed by the
project team." The work breakdown structure visually defines
the scope into manageable chunks that a project team can
understand, as each level of the work breakdown structure
provides further definition and detail.
• Figure depicts a sample work breakdown structure with three
levels defined.
18
Figure Work Breakdown Structure
19
Work Breakdown Structure Guidelines
• The following guidelines should be considered when creating a work
breakdown structure:
• The top level represents the final deliverable or project
• Sub-deliverables contain work packages that are assigned to a organization’s
department or unit
• All elements of the work breakdown structure don’t need to be defined to the
same level
• The work package defines the work, duration, and costs for the tasks required
to produce the sub-deliverable
• Work packages should not exceed 10 days of duration
• Work packages should be independent of other work packages in the work
breakdown structure
• Work packages are unique and should not be duplicated across the work
breakdown structure
20
21
Making WBS
• https://www.matchware.com/free-trial?filena
me=mindview_en
22

Planning Phase: Development Lifecycle Models, Matching Lifecycles To Projects, Project Plans, Work Breakdown Structures (WBS)

Uploaded by

Copyright:

Available Formats

Planning Phase: Development Lifecycle Models, Matching Lifecycles To Projects, Project Plans, Work Breakdown Structures (WBS)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Planning Phase: Development Lifecycle Models, Matching Lifecycles To Projects, Project Plans, Work Breakdown Structures (WBS)

Uploaded by

Copyright:

Available Formats

Lecture 5

Planning Phase: Development lifecycle models,

• According to PMI, “project management is the

Figure 3. The V- Model

You might also like