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 primary objective for the project team during this sprint is to enhance customer retention by 20% through the implementation of a highly functional thermostat that can be controlled via a mobile app. Previous projects and feedback from team members have highlighted the limited success of CapraTek’s Alfred products in terms of profitability, revenue, and customer engagement, largely because they lacked mobile application compatibility. Consequently, the team has collectively agreed upon this goal to provide customers with a more robust product, which exceeds the offerings of competitors. This goal not only provides the team with a clear direction but also serves as a motivational factor in completing the sprint backlog and supporting the team’s efforts.

In order to meet this customer retention target, the team must complete the items listed in the backlog, ensuring that customer needs are fully addressed. Additional sprint goals include designing an iOS mobile app to control the Alfred system, developing stable software to support Wi-Fi functionality for the mobile app, and programming thermostat features for user interaction. This allows customers not only to adjust the thermostat temperature from their phone but also to view usage trends and receive notifications for energy efficiency. These objectives help guide the team throughout the project and maintain a clear project vision for stakeholders.

Sprint Tasks

After discussing and prioritizing tasks, the team has populated the backlog and established the sprint tasks for the initial phase. The chart below outlines the first sprint, along with the estimated tasks necessary to achieve the sprint goal.

Roles & Responsibilities

During the planning meeting, it was decided that Rachel Davis, the Smart Home Technologies Project Manager, would act as Scrum Master, while Darren Stokes, one of CapraTek’s developers, would serve as the Product Owner. Rachel, with her expertise in Agile methodology, will lead efforts to engage stakeholders and facilitate the project process. Darren, having worked on previous Alfred products, brings valuable insights into customer preferences and will prioritize tasks based on his experience. This will help prevent stakeholders from focusing on ineffective tasks. The rest of the stakeholders will form the Scrum team and collaborate on completing the tasks outlined in the project backlog. In addition to her Scrum Master duties, Rachel will track team performance, hold daily stand-up meetings, address challenges, and ensure Scrum practices and principles are followed. Darren will manage and prioritize the product backlog, understand market and customer needs, oversee development, and evaluate the team’s progress at the end of each sprint. These roles will be essential for guiding stakeholders through this new process.

Sprint Burndown Chart

The following is a burndown chart for the 22-day sprint:

“Done” Definition

Upon completing the sprint, it must be reviewed to ensure all tasks meet the “done” criteria. For this sprint, the thermostat must have password-protected security on the iOS device, a functioning dashboard interface for viewing thermostat settings, customizable dashboard preferences to display trends, and alerts notifying the customer’s mobile device about energy efficiency. To confirm the completion of these tasks, developers must perform functionality testing, code reviews, static code analysis, unit testing, single-user performance testing, and corrective measures.

Once these quality assurance steps are completed, the team can proceed to the next sprint. Daily stand-up meetings will be held to address task challenges, track progress, and provide recommendations on mobile app features under development. All team members must agree on the sprint’s completion before moving forward; otherwise, it is not considered done. According to Agile Alliance (2021), failure to meet these criteria means the work should not be counted toward the sprint’s velocity. To avoid incomplete work, the team must ensure that all requirements are met and that customer needs are fully considered. They must also evaluate whether the product features meet the 20% customer retention goal. Checklists and clear contracts can help guide pre-implementation activities, minimize rework costs, and reduce the risk of misunderstandings or conflicts.

Part 2: Updated Burndown Chart

The updated burndown chart accounts for a team member’s illness and unexpected mandatory training. Despite these setbacks, the team still has one day to spare, ensuring that stakeholders are accommodated for any unforeseen circumstances.

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

Agile Alliance. (2021, March 3). Definition of done. Retrieved February 8, 2022, from https://www.agilealliance.org/glossary/definition-of-done/#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)