In The Humble Build-Up Chart – Communicating with Stakeholders , I discussed how a build-up chart can be used to show progress and projections – to achieve communication with stakeholders. Today, I’d like to address a couple of ways in which a build-up chart can be misleading. Done-ness? In Why Scrum requires completely “Done” software every Sprint , Christiaan Verwijs digs into what it means to produce a “Done”, useable, and potentially releasable product Increment (as defined by The Scrum Guide™). One way our build-up chart can mislead us is if what the build-up chart is tracking as “done” is not “Done”, usable, and potentially releasable. Looking at our sample build-up chart below, note the solid blue line that indicates progress-to-date. If the work that has been tracked here is not completely “done” and in a releasable state, then there is likely hidden work that will delay the actual release. Examples of work that might not be revealed by the build-up chart: Manual regression te