Product Backlog

Another benefit of the prioritized backlog is that development is extremely consistent. Instead of pushing an overwhelming number of requests through development, the backlog allows a drip feed of important work. While some organizations might experience lulls in development, Agile results in very steady work. This consistency yields a number of advantages to project management. Scrum team pace becomes very regular, which makes it easy to estimate how long a task or project might take.

While the Product Backlog is prioritized for future work, it typically doesn’t change what is currently in development. Once a request is pulled from the backlog and put into development, it is usually allowed to run to completion. Backlog changes affect what comes next, or what might be lined up for the following Sprint. In some extreme cases, a highly important feature might supersede what developers are currently working on. Normally, even high value tasks will fall in behind what is already in development.

By creating deliverables, conducting daily stand-up meetings, and prioritizing the Product Backlog, an Agile team can efficiently create software. Each of these components adds to the value of Agile software development. Collectively, they create a cohesive and productive organization.

Recommended Further Reading

The following materials may assist you in order to get the most out of this course: