Backlog is prioritized list of features, bug fixes, and other changes that need to be made to a product.
Think of it like a to-do list for your software project, but one that's constantly evolving and being refined by scrum team.
It's not just a random collection of ideas, but a carefully curated and prioritized list that guides the development team's work.
3 of 7
Why is a backlog so important?
Provides a single source of truth: It keeps everyone on the same page regarding what needs to be done.
Facilitates planning: It helps in estimating timelines and allocating resources.
Enables prioritization: It allows the team to focus on the most valuable items first.
Manages change: It accommodates new ideas and changing requirements throughout the development process.
4 of 7
Who is Product Owner, Scrum Team
The Product Owner is accountable for effective Product Backlog management, which includes:
Developing and explicitly communicating the Product Goal
Creating and clearly communicating Product Backlog Items
Ordering Product Backlog Items
Ensuring that the Product Backlog is transparent, visible and understood
The Scrum Team consists of one Scrum Master, one Product Owner, and Developers.
Within a Scrum Team, there are no sub-teams or hierarchies.
It is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
5 of 7
Product Backlog Item (PBI)
A Product Backlog Item (PBI) is a single element of work that exists in the product backlog. PBIs can include user stories, epics, specifications, bugs, or change requirements.
PBI contains multiple tasks which needs to be completed to consider PBI done
Basic types of PBI:
Functional
NonFunctional
Another types of PBI:
User Story
Epic
Features
Bug fixes
Tasks
6 of 7
Definition of Done
Business or Functional requirements (Acceptance Criteria)
Quality
Non-Functional Requirements
DONE = Releasable
7 of 7
Minimum Viable Product (MVP)
MVP is a version of your product with just enough features to attract early-adopter customers and validate your product idea early in the development cycle.
The goal of an MVP is to learn as much as possible about your customers with the least amount of effort.
It allows to gather feedback before investing too much time and resources in the final product.
MVP should have: Core functionality, Usability, Reliability, Sufficient value