Explanation
According to the Agile Practice Guide, a burnup chart is a graphical tool that shows the amount of work completed and the total amount of work in a project or sprint. It helps to visualize the progress and scope of the project or sprint, and to identify any changes or deviations that may occur. In this scenario, the burnup chart shows that the team has added new work to the sprint after it has started, as indicated by the upward slope of the total work line. This is a violation of the agile principle of delivering working software frequently and satisfying the customer through early and continuous delivery of valuable software. Adding new work to the sprint after it has started may disrupt the team's focus and flow, increase the complexity and uncertainty of the sprint, and compromise the quality and value of the deliverable. The project lead should address this issue with the product owner and the team, and remind them of the importance of respecting the sprint commitments and avoiding scope creep. The project lead should also help the product owner and the team to prioritize and refine the product backlog, and to plan and execute the sprints in a consistent and predictable manner. The project lead should also encourage the product owner and the team to communicate and collaborate effectively, and to seek and provide feedback regularly. Creating a burnup chart and mapping assumptions to impediments based on the impact to the project value (option C) is the best solution to the issue, as it demonstrates proactive and effective project integration and risk management. The team is not meeting the expectations of the product owner (option A) may not be true or fair, as the team may still be able to deliver the expected value and quality within the sprint timebox, despite the addition of new work. However, this option does not address the root cause of the issue or provide a constructive feedback to the product owner and the team. The product owner should not ask the team to change their sprint commitments (option B) may also be partially correct, as the product owner should respect the team's autonomy and capacity, and should not impose unrealistic or unnecessary changes to the sprint scope. However, this option does not consider the possibility that the team may have added new work to the sprint without the product owner's request or approval, or that the product owner and the team may have agreed to change the sprint commitments based on new information or feedback. The team should have stopped on day 4 and started a new sprint (option D) may also be impractical or inefficient, as it may waste the time and effort that the team has already invested in the current sprint, and may create unnecessary overhead and disruption to the project flow. Stopping and starting anew sprint may also not guarantee the improvement of the project performance or delivery, unless the product owner and the team address the underlying issue of adding new work to the sprint after it has started. References: : Project Management Institute. (2017). Agile Practice Guide. Newtown Square, PA:
Author1 : What is a Burn Up Chart & How to Create One | Atlassian 2 : What Is a Burn Up Chart In Agile Project Management1 : What Is a Burndown Chart? | Coursera 3