the ‘bee log

Interesting that the p&p team working on the new SCSF drop is putting up there iteration reviews for the public to see. I see this as another and valuable form of “practice guidance” they’re providing beyond the executable and code work products. So much about agile is about continually improving increment-over-increment. An implicit and oft-overlooked part of this is you should make this process transparent to the outside: to your customers, to the people that pay your bills, to the people that eat your dog food, whatever the scenario.

As you can see here and here they’re admitting their defeats along with enumerating their successes. They’re also not counting work partially-done as done-done.

There’s a lot one can take from this. Of course it’s a case study straight from a top agile shop, but we can certainly take a note and publish similar reports, if not to the outside world, for our customers and stakeholders to see.

Perhaps, too, p&p could take a page from the Scrum playbook and provide a demo in the form of a screencast at the end of each iteration. A small step like that could make life easier for the pragmatists like myself who tend to drop in on a later, more mature (CTP) release.