Entrepreneur. Customer-facing Product Management/ Marketing/ Consulting professional with over 25 years of software industry experience. Lean/ Agile Practitioner, Kanban Coach/ Trainer.
Co-founder, Sr. VP at Enterprise Agility tooling company Digité, Inc. – maker of SwiftKanban, SwiftEnterprise and SwiftEASe. Currently Head of Marketing/ Consulting. Kanban Management Professional (KMP), Kanban Coaching Professional (KCP), Accredited Kanban Trainer (AKT).
Still on a journey, interested in building innovative solutions to help individuals, teams, and enterprises deliver at a dramatically higher levels of productivity, efficiency and success rates.
Experience and interest areas include: – Contemporary Marketing methods and tools for effectively supporting buyers in their decision-making – Product Management, specifically Product-Market Fit and Lean Product Development – Lean/ Agile principles, practices and methods for successful and efficient project, products and services delivery in all aspects of business, not just IT and software – Managing and motivating people to become engaged and involved in organizational success and growth – Improving customer experience and service levels across all services I experience, both as provider and consumer.
Kanban’s 2-Phase Commit for Software Delivery Success
Software teams must commit to customers WHAT they will deliver by WHEN. They, in turn, push customers to FREEZE all requirements at the start. When software is delivered, the customer is either not ready for it OR requirements have changed. Kanban’s 2-Phase Commit provides an elegant solution!
Software project teams are under a lot of pressure to provide a clear estimate of their deliverables and delivery deadlines, even when customers and teams profess to be working with an “Agile approach”. Consequently, software teams also push their customers to define requirements fully and resist changes to requirements as that would cause a delay in projects. Once teams start working on requirements, often a fair amount of their work is aborted due to a change in requirement or a change in priority. At the other end, when teams are ready to deliver software, customers are often unprepared to take up a new release and the delivery cannot be accepted till then.
As a result, there’s a lot of dissatisfaction on all sides, with the customer – and the actual end-users – being unhappy with the software delivery, the teams being unhappy about wasted effort and overbearing pressure from customers – and all the extra effort taken (burning the midnight oil) going to waste.
Teams also spend a lot of time providing estimates of when they will complete delivery and at what cost. Those estimates and deadlines are often missed and the actual release is late.
Kanban’s 2-phase commit feature, combined with WIP Limits, provides an elegant solution to solving these issues. In this session, using examples from our own dev work as well as those from other companies, I will demonstrate just how the 2-phase commit process can resolve these problems and make for successful and timely delivery of the RIGHT PRODUCT at the RIGHT TIME; resulting in happy and successful customer-supplier relationships.
#kanban #ProjectManagement #changemanagement