PM FPX 4080 Assessment 5 The Sprint

PM FPX 4080 Assessment 5 The Sprint

Student Name

Capella University

PM-FPX4080 Agile Project Management

Prof. Name:

Date

Part 1: Sprint Plan

Sprint Goal

The goal for this sprint is to improve customer retention by 20% through the implementation of a highly effective thermostat that can be adjusted from a mobile app. In prior projects, CapraTek’s Alfred products have not achieved the desired success in terms of profitability, revenue, or customer interest, largely because the product lacked mobile application compatibility. The project team has discussed and agreed that providing customers with a product that surpasses competitors’ offerings is a priority. Achieving this goal not only motivates the team to complete the sprint backlog but also ensures customer satisfaction.

To meet this goal, the project team must complete the backlog tasks aimed at reducing customer retention issues. The sprint goal also outlines subsequent objectives, including designing an iOS mobile application to control the Alfred system, developing a stable software to support Wi-Fi capabilities for the mobile app, and programming the thermostat features for customer use. Customers will not only be able to adjust the thermostat temperature but also monitor trends and receive energy efficiency notifications. These goals guide the team throughout the project and make the vision clear to stakeholders.

Sprint Tasks

After identifying the most important tasks and adding them to the backlog, the following tasks have been scheduled for the first sprint:

Roles and Responsibilities

During the project preparation meeting, it was decided that Rachel Davis, the Smart Home Technologies Project Manager, will serve as the Scrum Master, while Darren Stokes, a developer at CapraTek, will act as the Product Owner. Rachel, with her knowledge of Agile methodology, will facilitate stakeholder engagement and ensure smooth implementation. Darren, having experience with previous Alfred products, understands customer needs and will create a prioritized list of tasks based on his expertise, helping avoid inefficiencies. The remaining team members will form the Scrum team and work together to execute the tasks in the project backlog.

Rachel will oversee team performance, conduct daily stand-up meetings, address challenges, ensure adherence to Scrum practices, and assist Darren in managing the product backlog. Darren, as the Product Owner, will be responsible for managing the backlog, prioritizing tasks, understanding market needs, overseeing development stages, and evaluating progress after each sprint. Both roles are critical in helping stakeholders adapt to the Agile approach and ensure the successful execution of the project.

Sprint Burndown Chart

The burndown chart below illustrates the progress made during the 22-day sprint:

“Done” Definition

At the end of each sprint, the product must undergo review to be considered complete. For this sprint, the thermostat must have a password-protected security system on iOS, a functional dashboard interface displaying thermostat settings, changeable dashboard preferences illustrating trends, and alerts notifying customers via the mobile app about energy-efficient settings. To ensure completion, developers will conduct functionality testing, code reviews, static code analysis, unit testing, performance testing, and corrective actions. Once these quality assurance measures are passed, the sprint is considered complete, allowing the team to move to the next sprint.

Daily stand-up meetings are essential for discussing task challenges, tracking progress, and providing recommendations for the ongoing development of mobile app features. The entire team must agree on the sprint’s completion before proceeding; otherwise, the sprint is not considered done. As stated by 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 avoid incomplete sprint tasks, the team must ensure that all requirements are met and that customer needs are fully considered. This involves determining if the new product features align with the 20% customer retention goal. By using checklists and explicit agreements, the team can streamline pre-implementation activities, limit rework, and minimize misunderstandings or conflicts among developers and customers (Definition, 2021).

Part 2: Updated Burndown Chart

Below is the updated burndown chart, which reflects team member sickness and mandatory training. Despite a one-day delay, the team still has one day to spare. The stakeholders are reassured that these occurrences have been accounted for.

References

Capella University. (n.d.). Sprint Planning Meeting. Capella Media. Retrieved February 8, 2022, from https://media.capella.edu/CourseMedia/pmfpx4080element236975/transcript.asp#scenario1

PM FPX 4080 Assessment 5 The Sprint

Definition of done. Agile Alliance. (2021, March 3). Retrieved February 8, 2022, from https://www.agilealliance.org/glossary/definition-ofdone/#q=~(infinite~false~filters~(postType~(~’page~’post~’aa_book~’aa_event_session~‘ aa_experience_report~’aa_glossary~’aa_research_paper~’aa_video))~searchTerm~’~sort~ false~sortDirection~’asc~page~1