A pioneer in applying Lean and Kanban to knowledge work, and an internationally recognized speaker and author, Jim Benson is CEO of the collaborative management consultancy Modus Cooperandi and founding partner of Modus Institute. He is a fellow in the Lean Systems Society and recipient of the Brickell Key Award for Excellence in Lean Thinking. He is the creator of Personal Kanban and co-author of Personal Kanban: Mapping Work | Navigating Life, winner of the Shingo Research and Publication Award. His other books include Why Plans Fail, Why Limit WIP and Beyond Agile.
Software is a world of possibilities. They are exciting. They are necessary. They are always just a little more work. Managers give team members too much to do. Team members invent more work to do. Companies make more commitments than they can keep. Work slows down, technical debt rises, and no one has any time to fix anything. Everyone experiences the frustration and shame of a bad release.
This is the foundation of the software industry. We dig our own graves in the deep pit of overwork. Award-winning author Jim Benson (Personal Kanban, Why Plans Fail, Why Limit WIP, Beyond Agile) will make you laugh and cry and he describes this all to familiar problem. He will give you hope as he describes how to recognize when you or your organization is overloaded and how to fix it
Everything in software is an experiment. We don't know if it will work. We don't know if people will buy it. We do know we will learn from it. We do know there will be a version 2.0. Product development implies we know what people want and we are developing it. This notion makes User Experience folks laugh.
We cement assumptions in "user stories" which are functional requirements in fancy wrappers. Using hypotheses instead of user stories and writing code not to test but to validate radically changes the way we approach software and drives quality through the roof. Every hypothesis includes its own testing and validation information. We can then track the impact of the software we create, understand how people use it, learn, and build better next time.
Jim Benson will discuss how this method of development has led several software companies to truly continuously improve.