An agile team's client has been asked to expedite the delivery of the next release. By delivering one month early, the company can generate US$40,000 more than expected for the quarter. What should the agile team do?
A.
Adhere to the new deadline and immediately advise the client that the schedule has been expedited
B.
Advise the client that it is best to continue as planned rather than introduce unforeseen risks by expecting the schedule
C.
Submit a change request to the client with a 50% increase in charges due to the new potential profit
D.
Request additional resources to meet the expedited deadline and obtain training for the new resources
In this scenario, the agile team should advise the client that it is best to continue as planned rather than introduce unforeseen risks by expediting the schedule. This approach ensures that the team maintains quality and avoids potential risks associated with rushing the delivery.
Option B: Advise the client that it is best to continue as planned rather than introduce unforeseen risks by expediting the schedule is the most appropriate choice.
Detailed Points:
Risk Management: Rushing the schedule can introduce unforeseen risks, such as reduced quality, increased defects, and potential rework.
Quality Assurance: Maintaining the planned schedule ensures that the team can adhere to their quality standards and deliver a reliable product.
Stakeholder Communication: Clear communication with the client about the potential risks and impacts of expediting the schedule helps manage their expectations.
Sustainable Pace: Agile principles emphasize maintaining a sustainable pace to avoid burnout and ensure consistent performance.
Value Delivery: While the potential for increased revenue is attractive, it should not come at the cost of delivering a subpar product that could harm the company's reputation in the long run.
Summary:
In summary, the agile team should advise the client to continue with the planned schedule to avoid introducing unforeseen risks by expediting the delivery. This approach ensures that the team maintains quality, manages risks effectively, and adheres to agile principles of sustainable pace and reliable value delivery. Clear communication with the client about the potential impacts of rushing the schedule is crucial for managing expectations and maintaining a strong client relationship.
If the client accepted a change in scope, then A should have sense as it means that change is welcome even late in the development. If XP is being used, the latest version could be presented during the Sprint Review... A could make sense.
Between B or D, I choose B because Requesting additional resource and training might take time. Also delivering early one month in 3 months (quarter) time is quite aggressive improvement and risky.
B - Correct
----------
A, D - Incorrect
From PMI’s Agile Practice Guide, Page 63:
“When a team sees what it has not yet completed as it works through an iteration, the team may become dispirited and possibly rush to complete the work without meeting the acceptance criteria.”
----------
C - Incorrect - Change requests are not part of Agile.
From PMI’s Agile Practice Guide, Page 63:
“High-uncertainty projects have high rates of change, complexity, and risk. These characteristics can present problems for traditional predictive approaches that aim to determine the bulk of the requirements upfront and control changes through a change request process. Instead, agile approaches were created to explore feasibility in short cycles and quickly adapt based on evaluation and feedback.”
If we consider three legs of scrum; transparency, inspection, and adaptation, then B is the answer. Without transparency and inspection you cant go with unplanned sprint
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
2 months, 3 weeks agothewalker
2 months, 3 weeks agothewalker
2 months, 3 weeks agoPetrevski
1 year, 6 months agoInvisibleBeing
1 year, 9 months agorichck102
2 years, 4 months agozzw890827
2 years, 8 months agothuha1704
2 years, 8 months agoAzurance
3 years, 4 months agoSTW
3 years, 5 months agoDsugandhi
3 years, 5 months agoHTTPS
3 years, 6 months agosnow5
3 years, 12 months agosnow5
4 years agoWmahmoudi
4 years agoGPena
4 years agoGPena
3 years, 10 months agoGPena
3 years, 7 months agoaws_guru1
3 years, 2 months agoSrini33
3 years agotsangckl
4 years, 1 month agodiligentstudent
4 years, 1 month ago