PM FPX 4080 Assessment 5

Part 1: Sprint Plan

PM FPX 4080 Assessment 5:Sprint Goal

The main goal for this sprint is to lift customer retention by 20% by creating a state-of-the-art, mobile app-controllable thermostat system. Previously, the CapraTek’s Alfred product line has not lived up to profit, revenue-generating, and customer interest expectations primarily due to the incompatibility with mobile apps. In team meetings, there was a consensus that providing a product superior to what the competition can provide is crucial. This goal is one of the major motivators for the team to finish the sprint backlog as well as meet customer satisfaction.

For this goal to be realized, the project team has to finish backlog tasks specially designed to resolve customer retention problems. Some of the most important jobs for this sprint include creating an iOS mobile app to manage the Alfred thermostat system, software implementation to provide Wi-Fi support to the app, and programming thermostat features for users’ convenience. This feature will allow customers to set thermostat temperatures, track usage patterns, and receive energy-saving notifications. These goals not only guide the project team but also provide stakeholders with a clear understanding of the project vision. 

Roles and Responsibilities

At the project planning session, Rachel Davis, Smart Home Technologies Project Manager, was designated as the Scrum Master, and Darren Stokes, one of the developers at CapraTek, was designated as Product Owner. Rachel, being the Agile process expert, will oversee stakeholder interaction and a hassle-free process of implementation. Darren, as being developed on top of current Alfred products, has first-hand knowledge of the customers’ requirements and will prioritize tasks in relation to these and avoid wastage of development time. The remaining team members will be part of the Scrum team and will work synergistically to carry out the activities as per the project backlog.

Rachel’s duties encompass tracking the performance of teams, holding daily stand-up meetings, solving problems, enforcing Scrum practice compliance, and helping Darren with the backlog. As the Product Owner, Darren has the duty of maintaining the backlog current, prioritizing, detecting market needs, overseeing development cycles, and measuring progress following each sprint. Both functions are critical in facilitating stakeholders’ walkthrough of the Agile process as well as ensuring effective project execution.

Sprint Burndown Chart

The burndown chart below indicates the progress throughout the length of the 22-day sprint:

[Insert Burndown Chart Here]

Part 2: Updated Burndown Chart

“Done” Definition

The product will have to be reviewed at the end of each sprint to ensure it is complete against the completion criteria. For the current sprint, the Alfred thermostat will have an iOS password-protected security system, a working dashboard interface for thermostat control, customizable dashboard preferences with trend drawings, and customer notifications on energy-efficient controls. To ensure completion, functionality testing, code reviews, static code analysis, unit testing, and performance testing shall be performed, along with corrective measures where required. Once these quality check tasks are done, the sprint is considered done so that the team can proceed.

The stand-up meetings every day are important to discuss the issues, monitor progress, and provide suggestions for day-to-day development of the mobile app. The team needs to agree to the ending of the sprint; otherwise, the sprint can’t be regarded as concluded. In accordance with the Agile Alliance, “Failure to meet these criteria at the end of the sprint normally implies that the work should not be counted toward that sprint’s velocity” (Definition, 2021).

To prevent incomplete sprint tasks, the team ought to ensure all requirements are satisfied and the customer’s needs are comprehensively catered for. It entails making judgments about whether the new product functionalities impact the aim of improving customer retention by 20%. Utilizing checklists and making specific agreements, the team can make automation of pre-implementation steps easier, decrease rework, and minimize misunderstandings or disagreements among team members and customers (Definition, 2021).

Here is the revised burndown chart, including team member sickness and required training. Despite a one-day lag, the team has one day left, and this satisfies the stakeholders that the issues were resolved.