CREATING

THE PROJECT
PLAN
Week 3
What is a Software Project Plan?
A software project plan is a collection of documents
that outline the tasks and timeline of your software
development.

Software project plans usually follow flexible progressions

that allow project managers to adjust for project success.

A flexible project plan enables software developers to

move forward and back in creating error-free programs
because a large part of software development comprises
testing and troubleshooting.
Importance of Software Project Plans
Defining role and responsibilities
Determining client requirements
Meeting project deadlines
Adhering to the project budget
Ensuring high-quality work
How to create a Software Project Plan

1. DEFINE THE SCOPE OF YOUR SOFTWARE PROJECT

A project's scope describes the goals needed to complete the project
successfully. When defining your scope, consider project aspects like
outcomes, tasks, budget, time frame, and deliverables.
How to create a Software Project Plan

2. ISOLATE TASKS WITHIN THE PROJECT

When creating a software project plan, it's helpful to isolate the
smaller tasks that comprise the project. This can help determine the
project budget and create a team to manage aspects of the project.
For example, you may want to create a team that performs quality assurance on the beta
code for the software. In your document, make a list of the separate tasks that lead to a
completed project.
How to create a Software Project Plan

3. DESIGN TIME-BASED OBJECTIVES

Deciding on your time-based objectives, or milestones, is an
important step in software project planning. To do this, determine
how long each task within the project should take.
For example, if you have six months to develop software for your client, you might want to
finish the program prototype by the second month of the project. Create deadlines or
milestones within the project, giving yourself extra time to account for any delays.
How to create a Software Project Plan

4. DELEGATE TASKS TO TEAMS OR INDIVIDUALS

If a task within your project is complex or may require specific
expertise, consider creating a team of skilled individuals to work
together.
For example, you may have one team work on design while another performs software
sprints, quality assurance and testing.
How to create a Software Project Plan

5. ESTABLISH SCHEDULES FOR YOUR TEAM

Once you know when to complete each task within the project, you can establish
schedules for everyone working on the software. Detailing how much labor you
need and communicating with your team about the project needs can help you
reach your milestones on time and ensure timely deliverables.
For example, if you expect to finish the project in six months, you can create a monthly
schedule that details what each team should work on during that month.
How to create a Software Project Plan

6. PERFORM APPROPRIATE RISK ASSESSMENTS

There's some risk for every project, and by performing risk assessments,
you can identify obstacles that could affect your project.

For example, if you rely on a stable internet connection to complete your work, a system
failure in the fiber optics network might be a risk. By performing risk assessments, you can
anticipate potential risk factors and prepare plans for adapting to them.
How to create a Software Project Plan

7. GATHER AND ANALYZE PROJECT DATA

Gathering and analyzing data is an important part of the software
planning process because it helps ensure the success of your current
plan. Gathering project data can determine if your budget and time
estimates remain correct. Understanding how each aspect of the
project plan and its actual work compare is important for creating a
realistic plan.
How to create a Software Project Plan

8. MAKE ADJUSTMENTS TO ENSURE SUCCESS

Using your project data, make necessary adjustments to the project
scope, how you implement your plan or the delegation of tasks. For
software projects, it's important to maintain a flexible plan so that you
can adapt it as needed. After you collect data from your team or client,
analyze this data to see if you need to make changes.
CREATING THE PROJECT PLAN
PROJECT MANAGEMENT PHASES CONSIST OF
Stage 1: Project Conception and Initiation

Stage 2: Project Planning

Stage 3: Project Execution

Stage 4: Project Monitoring & Controlling

Stage 5: Project Close

https://blog.hubspot.com/marketing/project-management-phases
PROJECT METHODOLOGY OPTIONS
Waterfall Development
Parallel Development
V-model
Rapid Application Development (RAD)
Iterative Development
System prototyping
Agile Development
Waterfall Development
is a sequential
development
process that
flows like a
waterfall
through all
phases of a
project
Parallel Development

is working on
multiple
projects or
features at the
same time.
V-Model

is an SDLC
model where
execution of
processes
happens in a
sequential
manner in a
V-shape.
Rapid Application Development:
Iterative Development

Iterative design
and prototyping is
a repeating cycle
of designing,
prototyping,
testing, and
refining multiple
“versions,” or
iterations, of a
product.
Rapid Application Development:
System Prototyping

allows you to
design a
working
“prototype” or
early sample
of what's to
come.
Throwaway Prototyping

Building initial ideas

for different
applications,
interfaces, or
functions, without
necessarily having
the intention of
including them in the
finished system.
Agile Development

is a type of
software
development
methodology that
anticipates the
need for flexibility
and applies a level
of pragmatism to
the delivery of the
finished product.
Selecting the Appropriate
Methodology
IMPORTANT FACTORS TO CONSIDER IN
SELECTING THE DEVELOPMENT
METHODOLOGY
Clarity of User Requirements
Familiarity with Technology
System Complexity
System Reliability
Short Time Schedules
Schedule Visibility
THANKYOU