Discovery & Delivery ARE Part of Kanban

Discovery & Delivery ARE Part of Kanban

Discovery work would be, for example, research to figure out whether this is the right thing to build for the customer. Maybe we are doing some experiments or some prototyping. It is very wise to do experiments when we have insufficient evidence so we can harvest the proposed value because at the end of the day, our work items are bets at best. They are ill-informed opinions at worst if you do not experiment. You could just fill your funnel with stuff to develop and maybe there is no evidence you should actually develop it. So discovery is about discovering value, it is about learning.

There are multiple patterns available for managing these four time horizons. The thing is that we are managing WHAT type of work it is as opposed to WHO is doing the work.

In a modern team that is trying to practice agility, I would hope that people are trying to learn other skills. The reality is that the people who do discovery have a lot of work to do and there are usually fewer people who have the skill to do that discovery. What I often find is the people who do discovery are often coaching, mentoring, teaching, and willing volunteers who want to learn how to do that discovery.

How to connect with AgileDad:

- [website] https://www.agiledad.com/

- [instagram] https://www.instagram.com/agile_coach/

- [facebook] https://www.facebook.com/RealAgileDad/

- [Linkedin] https://www.linkedin.com/in/leehenson/