WBS and Product Backlog: Siblings or Distant Cousins?

It’s easy to believe that work breakdown structures (WBS) have been around since the pyramids were built in Egypt, and that product backlogs are new inventions by youngsters in too much of a hurry to plan correctly. However, like most things, the truth is more complicated. In 1957, the Program Evaluation and Review Technique (PERT) approach was created by the United States Department of Defense (DoD) and described organizing tasks into product-oriented categories. However, they did not use the term “work breakdown structure” or WBS until 1962 when DoD, NASA and the aerospace industry published a document about PERT that described the WBS approach. Meanwhile, in 1960, Tom Gilb described his Evolutionary Value Delivery approach (or Evo for short) that […]

Read more

What’s in your Backlog?

Let’s explore what you do and do not put in a backlog. How do these sound? Features and non-functional requirements – Absolutely Bug fixes and change requests – Yes, probably Risk avoidance and risk reduction activities – Sure, maybe Opportunity exploitation activities and marketing ideas – Now you’re just getting weird! Team building and social events – Erm, no! Yet, if it’s all just stuff for the team to do, then why not put it in the backlog? Maybe because the customer has not asked for it and the product owner has to own and order it, but let’s look further. If we used a backlog metaphor for prioritizing backlog work items. It may look like this. I am not […]

Read more

BA’s on Agile Projects?

The role of the business Analyst (BA) on agile projects in some ways parallels the role of the project manager (PM). In that, some people believe these roles are not needed at all! The Scrum Guide, for instance, that outlines the Scrum approach describes only three roles: Scrum Master, Product Owner, and Development Team. Even when you look deeper into the Scrum Guide’s description for The Development Team role, it does not mention analysts or analysis work. However, most organizations agree, good BAs are great assets for any team, be it plan-driven, agile or hybrid. This article examines what BAs really do, looking at what stays the same on an agile project and what changes. The quick version is that […]

Read more