I wanted to share some general accomplishments from our first quarter of using Kanban in terms of metrics.  Our cycle times have been slashed in half!  Our backlog is the lowest I've ever seen it at.  And we've been able to quickly identify blockages and fix those issues.

I don't want you to think there's not room for improvement.  Our quality needs some work.  Since we don't have a QA group, we need to find some better way to bake in quality.  From the Kanabandev mailing list , Stuart C. mentioned that we could create a situation to encourage developers to better test their code.  This would be accomplished by forcing devs to change any bugs encountered after they say the change item has been completed.  This new work is in addition to their current work, so hopefully this encourages developers to create quality code.

Share this post: email it! | bookmark it! | digg it! | reddit! | kick it! | live it!
Sponsor