Having said that, it's taken out some overheads.
This week it became pretty obvious that we should do a release:
 |
| A pile of stuff to release now. |
There's a whole pile of stuff - and the more we leave it, the greater work will be required to get through acceptance testing.
So we decided to do a release and pulled those cards through acceptance testing.
None of the release work has changed (not sure if we're doing it right, mind you!).
We still needed to book in the production sys admins, we still wrote a test plan, we still did some manual testing and so on.
I'm still very much impressed with the Kanban approach. We still use many of the scrum and XP philosophies, but working in a Kanban framework seems to take away some overheads and replace them (ironically) with the "individuals and interactions over process and tools" thing from the manifesto.
It's been interesting to look at the board as we do this though - you'll notice that the left side of the board got pretty vacant back there at the beginning while we all focussed on getting set up for acceptance testing.
I'm not sure if that's the way it's supposed to be - but by the time we'd finished acceptance testing, the developers were beavering away on new stuff and by the time we were done, it looked "healthier" than I'd seen to date - new stuff coming through as we launched into production...
 |
| After the release |
I expect that the more regular flow is also down to the decision to break the bigger project work into constituent parts (a few posts ago).
I'd be really interested to hear from other people who are going through a Kanban testing journey, so we can learn from others!
