Our orders are delivered strictly on time without delay 
5-2 Project Two: Project Status Report
Cole Staats
Southern New Hampshire University
QSO-340 Project Management
Timothy Brecheen
June 4, 2023
1
PROJECT’S PURPOSE AND GOALS
The project's main objective is to design a Financial Services custom software solution to optimize workflows and procedures.
To achieve this goal the following is needed:
Requirement gathering
Business analysis
Design and architecture
Development and coding
Testing and quality assurance
Deployment and integration
User training and documentation
Maintenance and support
2
INFORMATION OF THE TEAM
The people working on this project are:
Project Manager – John Goodwill
Team Lead – Sarah Whiteston
Software Architect – Michael Burton
Technical Team Lead – Neil Kimber
Project Sponsor – Dennis Morgan
Stakeholders
Employees
Except for the project's sponsor, everyone involved will be present at the actual event.
Email will be used to get in touch with the project manager.
3
INITIAL SCHEDULE
| Milestone | End Date |
| Development | 20/09/2023 |
| UI design and development | 20/08/2023 |
| Attaining the software | 20/09/2023 |
| Customization | 10/11/2023 |
| Client approvals | 14/10/2023 |
| Obtaining the prototype | 29/11/2023 |
| Testing | 18/12/2023 |
4
2023
2023
Today
Jun
Jul
Aug
Sep
Oct
Nov
Dec
73 days
0%
Development
22 Jun – 30 Sep
50 days
0%
UI design and development
22 Jun – 30 Aug
23 days
0%
Attaining the software
31 Aug – 30 Sep
22 days
0%
Customization
1 Oct – 1 Nov
12 days
0%
Client approvals
1 Oct – 16 Oct
23 days
0%
Obtaining the prototype
17 Oct – 18 Nov
17 days
0%
Testing
19 Nov – 12 Dec
STATUS RISKS
There is a high probability that the initiative will succeed in the end.
It has significant risks, though, which might prevent it from reaching its targets.
The main risk is that the project could be finished later than expected.
The project runs the risk of costing more than originally estimated.
6
PROBLEMS THAT FACE THE TEAM
Getting customer buy-in is a major hurdle the team must overcome.
The team is also finding that designing and developing the UI is more difficult than initially anticipated.
The team's essential resources are in short supply.
Due to anticipated delays in the fulfillment of milestones, it is possible that the project's completion date will be extended.
7
NEWLY IDENTIFIED HAZARDS AND METHODS FOR ADDRESSING THEM
Concerns about data security pose the biggest threat to the project's success.
As scientific and technological progresses continue to accelerate, more and more cybercriminals are targeting internet services.
Encrypting any financial dealings related to the project is the best method to avoid such a threat.
Data loss is another possible hazard.
To lower the risk, we'll use a backup service.
8
MODIFIED COMPLETION AND MILESTONE DATES
| Milestone | End Date |
| Development | 05/10/2023 |
| UI design and development | 06/08/2023 |
| Attaining the software | 10/10/2023 |
| Customization | 11/11/2023 |
| Client approvals | 18/10/2023 |
| Obtaining the prototype | 19/11/2023 |
| Testing | 20/12/2023 |
9
THE NEXT STEPS
Each member of the team will be responsible for a certain aspect of project management.
The project manager will maintain involvement throughout the duration of the project to guarantee smooth operations.
Each project milestone will be followed by a review.
We will use a Gantt chart, a useful tool for quality control.
Everyone involved in the project must contribute to the manager's efforts to maintain a high standard of quality.
10
References
Gerlero, P. (2021). Successes and failures in software development project management: a systematic literature review. In CEUR Workshop Proceedings. DOI:
dos Santos, R. A., Vieira, D., Bravo, A., Suzuki, L., & Qudah, F. (2022). A systematic mapping study on the employment of neural networks on software engineering projects: Where to go next?. Journal of Software: Evolution and Process, 34(3), e2402.
11
