MNG91218 Project Report: Planning Website Upgrade ABC Software Ltd

This project report outlines the planning phase for a website upgrade project for ABC Software Private Limited. It includes a detailed scope statement defining the project's objectives, such as system hardware and software upgrades, new feature additions, and the development of a new business portal. The report features a comprehensive work breakdown structure (WBS) that decomposes the project into manageable tasks, along with activity descriptions and dependencies. Key activities include project surveying, estimation, planning, initiation, execution, and closure, with associated milestones. The document specifies activity dependencies, sequencing, and date constraints, providing a structured approach to project management. This resource is ideal for students seeking examples of project planning documents; Desklib offers a wealth of similar solved assignments and resources.

MNG91218 Assessment 3
A. Preparation Phase
A.1. Scope Statement
The scope of the project includes the upgradation of the website for ABC Software Private
Limited. The scope of the project also includes the following requirements.
 System hardware upgrade
 Software upgrade to latest versions
 Addition of new features within the website
 Development of new business portal within the website
 Other technical upgrades and testing

A.2. Work Breakdown Structure (WBS)
WBS should be presented in one of the following formats: Indented Outline, Organisational Chart or Free. See examples Exhibits 7.5-7.7,
Kloppenborg 2018, p. 222-223.
The overall work breakdown structure is shown in the following table.
WBS Task Name Duration Start Finish
0 Website Upgrade for ABC Software Private
Limited 129 days Mon 5/6/19 Thu 10/31/19
1 Survey and Discussion of Project 13 days Mon 5/6/19 Wed 5/22/19
1.1 Identify the issues with the current
website 5 days Mon 5/6/19 Fri 5/10/19
1.2 Analyze the implications of the issues 3 days Mon 5/13/19 Wed 5/15/19
1.3 Prepare for Team Meeting 1 day Thu 5/16/19 Thu 5/16/19
1.4 Discuss about website upgrade 2 days Fri 5/17/19 Mon 5/20/19
1.5 Check for project feasibility 2 days Tue 5/21/19 Wed 5/22/19
1.6 Milestone 1: Confirmation of Project 0 days Wed 5/22/19 Wed 5/22/19
2 Estimation and Planning of the Project 23 days Thu 5/23/19 Mon 6/24/19
2.1 Develop project team 2 days Thu 5/23/19 Fri 5/24/19
2.2 Primary Plan 11 days Mon 5/27/19 Mon 6/10/19
2.2.1 Set project goals based on
requirements 3 days Mon 5/27/19 Wed 5/29/19
2.2.2 Identify Project Scope 2 days Thu 5/30/19 Fri 5/31/19

2.2.3 Determine Project Life Cycle 2 days Mon 6/3/19 Tue 6/4/19
2.2.4 Develop work breakdown structure for
the project 1 day Wed 6/5/19 Wed 6/5/19
2.2.5 Determine appropriate schedule based
on the work breakdown structure 1 day Thu 6/6/19 Thu 6/6/19
2.2.6 Estimate Budget 2 days Fri 6/7/19 Mon 6/10/19
2.3 Secondary Plan 10 days Tue 6/11/19 Mon 6/24/19
2.3.1 Determine risks associated with the
project 2 days Tue 6/11/19 Wed 6/12/19
2.3.2 Develop Risk Register 2 days Thu 6/13/19 Fri 6/14/19
2.3.3 Prepare Mitigation Plan for Risks 2 days Mon 6/17/19 Tue 6/18/19
2.3.4 Review overall project plan 3 days Wed 6/19/19 Fri 6/21/19
2.3.5 Develop suitable quality management
plan 1 day Mon 6/24/19 Mon 6/24/19
2.4 Milestone 2: Approval to Proceed in
Project 0 days Mon 6/24/19 Mon 6/24/19
3 Initiation of Project 9 days Tue 6/25/19 Fri 7/5/19
3.1 Procure Budget 2 days Tue 6/25/19 Wed 6/26/19
3.2 Recruit Develper and Tester 3 days Thu 6/27/19 Mon 7/1/19

