• Home
  • Southern New Hampshire University
  • Introduction to Data and Information Management IT204
  • Introduction to Data and Information Management

Introduction to Data and Information Management

Course: QSO-340-X5861 Project Management 20EW5 Student's name: Salome Odipo Name of School: South New Hampshire University Date: 21st June 2020 Introduction The purpose of this document is to present the analysis of the first phase of the software development project and recommendations for the second phase. Some of the major project objectives were: Deliver a customized software solution to XYZ Financial Services : Develop the customized solution as per the initial and agreed upon schedule Conduct usability training once the software solution has been deployed Successes of the project One of the most notable successes of the project was that our team worked extra hard to complete the project and we managed to complete the project according to the agreed upon schedule. Secondly, despite facing a myriad of challenges, we were still able to deliver the customized software solution. Failures of the project Even though we found an immediate replacement for our software developer, it would have been appropriate to hire a developer who did not need to be trained as this affected the team's productivity. Secondly, since the product owner was reluctant to give additional time for the first release, our team should have shelved changes that would have caused too much delay to the second release and instead focused on the core features. Challenges of the Project 1. Finding replacement for team members who resigned in time and bring them on board to the project. To mitigate this challenge and reduce the after effect of team member leaving the project halfway, we should promote a more cohesive team which works together to ensure that someone else can perform the duty (Base36, n.d.) 2. Managing change requests from the product owners was another challenge as this came towards the completion of the project. Since the change was requested towards completion of the feature, the change could have been shelved until the second release. 3. The product owner was reluctant in giving additional time for the first release even though we had accepted scope changes. 4. After the deployment, users faced some challenges with the software. To mitigate this challenge, our team should plan and conduct usability training as well as further software tests to ensure the software product is running smoothly. For the first release, it would have been planned and done more effectively by: 1. Get lightweight processes which do not require lengthy bureaucratic approvals and features done early, and tested. Once this is done, they can be reviewed regularly by team members. 2. Secondly, before or during the first product release, our team should have established a release infrastructure early enough to avoid delays during deployment (CIO, 2018) 3. Establishing an appropriate positive expectation. If the software feature is important then, it should be given priority and done. Recommendations for Next Project Release