End Stage Report

Document Information

Project name: Task Manager 002

Period: Design and Development

Issue date: 28.01.2022

Author: Tochi Izuchukwu, Project Manager

Approver: Chima Uduma, Programme Manager

Document code: TM 002

Version: 1.0

Approval

Date Name and Signature

Page 1 of 6
Notes
This project is aimed at a client who wants to build a user-friendly system that would enable
users in the company to plan and manage simple projects easily on the go.
The objective is to develop an application that can be used to plan small projects and manage
daily tasks, such as a bride planning a wedding where individuals can be added to the project,
tasks can be assigned to the various individuals and progress on each task tracked and
updated. Because of poor efficiency in managing tasks with notes, whiteboards and mere
memory, there was a resultant decrease in productivity, inefficient task management, missed
deadlines and impact on the clients bottom-line.
This project intends to achieve the following benefits;

 To help everyday users plan and execute small projects with ease.
 To boost productivity
 To manage time and communication within teams
 To provide a single location for file storage, management and easy access.

Justification of the project

Using an investment appraisal metric called NPV, it has been established that the benefits derivable
from the implementation of the project will far outweigh the cost of implementing it. As much as
possible, it has been demonstrated that this project will help the business to better manage
workflows, so the impact will on the business will be seen in manner that productivity will be
increased as well as the revenues.
Furthermore, it has been shown that over a 3-year period, the benefits of gains made from increase
in productivity that will be accruable to the business is predicted at 150% and will surely have a
positive impact on the value of the business.
Lastly, the revenue of the client is projected to increase over the 3-year period to about 50%. This
can be positively correlated to the benefits that will be achieved over the long term.

Products

Product Status

Task Manager 002 End of the design stage and awaiting the onboarding of the
developer and tester so the next stage can commence, which is the
development stage.

Page 2 of 6
Project Objectives

Target Tolerance Current State Forecast

Scope Deliverables N/A End of Design On Track

Guide Stage

Time 15.02.2022 28.02.2022 Attention Required Currently being

managed

Cost £89,296 ±10% £54,642 £35,654

Quality As per Scope in N/A On Track On Track

Project Brief.

Risks As per RAID log N/A Being Managed On Track

Benefits As per Business N/A On Track On Track

Case.

Current Stage Objectives

Target Tolerance Actual State

Scope Deliverables Guide N/A End of Design Stage

Design Stage

Time 27.01.2022 03.02.2022 Completed

Cost £24,487 ±10% On Track

Quality As per Scope in N/A On Track

Project Brief

Risks As per RAID log N/A Being Managed

Benefits To create framework N/A Being Managed

for the development of
the application.

Page 3 of 6
Next Stage Objectives

Target Tolerance Forecast

Scope Development Stage N/A On Track

as per Deliverables
Guide.

Time 28.02.2022 07.03.2022 On Track

Cost £35,654 ±10% On Track

Quality As per Scope in N/A On Track

Project Brief

Risks As per RAID log N/A Being Managed

Benefits Implementing the N/A On Track

Design outcomes

Team Performance
On the whole, the team has performed admirably with the tools available to them, although there
has been a limited understanding of the work to be delivered in the design stage. We have worked
assiduously to meet the targets and are ready for the next stage, which is critical to the completion
of the project.

Follow-on Action Recommendations

Unfinished work or open issue/risk Owner

Process maps Business Analysts

Wire frame Business Analysts

Azure DevOps Project Managers

Page 4 of 6
Issues and risks

Issue or risk

Issue- Limited understanding of the work scope that is expected to be delivered.

Issue- No work synergy among the team which leads to delays in meeting work deadlines.

Risk- as per RAID log

Lessons Learned

Lesson Learned

There should have been more persons added to the BA team as against the two we had. This
had an impact on their workload and affected their ability to deliver on time.

There should have been a designated PMO to carry out PMO duties full time and assist the team
where necessary. Rotating this role was disruptive and created lags in meeting the deliverable
timelines.

PSR meetings should have had a specific day, preferably Saturdays which is at the end of the
week- to test deliverables met and plan for the next week’s deliverables. Having them on
Mondays was disruptive as it was the beginning of a new week for new deliverables.

Page 5 of 6
Page 6 of 6