ASSIGNMENT 3 & 4

GROUP MEMBERS
TALHA SAJJAD SP18-BSE-111
ABDURREHMAN MALIK FA17-BSE-007
SOFTWARE PROJECT MANAGEMENT

MICROSOFT CORPORATION
Contents
INTRODUCTION:.......................................................................................................................3
Purpose :.....................................................................................................................................3
General Project Information :......................................................................................................3
PROJECT TEAM......................................................................................................................3
STAKEHOLDERS....................................................................................................................3
CORE CONCEPTS:.....................................................................................................................4
PROJECT SCOPE STATEMENT..........................................................................................4
Scope.........................................................................................................................................4
Project Purpose / Business Justification....................................................................................4
Objectives (in business terms)...................................................................................................4
WBS..........................................................................................................................................4
PROJECT TIME.......................................................................................................................6
Deliverables...............................................................................................................................6
PRIORITIZED TASK LIST......................................................................................................7
Project Milestones:....................................................................................................................7
Network Diagram......................................................................................................................7
PROJECT COST.......................................................................................................................8
NPV analysis:............................................................................................................................8
Payback analysis:.......................................................................................................................9
Return for Investment:...............................................................................................................9
PROJECT QUALITY...............................................................................................................9
1 Quality Management Plan Components...............................................................................10
2 Project Quality Assurance....................................................................................................10
3 Quality Control.....................................................................................................................10
Supplementary knowledge:........................................................................................................12
RISK MANAGEMENT..........................................................................................................12
Major Known Risks.................................................................................................................12
Constraints...............................................................................................................................12
External Dependencies............................................................................................................12
COMMUNICATION PLAN...................................................................................................12
Communication Strategy.........................................................................................................12
Email........................................................................................................................................13
Meetings..................................................................................................................................13
Team Gantt..............................................................................................................................13

1
 INTRODUCTION:

This is the Software Project Management Plan (SPMP) for Project Online Learning
Management System, sponsored by Higher Education Commision.

PURPOSE :

The purpose of the project is to develop a management system for students to provide education
to students at homes through online means. This document establishes roles, responsibilities,
processes and schedules for managing the software development process, in addition to
outlining the tools, methods, and procedures to be used.

GENERAL PROJECT INFORMATION:

Project Name : Online Learning Management System

Executive Sponsors : Higher Education Commision

Department Sponsor : Comsats University Islamabad

Impact of Project : Provide Education to students at homes through online means.

PROJECT TEAM

Name Department Telephone E-mail

Project Nibras Computer 1122 nibras@comsats.edu.pk
Manager: Science
Team Armughan Computer 1234 Armughan@comsats.edu.
Members: Science pk
Uzair Computer 5678 Uzair@comsats.edu.pk
Science

2
STAKEHOLDERS

Higher Education Commission

Comsats University Islamabad
Ministry of Science and Technology
CUOnline Management
eLearning project managers of this project
Management and Development Teams of IT Department

CORE CONCEPTS:

PROJECT SCOPE STATEMENT

SCOPE:
The project would enable the live delivery of the lectures to the students and to ensure the
attendance of every student. It would manage the assignments and quizzes of the student
however it can not guarantee the network conditions for the students.

PROJECT PURPOSE / BUSINESS JUSTIFICATION:

In the light of the current situation of COVID-19 the university is closed and the valuable
time of the student is being wasted. This system would help students to carry out their
education without any interference online thus saving their time.

OBJECTIVES (IN BUSINESS TERMS):

To make sure that currently enrolled students finish their semester with ease and the new
admission could be carried out efficiently

WBS:

Work Breakdown Structure

3
 It is divided into 3 levels.

Level 1 Level 2 Level 3

