Transparency and Stakeholder Involvement: It's crucial to keep stakeholders informed about the potential negative ROI. By communicating the risk early, stakeholders can participate in discussions about how to proceed, which could include adjusting the scope, timelines, or resources.
Updating the Plan: After communicating the risk, the release plan can be updated to reflect any changes that stakeholders agree upon. This could involve reprioritizing features, revising budgets, or even reconsidering the project's viability.
Proactive Risk Management: Addressing the issue before it becomes a larger problem allows the team and stakeholders to make informed decisions. This could help mitigate losses or find ways to increase the project's value.
Option A (removing low-priority stories) might improve ROI, but it should be done in consultation with stakeholders to ensure that critical features aren't cut. Option B (replacing team members) is not a reliable strategy for improving ROI and could disrupt the team's dynamics and productivity. Option C (performing a root-cause analysis) is a good practice for improving efficiency, but it may not address the fundamental issues leading to a negative ROI.
D. Communicate the risk of a negative ROI to the stakeholders, and update the release plan.
If the team realizes that the project is likely to have a negative ROI, it is important to communicate this risk to the stakeholders. This will allow them to make informed decisions on whether to proceed with the project or make changes to the release plan to ensure a positive ROI. The team should work with the stakeholders to update the release plan and ensure that any changes made align with the project's goals and objectives. Prioritizing the backlog, replacing team members, or performing a root-cause analysis may not necessarily address the issue of a negative ROI and could result in additional risks and issues.
I believe C is the correct answer:
Please note that the question is talking about the TEAM and not just the DEVELOPMENT TEAM. The team includes everyone.
C. Perform a root-cause analysis to remove waste from the delivery process and increase the ROI:
Why the team thinks the project will not have a positive ROI? That is the question the team needs to ask and figure out the root cause for the project not being successful. There could be many reasons, for instance: The project itself may not bring in any value to the organization, or too many unnecessary features have been added to the project and etc...The team needs to find out the problem and figure out the solutions to propose to the stakeholders before anything (like; reaching out to the stakeholders and re-prioritizing the backlog).
Why D cannot be the correct answer:
D. Communicate the risk of a negative ROI to the stakeholders, and update the release plan:
Definitely, you want to update the stakeholders, but before you do that, you need to have answers for all the questions the stakeholders will ask. The stakeholders will definitely ask the team about why the team thinks the project is not feasible. Therefore, before we reach out to the stakeholders, we need to do an analysis collaboratively and then reach out to the stakeholders with the problem and the solution to the problem.
A is talking about prioritizing back log. Which will any case should happen. Doesn't look like this issue is related to user stories/ back log prioritization. This is about waste. And it is important to identify and remove waste to improve ROI. So I would go for C.
"the team" in agile includes development team, agile practitioner and product owner. Answer should be A
upvoted 2 times
...
...
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
thewalker
3 weeks, 3 days agothewalker
3 weeks, 3 days agoELTIGANI
2 months agoELTIGANI
2 months agoNtp
1 year agofletcher_ng
1 year, 2 months agoTonyMac
1 year, 2 months agoRaksim
1 year, 4 months agoMinhha3
1 year, 5 months agoPetrevski
1 year, 5 months agoInvisibleBeing
1 year, 8 months agoInvisibleBeing
1 year, 8 months agominwang
2 years agorichck102
2 years, 2 months agothuha1704
2 years, 6 months agoAzurance
3 years, 2 months agoBakayalo
3 years, 3 months agoHTTPS
3 years, 3 months agoMokel
3 years, 9 months agoAzurance
3 years, 2 months agosrv3
3 years, 9 months agoTHenry
3 years, 8 months agonavingthomas
3 years, 7 months ago