Why should you use Backlog?

Do you have a list of backlogs or a product backlog for your Agile project? In traditional waterfall project, you will find many many lists like issue logs, parking lots, features list or even wishlist. A project manager is literally a full time administrator for maintaining these lists. Oh yes, an Agile project do not have a project manager!

The Pros of a Product Backlog

A product backlog is a single source which all members refer to. It can hold your features, issues, wishlist or any tasks that is required to achieve your agile outcome. You can also breakdown any items from product backlog. It is usually arranged such that higher priority items are on the top of the list. You do not need to keep multiple types of lists and thus reduce a lot of “admin” task.

Improvised your Product Backlog for Waterfall

A true Agile project seldom exists in many large organisations. Thus, we often run a waterfall agile type of project. You can still streamline all your listings into a single product backlog. All you need to do is tweak a column for different point of view. Of course, the first step is to merge all the various lists into a single one. Do manage your stakeholders views carefully for this “simple” change.

Agile have many good artifacts that aim for speed and low maintenance with maximum outcome. Product backlog is one that you can consider to implement in your existing waterfall or hybrid project. We should acknowledge that the results outweigh the “efforts” put in creating nice lists.

One thought on “Why should you use Backlog?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s