1. Online 1.1 Initiation1.1.1 Requirement gathering from the
Learning stakeholders
Management 1.1.2 Develop project charter
System 1.1.3 Deliver LMS project charter
1.1.4 Feedback from the stakeholders
1.1.5 Approval of charter from the
stakeholders
1.2 Planning 1.2.1 Develop the LMS project scope
statement
1.2.2 Choose right people for the project and
form teams.
1.2.3 Hold a meeting before initializing the
project
1.2.4 Develop Project Plan
1.2.5 Submit Project Plan
1.2.6 Milestone: Project Plan Approval
1.3 Execution 1.3.1 A Meeting marking the initialization of
project
1.3.2 Gather User requirements and check
feasibility
1.3.3 Develop LMS design and architecture
including modules and functionalities
implemented
1.3.4 Gather necessary hardware for
development
1.3.5 Developing LMS according to the
strategy agreed upon.
1.3.6 Deploy the LMS system made for
testing
1.3.7 Testing Phase
1.3.8 Deploy the LMS system to train and
get feedback from a selected group of users
1.3.9 Release the LMS system
1.4 Control 1.4.1 Project Manager overlooks the
development phases plus the planning phase
1.4.2 Development status fed to the manager
1.4.3 Risk analysis and management
1.4.4 Accommodating new user
requirements
4
 1.5 Closeout 1.5.1 Audit
1.5.2 Document Lessons Learned
1.5.3 Maintain Project Record
1.5.4 Send the record for review and
approval
1.5.5 Archive the record and project
documents

PROJECT TIME

For improving time management and completing all tasks on time our team used many tools
and techniques used in project time management, which are listed below, one of the main tool
we used priority task division, we divided the tasks and then completed them according to
their priority.

DELIVERABLES

● Requirements from stakeholders to be gathered by 01/09/2020

● Inspect user stories
● First increment to be delivered by 15/09/2020
● User-Interface to be delivered by 20/09/2020
● Backend functionality implemented by 30/09/2020
● Testing phase to begin by 10/10/2020
● A complete working model to be delivered by 25/10/2020
● Next iteration to be started

After making deliverables we prioritize the tasks using project time tool

PRIORITIZED TASK LIST

HIGH PRIORITY TASKS DATE DUE

☐ Coding  15/09/2020
☐ Design User Interface  25/09/2020

5
 ☐ Database connection  30/09/2020
MEDIUM PRIORITY TASKS DATE DUE
☐ Devolopment  05/10/2020
LOW PRIORITY TASKS DATE DUE
☐ Testing  15/10/2020
ADDITIONAL TASKS DUE DATE
☐  Feedback  25/10/2020

PROJECT MILESTONES:

Requirement Phase: Start date: Tuesday 01/09/2020 End date:Thursday 10/09/2020

Design Phase: Start date: 15/09/2020 End date: 25/06/2020

Development Phase: Start date: 26/09/2020 End date: 05/10/2020

Testing Phase: Start date: 06/10/2020 End date: 15/10/2020

Deployment Phase: Start date: 16/10/2020 End date: 30/10/2020

NETWORK DIAGRAM

Activities Predecessor Duration

Requirement 6
elicitation(A)
Project Charter(B) Requirement 2
elicitation(A)
Scope Statement(C) Requirement 2
elicitation(A)
Assign tasks to teams(D) Project Charter(B) 7
Project Plan Dev(E) Scope Statement(C), 8
Project Charter(B)
User Requirement Project Plan Dev(E), 6
Gathering(F) Scope Statement(C)
LMS Design(G) User Requirement 12
Gathering(F),(D)
Develop LMS in LMS Design(G) 22
stages(H)
6
 Test the LMS(I) Develop LMS in 5
stages(H)
Deploy(J) Test the LMS(I) 1

C H I
2 22 5
E
8
Start
End
F G
6 12
J
1

A B D
6 2 7

Paths Duration
A,B,D,G,H,I,J 55
A,B,E,F,G,H,I,J 62
A,C,E,F,G,H,I,J 62
A,C,F,G,H,I,J 54

PROJECT COST

In order to manage cost we used cost management tool NVP Analysis, it gave us the idea
how much we are spending and in how many years we will be able to earn back from it
and can fulfil our devolopment cost.

NPV ANALYSIS:

Suppose we made an initial investment of 10,000 on the project and we have

7
 discount rate of 10%. The cash flows are given below:

PV Factor year 1: 1 ÷ (1 + 12%)1 =0.8928

