A backlog is simply an ordered list of work to be done on a project. Each item on the list rolls up to the business case the project is trying to solve for. Ideally the backlog is prioritized and reprioritized so high-priority items are worked on and completed until the project (deliverable) is complete and accepted by the organization.
A backlog represents how the team adapts to plans throughout the project and how changes will be incorporated. In projects where an adaptive/agile approach is taken, there is an expectation that work will evolve and adapt to additions to the project backlog. In fact, changes to the project are encouraged. A project manager usually works with the product/project owner to manage expectations around adding scope or items to the backlog and how that might affect the budget, schedule, and availability of resources.
The number of backlog items that are in progress at any given time is telling. When there are too many items in progress, a project team can lose focus. It’s often the case that limiting in-progress work is more efficient in the long run. A Kanban board is effective at displaying backlog, in-progress, and completed tasks.
Backlog refinement is a key ceremony/event where the project backlog is considered and (re)prioritized to set the work for the upcoming sprint or iteration.
Want to learn more about Project Management? See my Project MGMT publication for these 30 key PM topics:
Projects, lifecycle, management, manager, methodologies, the triangle, stakeholders, deliverable, team, charter, scope, budget, schedule, planning, baselining, milestones, dependencies, resources, risk, procurement, communication, ceremonies, integration, backlog, whiteboard, closure, software tools, office(r), code of ethics, body of knowledge
Leave a Reply