See a real world example of the application of minimally marketable features. Further, see how feature flow can be managed using kanban and decoupled from the individual practices being used by the engineering teams (scrum in this case). The intended format is a combination of presentation and Q&A for gaining specific insights into practical application on the ground. Also attendees can learn about how to use measurement to assess progress empirically.

The Project Lockhart team was stacked with high performers and chartered with a clear mission, to simplify, unify, and orchestrate firewall security policy, for Cisco security products, from the cloud. We had organized around core agile principles, choosing scrum, and were executing one week sprints with two teams. The team had embraced CI/CD, delivering sprint increments every week to production in the cloud. We had supportive and engaged leadership. We were ready to build. The challenge we faced was as mundane as it was difficult to solve in practice. There was a lot of pressure on the team to execute and this coupled with inadequate backlog decomposition and refinement practices resulted in churn, inefficiency, and lack of alignment.

Learning Objectives:

• How to develop Minimally Marketable Features
• How to use Minimally Marketable Features to develop a Product Backlog/Roadmap
• How to measure progress at the program level using Minimally Marketable Features