Why Is ‘Make Work Visible’ one of the three Scrum artifacts?  Why does it matter and how can you apply it to non-technical and non-scrum initiatives?

* Making Work Visible doesn’t seem like an artifact, but in fact is a way of thinking about delivery and status that eliminates the overhead of collecting and producing status reports

* The easiest way to make work visible is to publish done things, but there are many other practices that make true ’status’ more available and transparent

* These techniques also apply to non-technical product