3.3 Allocate Roles in Project 1 day Tue 7/2/19 Tue 7/2/19
3.4 Purchase Hardware 2 days Wed 7/3/19 Thu 7/4/19
3.5 Purchase Software 1 day Fri 7/5/19 Fri 7/5/19
3.6 Milestone 3: All Preparations Complete 0 days Fri 7/5/19 Fri 7/5/19
4 Execution of Project 73 days Mon 7/8/19 Wed 10/16/19
4.1 Upgrade Hardware System 5 days Mon 7/8/19 Fri 7/12/19
4.2 Set Up Software Platform 3 days Mon 7/15/19 Wed 7/17/19
4.3 System Development 52 days Thu 7/18/19 Fri 9/27/19
4.3.1 Upgrade Website 15 days Thu 7/18/19 Wed 8/7/19
4.3.2 Initial Testing 5 days Thu 8/8/19 Wed 8/14/19
4.3.3 Addition of Features 15 days Thu 8/15/19 Wed 9/4/19
4.3.4 Develop business portal 10 days Thu 9/5/19 Wed 9/18/19
4.3.5 Beta Testing 5 days Thu 9/19/19 Wed 9/25/19
4.3.6 Completion of Design 2 days Thu 9/26/19 Fri 9/27/19
4.4 Testing the Website 13 days Mon 9/30/19 Wed 10/16/19
4.4.1 Reconnect with Central Server 2 days Mon 9/30/19 Tue 10/1/19
4.4.2 Test Website Features 5 days Wed 10/2/19 Tue 10/8/19
4.4.3 Identify and Solve Issues 6 days Wed 10/9/19 Wed 10/16/19

4.5 Milestone 4: Go Live 0 days Wed 10/16/19 Wed 10/16/19
5 Closing of Project 11 days Thu 10/17/19 Thu 10/31/19
5.1 Appraisal 2 days Thu 10/17/19 Fri 10/18/19
5.2 Post Project Review 4 days Mon 10/21/19 Thu 10/24/19
5.3 Submit Final Project Report 5 days Fri 10/25/19 Thu 10/31/19
5.4 Milestone 5: Sign Off 0 days Thu 10/31/19 Thu 10/31/19
The work breakdown structure is also shown in the following diagram.
Figure 1: Work Breakdown Structure

(Source: Created by Author)

A.3. WBS Activity Decomposition
Define the activities within each work package and provide a description.
WBS Task Name Task Description
0 Website Upgrade for ABC Software Private Limited
1 Survey and Discussion of Project
1.1 Identify the issues with the current website Conduct survey on the current website to identify issues faced
1.2 Analyze the implications of the issues Analysis of the issues and their implications on the business of the
company
1.3 Prepare for Team Meeting Call meeting of the stakeholders for discussion regarding the issues
1.4 Discuss about website upgrade Discuss if the website upgrade is an appropriate solution for the
company
1.5 Check for project feasibility Check whether the proposed upgrade is feasible for the company in
terms of budget, time and final end product
1.6 Milestone 1: Confirmation of Project
2 Estimation and Planning of the Project
2.1 Develop project team
2.2 Primary Plan
2.2.1 Set project goals based on requirements Determination of final goals of the project
2.2.2 Identify Project Scope Determine the scope of the project as per the requirements

2.2.3 Determine Project Life Cycle Select an appropriate project life cycle as per the requirements
2.2.4 Develop work breakdown structure for the project Develop the work breakdown structure after developing the work
packages
2.2.5 Determine appropriate schedule based on the work breakdown
structure
Determine a feasible schedule for the overall project
2.2.6 Estimate Budget Determine a feasible and sufficient budget for the project
2.3 Secondary Plan
2.3.1 Determine risks associated with the project Identify the possible risks that may hamper the project
2.3.2 Develop Risk Register Develop a risk register table and analyze the risks using the same
2.3.3 Prepare Mitigation Plan for Risks Develop management plans to mitigate all the risks identified
2.3.4 Review overall project plan Analyze the project plan for further modifications and changes
2.3.5 Develop suitable quality management plan Develop appropriate quality standards for the purpose of the project
2.4 Milestone 2: Approval to Proceed in Project
3 Initiation of Project
3.1 Procure Budget Procure project budget from management or sponsor
3.2 Recruit Developer and Tester Recruit the project team who will responsible for executing the
project
3.3 Allocate Roles in Project Allocate the roles to the developer and tester as per the project
requirements

