PM FPX 4080 Assessment 3 Project Schedule and Product Backlog
PM FPX 4080 Assessment 3 Project Schedule and Product Backlog
Name
Capella University
PM-FPX 4080 Agile Project Management
Prof. Name
Date
PM FPX 4080 Assessment 3 Project Schedule and Product Backlog
Introduction
A well-organized product backlog and project schedule help development teams prioritize features, manage deadlines, and deliver a reliable product that meets user needs. For CapraTek’s smart thermostat iOS application, the project backlog identifies essential features such as network security, energy-saving notifications, thermostat setting management, remote access, and an intuitive user interface. The project schedule translates these requirements into specific development tasks, estimated durations, priorities, and completion dates.
This project plan focuses on improving the customer experience while maintaining security and usability. High-priority features address essential functionality and documentation requirements, medium-priority features improve convenience and household control, and low-priority features introduce additional scheduling and support capabilities. By connecting user stories to scheduled tasks, the project team can monitor progress, coordinate quality assurance (QA), and prepare for product deployment.
The original project schedule covers February through August 2022. These dates are retained as historical planning information rather than current deadlines. The backlog and schedule can also serve as a reference for understanding agile product development, feature prioritization, and project schedule management.
Part 1: Smart Thermostat Product Backlog
What Is a Product Backlog?
A product backlog is an organized list of product requirements, enhancements, and user stories that guide software development. Each user story describes a feature from the perspective of the person who will use or benefit from it. Assigning priorities helps the team determine which requirements should be addressed first.
For the CapraTek smart thermostat project, the backlog emphasizes security, energy efficiency, visibility of thermostat settings, and ease of use. Additional features support remote temperature control, parental restrictions, installation assistance, scheduling flexibility, and conflict notifications.
High-Priority Product Backlog Items
User story 1: Protect the home network.
As a user, I want the thermostat to protect my home network from security vulnerabilities so that adding a connected device does not unnecessarily increase the risk of hacking or unauthorized access.
Priority: High.
The development team should prioritize secure authentication, appropriate access controls, secure communications, and testing for potential vulnerabilities. Security should be considered throughout development rather than treated as a final deployment task.
User story 2: Promote energy-efficient settings.
As a user, I want the application to notify me when I select an energy-saving thermostat setting so that I can make more environmentally responsible choices and potentially reduce energy consumption.
Priority: High.
The application should clearly identify energy-saving options and provide understandable feedback when users select them.
User story 3: Display current thermostat settings.
As a user, I want to view all active thermostat settings on my iOS device so that I can review the current configuration and confirm that the system is operating as intended.
Priority: High.
The dashboard should present important settings in an organized, readable format, allowing users to identify their current temperature targets and schedules quickly.
User story 4: Provide final interface designs to the technical writer.
As a technical writer, I want access to the final user interface designs at least three weeks before the product launch so that I can prepare accurate user guides and supporting documentation.
Priority: High.
The project team should establish a documentation milestone that allows sufficient time to prepare, review, and finalize instructions before launch.
User story 5: Customize thermostat settings views.
As a user, I want to change how thermostat settings are displayed on my iOS device so that I can identify patterns, review settings more easily, and spot possible configuration errors.
Priority: High.
Flexible viewing options can help users interpret schedules and settings more effectively. The interface should make important information easy to compare without creating unnecessary complexity.
Medium-Priority Product Backlog Items
User story 6: Manage the thermostat remotely.
As a user, I want to add new settings and manage my thermostat through my iOS device from different locations so that I can control my home environment when I am away.
Priority: Medium.
Remote management should provide convenient access while enforcing authentication and appropriate security protections.
User story 7: Adjust temperatures using a spinner control.
As a user, I want a spinner or similar interactive control for changing thermostat temperatures so that I can adjust settings quickly and easily from my phone.
Priority: Medium.
The temperature control should be intuitive, responsive, and accessible, with clear feedback showing the selected temperature.
User story 8: Provide an intuitive user interface.
As a user, I want the thermostat application to have an intuitive interface so that I can complete common tasks without spending unnecessary time learning how to use the system.
Priority: Medium.
The design should use consistent navigation, understandable labels, clear feedback, and a layout that supports users with different levels of technical experience.
User story 9: Prevent unauthorized changes by children.
As a parent, I want to lock or restrict thermostat controls so that children cannot make unwanted temperature changes when I am away from home.
Priority: Medium.
The application should offer suitable access restrictions or a thermostat lock feature to help households maintain their preferred settings and manage energy use.
Low-Priority Product Backlog Items
User story 10: Provide thermostat installation assistance.
As a user, I want installation instructions and assistance within the application so that I can access the information needed to install and configure my thermostat correctly.
Priority: Low.
The application should provide clear setup guidance, supported installation steps, and troubleshooting information where appropriate.
User story 11: Adjust settings when arrival times change.
As a user, I want to notify the thermostat that I will arrive home later than expected so that it can adjust the schedule automatically without requiring me to change each setting manually.
Priority: Low.
This feature should make it easier to accommodate changing routines while allowing users to review or override automatic adjustments.
User story 12: Identify conflicting thermostat settings.
As a household member, I want to receive a notification when my thermostat settings conflict with settings entered by another authorized user so that we can resolve scheduling disagreements before they affect the household.
Priority: Low.
The application should identify conflicting schedules or temperature targets and provide a clear way to review and resolve them.
User story 13: Schedule settings for future dates.
As a user, I want a calendar that allows me to select individual dates or date ranges for thermostat settings so that I can prepare for vacations, school holidays, and other changes in my routine.
Priority: Low.
The calendar should make it easy to create temporary schedules and return to the regular thermostat program when the selected period ends.
Product Backlog Summary
The following table summarizes the 13 user stories and their assigned priority levels.
| Backlog ID | Feature | Priority |
|---|---|---|
| 100-013 | Protect the iOS application with secure login | High |
| 100-009 | Notify users about energy-efficient settings | High |
| 100-001 | Display all current thermostat settings | High |
| 100-004 | Provide final UI information to the technical writer | High |
| 100-002 | Customize thermostat setting views and identify trends | High |
| 100-003 | Manage thermostat settings remotely | Medium |
| 100-011 | Add a spinner or similar temperature control | Medium |
| 100-005 | Create an intuitive user interface | Medium |
| 100-007 | Add thermostat locking and parental restrictions | Medium |
| 100-012 | Provide installation assistance | Low |
| 100-014* | Adjust settings when arrival times change | Low |
| 100-008 | Notify users about conflicting settings | Low |
| 100-010 | Add calendar-based scheduling | Low |
The original backlog did not assign a distinct ID to the late-arrival feature. ID 100-014 is a suggested identifier for tracking purposes and should be reconciled with the official project records.
Part 2: Project Schedule
Purpose of the Project Schedule
A project schedule identifies the activities required to complete a project, including their estimated durations, start dates, end dates, priorities, and current status. It helps the project manager coordinate development work, allocate resources, monitor progress, and identify potential delays.
For the CapraTek smart thermostat application, the schedule includes security development, dashboard design, customizable views, energy notifications, technical documentation, testing, remote management, calendar functionality, and final product deployment.
The schedule should be treated as a baseline for monitoring project performance. Changes to task durations, dependencies, or release dates should be documented and reviewed to understand their impact on the overall project.
February–March 2022: Security and Core Dashboard Development
The initial development phase focuses on securing the iOS application and creating the core thermostat dashboard.
| Task ID | Task description | Priority | Start date | End date | Duration (hours) | Status |
|---|---|---|---|---|---|---|
| 100-013 | Configure password-protected iOS login | High | 02/14/2022 | 03/11/2022 | 160 | Started |
| 100-001 | Create the dashboard for viewing thermostat settings | High | 02/14/2022 | 02/25/2022 | 80 | Complete |
| 100-002 | Develop customizable setting views and trend displays | High | 02/28/2022 | 03/18/2022 | 160 | In progress |
| 100-009 | Create notifications for energy-efficient settings | High | 03/01/2022 | 03/16/2022 | 96 | Not started |
| 100-004 | Provide final UI materials to the technical writer | High | 03/17/2022 | 03/18/2022 | 16 | Not started |
| N/A | Conduct QA testing and deployment | High | 03/21/2022 | 03/25/2022 | 40 | Not started |
This phase establishes the application’s essential functionality. The security task protects access to the application, while the dashboard provides users with a clear view of their thermostat settings. Customizable displays and energy notifications extend the core experience.
The technical writer must receive sufficiently stable interface designs to prepare accurate documentation. The team should also verify that the documentation milestone provides enough time for review before the relevant release.
March–April 2022: Usability and Household Controls
The next phase emphasizes ease of use and additional household control features.
| Task ID | Task description | Priority | Start date | End date | Duration (hours) | Status |
|---|---|---|---|---|---|---|
| 100-011 | Configure a spinner or similar temperature control | Medium | 03/28/2022 | 04/22/2022 | 160 | Not started |
| 100-005 | Design an intuitive interface with easy-to-use features | Medium | 04/04/2022 | 04/22/2022 | 80 | Not started |
| 100-007 | Develop thermostat locking capabilities | Medium | 04/11/2022 | 04/29/2022 | 120 | Not started |
| 100-012 | Add installation assistance and application instructions | Low | 04/20/2022 | 04/28/2022 | 56 | Not started |
| 100-004 | Provide updated UI materials to the technical writer | High | 05/02/2022 | 05/03/2022 | 16 | Not started |
| N/A | Conduct QA testing and deployment | High | 05/04/2022 | 05/10/2022 | 40 | Not started |
The main objective of this phase is to make thermostat control more convenient and accessible. Temperature adjustment controls should be easy to operate, while the interface should reduce confusion and help users complete common tasks efficiently.
Thermostat locking capabilities can also help households prevent unwanted changes. Installation guidance provides additional support for customers configuring the device for the first time.
Because the listed tasks overlap, the project manager should confirm that the same development resources are not assigned to conflicting activities and that QA receives completed features in time for testing.
May–June 2022: Scheduling and Conflict Management
The following phase introduces calendar-based scheduling and notifications for conflicting thermostat settings.
| Task ID | Task description | Priority | Start date | End date | Duration (hours) | Status |
|---|---|---|---|---|---|---|
| 100-006 | Develop an iOS schedule with editable thermostat settings | Low | 05/11/2022 | 05/20/2022 | 64 | Not started |
| 100-008 | Create alerts for conflicting thermostat settings | Low | 05/16/2022 | 06/07/2022 | 136 | Not started |
| 100-010 | Develop calendar features for future thermostat settings | Low | 05/25/2022 | 06/13/2022 | 112 | Not started |
These tasks help users manage thermostat settings around changing schedules, planned vacations, school holidays, and other events. Conflict notifications should make it easier for household members to identify incompatible settings and resolve them before they create inconvenience.
The project team should verify that calendar selections, recurring schedules, and temporary adjustments work together correctly. Testing should also confirm that users can review changes and restore their normal schedules when a temporary period ends.
June–August 2022: Remote Management and Product Launch
The final phase focuses on remote thermostat control, final documentation, quality assurance, deployment, and product launch.
| Task ID | Task description | Priority | Start date | End date | Duration (hours) | Status |
|---|---|---|---|---|---|---|
| 100-003 | Create the interface for remotely adjusting settings | Medium | 06/14/2022 | 07/01/2022 | 112 | Not started |
| 100-004 | Provide final UI materials to the technical writer | High | 07/04/2022 | 07/05/2022 | 16 | Not started |
| N/A | Conduct final QA testing and deployment | High | 07/06/2022 | 07/12/2022 | 40 | Not started |
| N/A | Prepare and execute product launch | N/A | 07/13/2022 | 08/01/2022 | 112 | Not started |
Remote management allows users to review and adjust thermostat settings when they are away from home. Because remote control involves access to a connected device, the team should validate authentication, permissions, communication reliability, and the handling of failed or delayed commands.
The final documentation milestone should provide the technical writer with stable interface designs and confirmed functionality. Before deployment, QA should verify the application’s core features, security controls, compatibility, and defect resolution. Launch activities should proceed only when the required acceptance criteria have been met.
Project Schedule Management and Monitoring
Tracking Task Progress
The project manager should monitor each task against its planned start date, end date, duration, and completion status. Task owners should report progress regularly, identify blockers, and communicate changes that may affect dependent work.
The original schedule uses statuses such as Started, In Progress, Complete, and Not Started. These status labels provide a basic overview, but they should be supported by objective completion criteria. For example, a dashboard task should not be marked complete until its required functions have been implemented and the relevant acceptance tests have passed.
Managing Dependencies and Schedule Risks
Some tasks depend on earlier work. Finalizing the user interface, for example, depends on sufficiently stable design decisions, while documentation and QA depend on access to the relevant builds and product specifications.
The project manager should identify dependencies and determine which activities are most likely to affect the launch date. Potential risks include delayed security testing, unresolved software defects, changes to interface designs, insufficient testing resources, and late delivery of documentation.
A regular schedule review can help the team identify delays early and decide whether tasks can be resequenced, additional resources are needed, or the release plan requires formal revision.
Quality Assurance and Deployment
QA testing is an important checkpoint between development and deployment. Testing should confirm that each feature meets its acceptance criteria and that changes do not introduce regressions in existing functionality.
For the smart thermostat application, testing should cover secure login, dashboard accuracy, temperature adjustments, energy notifications, scheduling, remote control, and conflict alerts. The team should also evaluate usability and confirm that the application behaves appropriately when network connectivity is unavailable or commands cannot be completed.
Deployment should follow an approved release process, with unresolved critical defects addressed before launch. User documentation, support arrangements, and stakeholder notifications should also be ready for the planned release.
Recommendations for Improving the Project Plan
The backlog and schedule provide a useful foundation, but several areas should be clarified before the plan is used to manage an active development project.
First, each user story should have a unique backlog ID. The original schedule repeats ID 100-004 for technical documentation, while the late-arrival feature does not have a clearly assigned identifier in the supplied backlog. Unique identifiers will improve traceability between requirements, tasks, testing, and reporting.
Second, the project team should define acceptance criteria for every feature. For example, the security story should specify the required authentication and security tests, while the energy-saving notification story should define when a notification appears and how its behavior will be verified.
Third, the team should confirm the relationship between estimated hours, task dates, and resource availability. Several tasks overlap, so the project manager should verify that the assigned team can complete them within the planned periods.
Finally, the project manager should validate the documentation and release timeline. The original backlog requires final interfaces to be available to the technical writer at least three weeks before launch. The schedule includes documentation handoffs in March, May, and July, but it does not explicitly establish the three-week lead time before the August 1, 2022 launch. The documentation milestone should therefore be reconciled with the requirement.
Frequently Asked Questions
What is the purpose of PM FPX 4080 Assessment 3?
PM FPX 4080 Assessment 3 focuses on developing a product backlog and project schedule for a software development project. The smart thermostat scenario demonstrates how user requirements can be prioritized and translated into scheduled development, testing, documentation, and deployment activities.
What is a product backlog in agile project management?
A product backlog is a prioritized list of features, improvements, and requirements for a product. It helps the development team understand what needs to be built and which items offer the greatest value or address the most important risks.
Why are security features a high priority for a smart thermostat?
A smart thermostat connects to a home network and may allow users to control household settings remotely. Appropriate authentication, access controls, secure communications, and vulnerability testing help reduce the risk of unauthorized access and protect connected devices.
How are user stories used in the project schedule?
User stories describe the functionality required from the user’s perspective. The project team translates them into development tasks, estimates the effort required, assigns priorities, and schedules implementation and testing activities.
What is the difference between a product backlog and a project schedule?
A product backlog organizes product requirements and their priorities. A project schedule organizes the work needed to deliver those requirements by assigning dates, durations, dependencies, and progress statuses.
Why is QA testing important before a smart thermostat app launch?
QA testing verifies that the application works as expected and helps identify defects before customers use the product. Testing can cover security, usability, temperature controls, scheduling, remote access, and the accuracy of displayed thermostat settings.
How can a project manager reduce delays in the development schedule?
The project manager can reduce delays by defining clear requirements, assigning task owners, monitoring dependencies, reviewing progress regularly, identifying resource conflicts, and addressing risks early. Schedule changes should be documented and evaluated for their impact on the release date.
Why must the technical writer receive the final user interface early?
The technical writer needs sufficiently stable interface designs to prepare accurate instructions and user guides. Early delivery provides time to draft, review, and update documentation before the product launches.
References
Capella University. (n.d.-a). CapraTek headquarters. Capella Media. https://media.capella.edu/CourseMedia/pm-fpx4080element236974/wrapper.asp
Capella University. (n.d.-b). Mahomet plant. Capella Media. https://media.capella.edu/CourseMedia/pm-fpx4080element236974/wrapper.asp
PM FPX 4080 Assessment 3 Project Schedule and Product Backlog
Capella University. (n.d.-c). Reed Massey’s office. Capella Media. https://media.capella.edu/CourseMedia/pm-fpx4080element236974/wrapper.asp