Prompt Title: Agile - Users Stories

n this activity, you will write user stories and create acceptance criteria for each story based on customer needs. These user stories, collected under one epic, will form the basis of a Product Backlog. Note: Throughout this course, you will complete tasks normally done by others (like the Development Team or Product Owner). Even if you don’t perform them yourself, it is important that you understand these processes. Be sure to complete this activity before moving on. The next course item will provide you with a completed exemplar to compare to your own work. You will not be able to access the exemplar until you have completed this activity. Scenario Review the scenario below. Then complete the step-by-step-instructions. Imagine you are overseeing the development and launch of Virtual Verde, Office Green's new product line. Virtual Verde’s mission is to make working from home more enjoyable by offering desk plants for home office use. New customers recently received the first batch of plants. As a next step, your team had planned to introduce new product offerings to the Virtual Verde catalog—starting with Bonsai trees. However, a customer survey discovered that 70% of the new customers had difficulty caring for their plants. Many of the plants wilted and died within a month. This information inspired the team to develop new offerings and companion products to help new owners care for their plants. From the survey, Office Green learned that they can create value for their customers by making it easy to: Find out which plants are easiest to care for Access care instructions easily Have the right tools to care for their plants Remember when to water their plants Get expert help and advice quickly Have a hassle-free way to return their orders You will work with your team to create user stories that will help them build solutions to address these customer needs, and add them to the Product Backlog. Your team has already added Bonsai tree user stories to the Backlog, but the new plant care stories have now become the top priority. Note: In general, the Product Owner leads in prioritizing the Backlog and addressing new concerns. Anyone can work on user stories, but the Development Team typically gives feedback on them. Using the Bonsai tree stories in the Backlog template as a model, create six new user stories—one to address each of the six customer needs from the scenario. Your user stories should follow this construction: As a <user role>, I want <this action> so that I can <get this value>. For the <user role> part of each story, consider what sort of person might have that specific customer need. They might be a potential customer, a new plant owner, or something else. Keep in mind that these stories should help customers who may not have much experience caring for plants. For the <action> part of each user story, fill in the specific customer need. For the <value> part of each story, think about why your user might want to perform that particular action and how it will help them. When completed, each story should express a customer need the team can work to fulfill. For example, imagine that a customer wants to learn about different styles of Bonsai cutting and shaping. A related user story might read: “As a new Bonsai tree owner, I want to learn about different Bonsai styles so that I can pick the right one for my tree.”