Description
QSO 340 Project Three Guidelines and Rubric
Competency
In this project, you will demonstrate your mastery of the following competency:
Analyze and reflect on factors that commonly lead to the success or failure of a project
Scenario
You have reached the end of Release One of the XYZ Business Workflow project, and your team has faced some challenges during the development process.
One software tester and one developer from your team resigned. You found replacements for both of them. But, the new developer had to be trained by one of your other team members. This affected the team’s productivity.
Also, during one of your status meetings with the client stakeholders, their product owner requested a change in a feature that was almost complete. They were also very resistant to give any additional time for the first release. As a result, you had to add extra hours to your development time.
To accommodate these changes, your team worked extra hours and even some weekends to complete the project. Finally, you managed to deliver the first release according to schedule.
Although the release goes fairly smoothly, after a few days, the customer reports that their users are facing some issues with the software. They also have a list of changes and two new features they would like to see in the software before your final rollout in Release Two.
Directions
Analysis and Recommendations
Your executive team has asked you to prepare a report summarizing your analysis of the first release of the XYZ Business Workflow software and recommendations for how you think Release Two of the project should be planned.
Think about the project charter, the initial project plan you created in Project One, and the challenges the project team has faced so far. What steps did you take to manage these challenges? In retrospect, can you think of some other strategies you could have used during project planning and/or risk mitigation for better results? Specifically, your report should include the following:
Reflect on the project so far and provide your analysis of what went well and what could have been better.
Outline what you think were the successes and failures of the project.
Identify major challenges your team faced in completing this project and describe how you handled them.
List some alternate strategies you could have used during project planning and/or during risk mitigation for better results.
Based on your experience with Release One, provide some recommendations for managing the second release of the XYZ Business Workflow software, including the methodology, change management, and quality control strategies.
Use information from the scenario, Project One and Project Two, and make reasonable assumptions as you complete these tasks. Be sure to explain your assumptions.
What to Submit
To complete this project, you must submit the following:
Project Analysis Recommendations
Write a short paper with your analysis of the first phase of the software development project and your recommendations for the second phase. Your paper should be 750 to 1,250 words in length; cite any references using the APA format.
Unformatted Attachment Preview
1
QSO 340 Project One
Cherelle Pratt
QSO 340- Project Management
September 17, 2023
2
QSO 340 Project One
Stakeholder Register
This entails a project management document with the relevant information regarding the
respective project stakeholders (Usmani, 2021). Therefore, the stakeholder register in this case is
as follows.
Name
Cherelle Pratt
Role
Project Manager
Michael Lee
Software Architect
[UI Designer]
User Interface
Designer
UI Developer
[UI Developer]
[Technical Team
Leads]
[Software
Developers]
[Software Testers]
Technical Team
Leads
Software Developers
Julia Smith
Product Manager
Ryan Hernandez
Team Lead (ABC
Workflow)
Software Testers
Influence on Project
High – Responsible for project planning and
execution.
High – Responsible for the technical aspects of the
project.
High – Critical for the UI redesign aspect of the
project.
Medium – Responsible for implementing the UI
changes.
Medium – Coordinate the development teams and
provide technical guidance.
Medium – Responsible for developing software
features and customizations.
Medium – Ensure software quality through testing and
validation.
Medium – Represents ABC Workflow v3.0 and
provides insights into requirements.
Low – Provides insights into the existing ABC
Workflow v3.0.
Risk Register
This entails a project risks table allowing project managers to easily track the pinpointed
risks and related information about them (Uzulāns, 2016). Therefore, the risk register in this case
is as follows.
Risk
ID
Description
of Risk
R1
Software
Compatibility
R2
Resource
Availability
Probability
of
Occurrence
Medium
Impact
on the
Project
High
Medium
High
Response Plan
Person
Responsible
Status
Conduct thorough
compatibility testing.
Adapt or replace
incompatible
components.
Ensure resource
allocation and backup
plans. Consider
outsourcing if
necessary.
Software
Architect
Open
Project
Manager
Open
3
R3
Scope Creep
Low
High
R4
Stakeholder
Conflicts
Low
Medium
Clearly define and
document project
scope. Implement
strict change control
procedures.
Establish effective
communication
channels. Mediation
if conflicts arise.
Project
Manager
Open
Project
Manager
Open
Description of Risks:
❖ Software Compatibility (R1): The new software may not work with some XYZ Financial
Services systems, causing integration issues.
❖ Resource Availability (R2): Other projects may limit full-time software developers, testers,
and UI designers, affecting project timelines.
❖ Scope Creep (R3): Uncontrolled project scope changes that delay and increase development.
❖ Stakeholder Conflicts (R4): Stakeholder disagreements can undermine project decisionmaking and progress.
Work-Breakdown Structure (WBS)
This entails a project management tool which uses a stepwise approach to deal with large
projects containing numerous moving pieces (Organ, 2023).
The Tasks and Milestones
Project Initiation
➢ Define Project Scope
➢ Create Project Charter
➢ Identify Stakeholders Requirements Analysis
Requirement Analysis
➢ Review ABC Workflow v3.0
➢ Get XYZ Financial Services Requirements
➢ Software Requirements document Design Phase
Design Phase
➢
➢
➢
➢
UI Design
Create UI
Architecture Design
Database Design
Development Phase
➢ Feature 1 Development
➢ Feature 2 Development
➢ Feature 3 Development
4
➢
➢
➢
➢
➢
Feature Customization 1
Feature Customization 2
Feature Customization 3
Feature Customization 4
Feature Customization 5
Testing Phase
➢
➢
➢
➢
Unit Testing
Integration Testing
System Testing
User Acceptance Testing
Issue Resolution
➢ Fix Software Issues
➢ Fixing Testing Issues
➢ Client Feedback Incorporation
Prototype Delivery
➢ Prototype Preparation for release
➢ Release 1: XYZ Business Workflow 1.0 (Milestone One)
Deployment
➢ Prototype deployment at two customer locations
➢ Testing and Validation
Feedback and refinement
➢ Get User Feedback
➢ Implement Refinements
➢ Release 2: XYZ Business Workflow 1.1 (Milestone Two)
Worldwide Rollout
➢ Deployment of XYZ Business Workflow 1.1 at All Customer Locations (Milestone Three)
Dependencies
On dependencies, it should be noted that from task 1-10, the current task is a prerequisite
for next one and thus precedes it as shown in the networking diagram for the work breakdown
structure below:
Networking Diagram of the WBS
[1. Project Initiation]
5
[2. Requirements Analysis]
[3. Design Phase]
[4. Development Phase]
[5. Testing Phase]
[6. Issue Resolution]
[7. Prototype Delivery]
[8. Deployment]
[9. Feedback and Refinement]
[10. Worldwide Rollout]
Responsibility Assignment Matrix
RACI Chart for Project Tasks:
Task
1. Define
Project Scope
Project
Software UI
UI
Technical Software
Software
Manager Architect Designer Developer Team
Developers Testers
Leads
R
C
C
C
C
C
C
6
2. Develop
Project Charter
R
A
I
I
I
I
I
3. Identify
Stakeholders
R
C
C
C
C
C
C
4. Requirements R
Analysis
I
C
I
I
C
C
5. Design Phase
R
A
R
A
C
I
C
6.Development
Phase
R
A
C
I
R
R
C
7. Testing Phase R
I
C
I
R
C
R
8. Issue
Resolution
9. Prototype
Delivery
10. Deployment
R
A
C
I
R
R
C
R
I
I
I
C
C
C
R
C
C
C
C
C
C
11. Feedback
and Refinement
R
A
R
A
C
R
C
12. Worldwide
Rollout
R
A
C
I
R
R
C
Consulted
C
C
A
C
C
C
C
A
A
Informed
I
I
I
I
I
I
I
I
I
RACI Chart for Stakeholders
Stakeholder
Project Manager
Software Architect
UI Designer
UI Developer
Technical Team Leads
Software Developers
Software Testers
Julia Smith (Product Manager)
Ryan Hernandez (Team Lead)
Responsible
R
R
R
R
R
R
R
R
R
Accountable
A
A
C
A
A
A
A
C
C
RACI Roles Explanation
❖ Responsible (R): A person or team in charge of a task or role.
❖ Accountable (A): The person responsible for completing the task. This usually involves one
person.
❖ Consulted (C): This entails those offering input and are consulted before decision making.
❖ Informed (I): Those who are informed of the task’s progress or outcome but don’t participate.
7
Generally, the RACI chart improves project team and stakeholder communication and
responsibility (Miranda, 2022).
8
References
Miranda, D. (2022, March 25). What Is A RACI Chart? How This Project Management Tool Can
Boost Your Productivity. Forbes Advisor. https://www.forbes.com/advisor/business/racichart/#:~:text=A%20RACI%20chart%2C%20also%20called
Organ, C. (2023, March 23). Work Breakdown Structure (WBS) In Project Management. Forbes
Advisor. https://www.forbes.com/advisor/in/business/what-is-work-breakdownstructure/#:~:text=A%20work%20breakdown%20structure%20(WBS
Usmani, F. (2021, August 24). Stakeholder Register in Project Management. PM Study Circle.
Uzulāns, J. (2016). Project Risk Register Analysis Based on the Theoretical Analysis of Project
Management Notion of Risk. Economics and Business, 29(1), 43–48.
https://doi.org/10.1515/eb-2016-0020
Project Status Report
•Subtitle: XYZ Business Workflow Project
•Date: 10/01/2023
•Presenter: Cherelle Pratt
Introduction
• Welcome to the status report for the XYZ Business
Workflow Project.
• The project is at week 10 and this report will give an
overview of its development, as well as the project’s
current timeline, risk register, and any other pertinent
information.
Project Goal and Objectives
• The XYZ Business Workflow project’s
objective is to create a system that would
simplify processes and offer the features
required to boost business productivity.
• The project’s goals include the following:
• Create the first feature, the second, the third,
and the system testing.
• Ensure the project is delivered on time, within
budget, and to the agreed-upon quality
(Wijaya et al. 2022).
• Identify and manage any risks related to the
project.
Team Information
• The XYZ Business Workflow project is led by
Cherelle Pratt and consists of the following
team members and their roles:
• Cherelle Pratt: Project Manager
• Software architect—Michael Lee
• Technical team lead—To be decided (TBD)
• Software developers—TBD
• Software testers—TBD
• UI design and development team—TBD
• Julia Smith—Product Manager (ABC
Workflow v3.0)
• Ryan Hernandez—Team Lead (ABC Workflow
v3.0)
Initial Schedule
with Milestones
and End Dates
Current
Project Status
• The project’s state as of right now
is as follows:
• First Feature: 5 Weeks (1 Week
Delayed)
• Second Feature: 10 Weeks
• Feature Customization 3: 5 Weeks
• System Testing: 1.5 Weeks
• The project’s current anticipated
completion date is 28/12/2023
Gantt Chart For Project’s Progress And
Current Schedule
Task
First Feature
Second Feature
Feature
Customization
System Testing
Project Completion
Week Week Week Week Week Week Week Week Week Week
1
2
3
4
5
6
7
8
9
10
The following is the most recent risk/issues
registry for the XYZ Business Workflow
project:
Updated
Risk/Issues
Register
➢ Risk 1: A delay in receiving client
approvals
➢ Risk 2: A one-week overrun in UI design
and development
➢ Risk 3: A three-day increase in Feature 1
development effort due to a problem with
resource availability.
➢ Problem 1: The wait for client approvals
➢ problem 2: UI design and development
are taking a week longer than expected.
➢ Problem 3: A problem with resource
availability extends the development effort
for Feature 1 by three days.
Project
Summary
Project Summary
Continuation
• Action items to keep the project on schedule
include:
➢ Ensure that all parties involved are aware of
any delays
➢ Regularly check on progress and update
parties involved
➢ Determine potential hazards and create
mitigating strategies
Closing
• We appreciate you reading this project status
report. Please do not hesitate to contact us if
you have any questions.
Reference
➢
Wijaya, S., Sari, M. H. R. S. R., & Supriatna, Y.
(2022). Integrated Information System of Material
Resource Planning and Supply Chain Procurement:
A Case Study of XYZ Company. CommIT
(Communication and Information Technology)
Journal, 16(2), 183-193.
https://doi.org/10.21512/commit.v16i2.7945
Purchase answer to see full
attachment