PV Factor year 2: 1 ÷ (1 + 12%)2 =0.7971
PV Factor year 3: 1 ÷ (1 + 12%)3 =0.7117

Year Net Cash Inflow PV Factor Present Value

of Inflows
1 5000 0.8928 4464
2 6000 0.7971 4782
3 8000 0.7117 5963

Total Inflow=15209

NPV=Total Inflow –Initial Investment =15209-10000=5209

PAYBACK ANALYSIS:

Year Costs Cumulative Benefits Cumulative

Cost Benefits
0 10000 10000 1800 1800
1 1500 11500 6000 7800
2 3000 14500 8000 15800
3 2800 17300 9000 24800

As we can see that in the second year our benefits have crossed the cumulative cost
and in first year, we were pretty close to the cumulative cost, we hence conclude
that the third year was the payback year.

RETURN FOR INVESTMENT:

ROI= (Net return on investment-Cost of investment)/Cost of investment
ROI=15209-10000/10000=0.52 (52%)

8
PROJECT QUALITY

The primary goal of the Quality Management plan is to ensure that the project deliverables
are of adequate quality and fit-for-purpose. Quality assurance and Quality control is an
integral part of the Quality Management Plan.

1 QUALITY MANAGEMENT PLAN COMPONENTS

To achieve this, the Online learning Management System Quality Management Plan
includes the following components:

 Quality Assurance - to ensure quality project management processes.

 Quality Control - via the development of quality outputs

2 PROJECT QUALITY ASSURANCE

Quality assurance in the project will be achieved by defining the defining the relevant
quality project management processes.

2.1 Tools And techniques

Quality Audit :

 It will be used to review of quality management activities to identify good or best

practices and lessons learned for use on current or future projects.
 It will assure stakeholders that the measures taken are appropriate and that quality
processes are followed
 If the measurements result in variances beyond the defined tolerance, corrective
actions can be identified.
 Identify gaps and shortcomings.
 Share good practices within the organization or industry
 Proactively improve processes to raise team productivity.
 Highlight contributions identified through the audit in the lessons learned repository.

 Relevant business domain driven standards

Any changes to these standards need be recorded as an issue in the Project Issues Register.

3 QUALITY CONTROL
In this process we will verify if the product’s compliance with the functional requirements.
9
 3.1 Tools And techniques

  To detect the defects within the management system. But no matter how thoroughly
the product is tested, we can never be 100 percent sure that there are no defects
 Unit testing will be applied to each individual component (often a program) to
ensure it is as defect-free as possible
 System testing will also be performed the entire system as one entity
 We will apply Integration testing as it occurs between unit and system testing to test
functionally grouped components
 User acceptance test is to confirm that the system is ready for operational use.
During the Acceptance Test, end-users (customers) of the system compare the
system to its initial requirements.

10
 SUPPLEMENTARY KNOWLEDGE:

RISK MANAGEMENT

MAJOR KNOWN RISKS

Risk Risk Rating (Hi, Med, Lo)

Network Quality on the user side Hi
Quality of the lectures Med
Cloud System Availability Low
Lack of feedback from students Hi
CONSTRAINTS
The time available for the development of the software is very much less.
Requirements from all of the stakeholders cannot be gathered in such a short
interval.

EXTERNAL DEPENDENCIES
The project depended on AWS for cloud storage and Youtube for the video
storage. External stakeholders would be needed to test the system.

COMMUNICATION PLAN

COMMUNICATION STRATEGY

The project manager will make a weekly report on the development of the project and will
issue guidelines weekly. The project manager will also use online means of
communication such as email and video conferences.

We used this tool for better communication between team and sponsors.

11
 Communication Frequency Goal Owner Audience

EMAIL

Project Status Weekly Review Project Project Project

Report Status Manager Team+Sponsers

MEETINGS

Team Standup Daily Discus what everyone Project Project Team

did yesterday and any Manager
blockers
Project Review At Present project Project Project
milestones deliverables,feedback, Manager Team+
and discuss steps Project
Sponser

TEAM GANTT

Task progress Daily Share Daily Project Project Team

updates progress Manager

12