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

Agile Pendentives

A “Pendentive” is an architectural converter that lets you fit a domed roof on a square base. The pendentive shown in the image on the right is the yellow part.  When working in a traditional project management setting we often need agile pendentives that let us fit agile practices onto a traditional base. Here are some examples: Traditional to Agile1.    WBS –>  Prioritized Backlog. When asked to show the Work Breakdown Structure (WBS) sponsors and PMO are likely looking for a breakdown of the project deliverables. Traditional project management approaches recommend creating a WBS early in a project lifecycle after gathering requirements and defining scope. Agile projects acknowledge this upfront design is likely to change and so deliberately go a […]

Read more