3.4 Purchase Hardware Purchase hardware for hardware upgrade
3.5 Purchase Software Purchase software for software upgrade
3.6 Milestone 3: All Preparations Complete
4 Execution of Project
4.1 Upgrade Hardware System Upgrade all the existing hardware available
4.2 Set Up Software Platform Set up the software for website upgrade
4.3 System Development
4.3.1 Upgrade Website Upgrade the existing website with new and updated codes and
interface
4.3.2 Initial Testing Initial testing for the checking of performance of the updated site
4.3.3 Addition of Features Add new features to the website as per the requirements of the
company
4.3.4 Develop business portal Design and implement a business portal suitable for the company
4.3.5 Beta Testing Beta testing of the website before launch
4.3.6 Completion of Design Complete the design and development
4.4 Testing the Website
4.4.1 Reconnect with Central Server Reconnect the website with the company server
4.4.2 Test Website Features Final testing of the website performance and features
4.4.3 Identify and Solve Issues Identify and solve the existing bugs and issues

4.5 Milestone 4: Go Live
5 Closing of Project
5.1 Appraisal Appraise the entire project team
5.2 Post Project Review Review the overall project using checklist
5.3 Submit Final Project Report Develop and submit project report
5.4 Milestone 5: Sign Off

A.4. Activity Dependencies & Sequencing
Nominate the predecessor(s) and type, date constraint and logic for dependency and sequence.
Date constraint types:
 As Soon As Possible (ASAP) - the activity will start at the project estimated start date (no constraint will be set)
 Start No Earlier Than (SNET) - the activity will start at the selected date or later (if it is "pushed" by links)
 Start No Later Than (SNLT) - the activity can't start later than the selected date, even if a link is forcing this (in this situation an error message may appear and the
command will not be executed)
 Finish No Earlier Than (FNET) - the activity will end at the selected date or later
 Finish No Later Than (FNLT) - the activity can't end later than the selected date, even if a link is forcing this (in this situation an error message may appear and the
command will not be executed)
 Must Start On (MSO) - the activity will start exactly at the selected date
 Must Finish On (MFO) - the activity will end exactly at the selected date.
 By default, the date constraint is “ASAP,” which allows the activity to “float” relative to its dependency on other activities.
WBS Task Name Predecessors &
Type
Date
Constraint
Dependency & Sequence logic
0 Website Upgrade for ABC Software Private Limited
1 Survey and Discussion of Project
1.1 Identify the issues with the current website ASAP
1.2 Analyze the implications of the issues 2 (FS) ASAP The previous activity must finish before this activity
can be initiated.
1.3 Prepare for Team Meeting 3 (FS) ASAP The previous activity must finish before this activity
can be initiated.
1.4 Discuss about website upgrade 4 (FS) ASAP The previous activity must finish before this activity
can be initiated.
1.5 Check for project feasibility 5 (FS) ASAP The previous activity must finish before this activity
can be initiated.

1.6 Milestone 1: Confirmation of Project 6 (FS) ASAP The previous activity must finish before this activity
can be initiated.
2 Estimation and Planning of the Project
2.1 Develop project team 7 (FS) ASAP The previous activity must finish before this activity
can be initiated.
2.2 Primary Plan
2.2.
1 Set project goals based on requirements 9 (FS) ASAP The previous activity must finish before this activity
can be initiated.
2.2.
2 Identify Project Scope 11 (FS) ASAP The previous activity must finish before this activity
can be initiated.
2.2.
3 Determine Project Life Cycle 12 (FS) ASAP The previous activity must finish before this activity
can be initiated.
2.2.
4 Develop work breakdown structure for the project 13 (FS) ASAP The previous activity must finish before this activity
can be initiated.
2.2.
5
Determine appropriate schedule based on the work
breakdown structure 14 (FS) ASAP The previous activity must finish before this activity
can be initiated.
2.2.
6 Estimate Budget 15 (FS) ASAP The previous activity must finish before this activity
can be initiated.
2.3 Secondary Plan
2.3.
1 Determine risks associated with the project 16 (FS) ASAP The previous activity must finish before this activity
can be initiated.
2.3.
2 Develop Risk Register 18 (FS) ASAP The previous activity must finish before this activity
can be initiated.
2.3.
3 Prepare Mitigation Plan for Risks 19 (FS) ASAP The previous activity must finish before this activity
can be initiated.
2.3.
4 Review overall project plan 20 (FS) ASAP The previous activity must finish before this activity
can be initiated.
2.3.
5 Develop suitable quality management plan 21 (FS) ASAP The previous activity must finish before this activity
can be initiated.
2.4 Milestone 2: Approval to Proceed in Project 22 (FS) ASAP The previous activity must finish before this activity