Here is something to think about as you work work work... towards a potentially release-able product: 'Until your work interacts with the market, it's as if there is no work' -- Seth Godin
One might ask the following: "Why bother checking? We "know" that we are on track already!" "Can we just keep working and deliver the work when we are done?" "Can we just tell you what tasks we did and have completed?" "May we provide you a PowerPoint deck, screenshots, metric, list of lessons learned from our Spikes, some documentation and toll gate decks?" Good questions! Think about those questions for a few minutes. The thing is, a few errors accumulated everyday/ every sprint/iteration... unchecked... for a whole program increment (PI) spells disaster. Does it make sense to show the incremental…
In Sun Tzu's book, "Art of War", there is a section on "Waging War". I quote: "As for military operations, let us consider an army of 1000 attack chariots, 1000 heavy chariots and 100,000 armoured troop, all provisioned for a campaign of 1000 li". Tzu further added, "...Allow expenses for maintenance and manufacture of chariots and armour...". And, most of all, ensure victory. Tzu wrote about this in the section "Deployment". I quote, "Being prepared for all circumstances is what ensures certain victory..." Equating that to Lean-Agile teams, we should organize our teams around features (feature teams -- the "attacking…