Tuesday 4th October, 2011
1:00pm to 1:45pm
What this session is about:
One very important property in Kanban is called "make process policies explicit". This includes well defined interfaces to upstream as well as downstream partners. Kanban tries to define these interfaces on a very abstract level, because Kanban is a change managent approach that wants to integrate with several possible project management approaches without making assumptions about them.
From software development, we know that it is good to describe the behavior of an interface as a form of contract between client and service, using example scenarios and assertions, deliberate discovery, behavior driven development, TDD, Design by Contract, whatever. Can this be done with process policies in Kanban, too?
In this session, I'd like to discuss questions like these:
What the session is like and what you can take away:
In a short presentation, I will challenge the usual expectations on a team, as described in literature or on the Net. I also ask whether teams typically agree to think about their interfaces. My proposition is that thinking in terms of contracts can help to improve a team's services over an extended period of time.
Both business and team can earn value from this:
Helping product development organizations make more money and increase customer as well as employee satisfaction. Just effective collaboration.
Sign in to add slides, notes or videos to this session