Big Picture Explanation

For larger or more complex organisation we use the Big Picture. The Big Picture contains all of the parts of the H-Model, showing strategy and portfolio layers that are missing from the Small Picture. The big picture shows how many teams can deliver in parallel towards a large portfolio serving strategic goals. The Big Picture describes how concepts join up and flow throughout the enture software value stream. Every item on the big picture is clickable, linking to a detailed article.

HSD is indicative, not prescriptive – many big pictures can be formed with elements swapped out and skipped as required. The purpose of the big picture is not to insist that each element must be used, instead it is to describe how elements join up and what the whole system looks like.Although the Big Picture shows a “Programme” construct delivering a Product Family and co-ordinating contributing Product delivery “Projects” we use very broad definitions and do not intend to imply traditionalist project and programme management is always required. HSD requires iterative or continuous delivery, therefore iterative Project and Programme management have a place, but waterfall processes do not.Often we encounter organizations where different groups of people are working professionally but due to a lack of understanding of their “big picture” their work is simply not joined up with other areas of the organization or other teams. There’s no value in teams sprinting really well but delivering the wrong product. There’s no value in planning that doesn’t reflect reality and join up strategy to delivery.Understanding how work joins up to deliver Business Value is the first step towards actually generating Business Value making an organization happier, faster, leaner, more agile and producing products of greater value.There are a number of variants of the Big Picture, including a Small Picture used when Programmes aren’t necessary, as well as a variant for Commercial Off The Shelf (COTS) delivery.