Lab 4: User Stories, Product Backlog, and Sprint Backlog

Estimated duration: 1 hour 23 minutes

Scenario: Develop an Application (App) to Provide Real-Time Marketing Data

It is now time to begin the Sprint Planning for the project. The original project scenario defined functionality required by various stakeholders from the new App. Here is a quick review of the functionality requirements and a more detailed list of the needs of each role. This list will serve as a basis to develop user stories. The team also briefly reviewed the complexity level of each stakeholder's need. This will assist you in assigning story points to each user story.

Stakeholder	Needs	Initial Complexity Analysis
AHI Leadership	Identify and understand current and evolving segments Target and engage with emerging markets Access data feeds from all pertinent data sources Provide on-demand reports	Low to Moderate
Marketing	Track current market trends in the skincare industry on a real-time basis Monitor customer interest and preferences for AHI products based on views analysis Generate competitive analysis data through analysis of worldwide sales data Calculate AHI market share and trends by product categories Track sales and sales trends Provide on-demand reports	High
Finance	Allow for secure order invoicing and processing Provide real-time inventory and product availability reports Provide on-demand financial sales and forecasting metrics	Moderate
IT	Ensure App interfaces with new hardware and software Ensure App and new IT security upgrades are compatible Ensure IT storage meets App operational needs	Moderate
AHI Customers	Easy access to all AHI product offerings Secure invoicing Reliable order processing Confirmation of all transactions	Low to Moderate

Objectives

• Develop a User Story to support each stakeholder's need.
• Goal is five User Stories.
• Develop a product backlog for the five user stories created.
• Develop a Sprint Backlog to support your top two prioritized user stories. This sprint backlog supports sprint 1.
• All user stories will be shared for reference in the solution.

Exercise 2: Develop Product Backlog

1. Create a Product Backlog.
2. Number each user story.
3. Prioritize each user story. Note: Your prioritization may differ from the solution.
4. Complete all columns.

Note 1: Give your team a name.

Note 2: Estimate story points. Use the initial complexity analysis provided in this lab introduction as a guide. Your story points may differ from the solution.

Note 3: Assume that this project will be broken out into two 30-day sprints.

Note: At any point during the lab, you can refer to the example if you have any doubts.

Product Backlog Template

Product Backlog Example

Story Points Template

Story Points Example

Caibri iBody) 12 B y) 5409 IiE 2x0 Wheria Crapary = frat ans inei + Product Radberfor haject int narowiz Neneitonis Aurninit mannin- 1 Story Point More Complex User Story 5 User Story 2 User Story 1 User Story 4 User Story 3