define the scope and the requirements of your project by developing product backlog items (PBIs) in Azure DevOps. Your product backlog must include at least three backlog features (epics) and 10 PBIs in a nested, hierarchical order. The backlog epics and PBIs must also be arranged based on the value they provide to the customer. Ensure that PBIs contain the definition of done criteria (e.g., each PBI details what the feature will and will not do and defines precise acceptance criteria). Each PBI should also contain an estimate of effort in story point units.
Once you have completed your product backlog in Azure DevOps, take a screenshot of it for your assignment submission, and complete the paper requirements below.
In your paper,
Summarize the backlog epics and their associated PBIs, and how they contribute toward the successful completion of the project.
Explain the approach and decisions that your group made while developing the epics and PBIs.
Outline the lessons learned as a result of this experience.
Include the screenshot showing the completion of your product backlog in Azure DevOps.
Full Answer Section
Creating Backlog Epics:
- Identify Key Features: Break down your project into 3-5 major features, each representing a significant chunk of functionality or value.
- Epic Description: Briefly describe each feature and how it contributes to the overall project goal.
- Value to Customer: Prioritize your features based on the value they provide to your target audience. Features that address their biggest needs or pain points should be prioritized.
Developing PBIs:
- Break Down Features: For each epic, create smaller, more granular product backlog items (PBIs) that represent specific functionalities within the feature. Aim for 3-5 PBIs per epic.
- User Stories: Use the user story format to describe each PBI. This format typically follows the structure: "As a [user], I want [feature] so that [benefit]."
- Definition of Done: Clearly define what "done" means for each PBI. This should include specific acceptance criteria, features included and excluded, and any quality standards.
- Story Points: Estimate the effort required to complete each PBI using story points. This helps with planning and resource allocation.
Example:
Project Goal: Develop a mobile app that helps users find and book dog walkers in their area.
Epics:
- Search & Discovery: Find dog walkers based on location, availability, and ratings. (High Value)
- Booking & Management: Book appointments, manage payments, and communicate with walkers. (Medium Value)
- User Profiles & Reviews: Create user profiles, leave reviews, and manage settings. (Low Value)
PBIs (under Search & Discovery Epic):
- As a dog owner, I want to search for dog walkers within a 5-mile radius of my location. (5 story points)
- As a dog owner, I want to filter dog walkers by their experience with specific dog breeds. (8 story points)
- As a dog owner, I want to see dog walkers' average rating and number of reviews. (3 story points)