Software Project Planning and Management

This document presents a comprehensive software project plan encompassing various stages, from requirement analysis to software system development. It includes a detailed budget breakdown, key milestones with start and finish dates, specific deliverables, and a responsibility assignment matrix (RAM) outlining roles and responsibilities for different activities. The plan aims to provide a structured approach to managing the software development lifecycle.

Project Management Plan
Project ID
Project Name Tasks for software development
project
Project ID #003458
Sponsor Chris Jones Project
Mgr.
<<name of the student>>
Date 10/02/18 Version
Prepared By Anna Lewis (Documenter) Requested
By
Project Sponsor
Project Charter Version Control
Version Date Author Change Description
1.0 21/02/18
 Anna Lewis
 Charter is created
2.0 27/02/18
 Chris Jones
 Schedule change
 Milestone change
 Budget change
Project Business Case and Information
Project Charter
Purpose
 The project charter helps in forming the initial information transfer document that can be used for
providing the overview of the basic project description, scope (in scope and out of scope), aims and
objectives, assumptions and constraints of the project. It provides the development of the effective work
estimates and schedule planning for the effective project operations.
 The objectives of the charter document are to serve as the initial document for the project so that the
stakeholders can get the idea of what would occur in project.
Background The project is an IT development project and the development of the software is the basic deliverable
for the project. Many organizations have been using the development of the software
implementation for improving their operations. The use of the software development in the project
would help in integrating the facilities of effective communication management within the
organization. The development of the effective communication had helped in listing the facilities of
complete software development of the operations.
Benefits The implementation of the software development projects would allow the formation of the
improved operations for the organization. The implementation of the effective communication in the
organization is resulted by the formation of the successive and effective communication in the
operations of the project.
Objectives The business goals in implementing the software development project are increase in the overall
outcomes of the project, deployment of the successive and effective integration management, and
increase of overall sales of the organization.
The objectives of the project are,
To develop and implement software implementation for the organization
To form the plan supporting the development of the effective and improved activity
Scope In Scope The project scope involves the development of the operations for implementing the
software development for the organization. The in scope items of the project are
documents like charter and initiation documentation, plan development for scope,
communication, development, deployment, maintenance, communication, quality, and
risk management, and designing UI, use case, database, and permissions.

Out of
Scope
The out of scope items of the project are the transportation requirements, system
change implementation, test plan, and change management.
Approach The project had been developed by following the traditional waterfall approach for listing the
activities of the project and forming the accurate development of the operations for the organization.
The project is divided into 3 phases namely initiation phase, planning phase, and execution phase. The
alignment of the activities in these three phases has been termed as work package.
Success Indicators The success criteria for the project are,
Completion of project in the expected time of within 3-4 months
Overall cost of the project would be $100,000.00
Design developed would be feasible and the test results would be favorable for utilization
Assumptions Resources required for the project would be available for being used for effective operations.
Project would include the modification of the activities for forming the development of intrusive
development
Project schedule is developed for ensuring that the development of the activities would involve the
listing the activities of the project
Constraints The time, cost, and technology development are the constraints of the project. The use of effective
technology development is the factors of constraints for the project.
Project References Milestones Description
Project Organizational structure
Key
Stakeholders
Stakeholder Name Stakeholder Role Responsibility & Authority
Client Approval of project
requirements
Sponsor Providing investing amount
for the project
Steering
Committee
Name Role Responsibility & Authority
Project Manager Managing the activities of
the project
Quality Head Maintaining the quality of
the operations
Project
Resources
Name Role Responsibility & Authority
Documenter Documenting the reports of

the project
Analyst Analyzes the requirements
of the project
Engineer In-charge of the effective
and improved technology
activities
Responsibilities
Accountabilitie
s Matrix (RAM)
A = Accountable
R = Responsible
I = Involved
IR = Reviewer
C = Consulted /Communicate
Client
Sponsor/Investor
Project Manager
Quality Head
Documenter
Analyst
Engineer
Quality Assurance/
Control
Initiation
Requirement Analysis F
Scope Development
Development of project
charter
Project Initiation
Documentation
Project Kick off meeting
Planning
Development Planning
Deployment Planning
Maintenance Planning
Project Planning
Communication Planning
Quality Planning R
Risk Management Planning
Procurement Planning
Plans Approval
Execution
Develop use cases
Create data and hardware
architecture
Perform impact analysis
Develop migration strategy
Design UI
Design objects and workflow
Design rules and middle tier
Design database
Design connectivity with other
systems
Design permissions
Product design approved v

Organizational
Structure
[Include a high level organizational chart representing the delivery work streams with the leads of each
streams identified.]
Project Budget and Deliverables
Budget Stage 1 Reference No. Stage 1 approved amount $
#003578 $100,000.00
Key Milestones &
Deliverables
Milestones Earliest Start Date Latest Start Date
Project Kick off meeting Wed 3/7/18 Wed 3/7/18
Plans Approval Wed 4/11/18 Thu 4/12/18
Perform impact analysis Wed 4/25/18 Fri 4/27/18
Product design approved Wed 6/6/18 Wed 6/6/18
Deliverables
S. No. Deliverable Start date Finish date
1 Development of project charter Wed 2/21/18 Tue 2/27/18
2 Project Initiation Documentation Wed 2/28/18 Tue 3/6/18
3 Various Plans for project Thu 3/8/18 Thu 4/12/18
4 Develop use cases Fri 4/13/18 Tue 4/17/18
5 Create data and hardware architecture Wed 4/18/18 Tue 4/24/18
6 Software System Wed 6/6/18 Wed 6/6/18
Approvals
Name Signature Date
Sponsor
Steering Committee