Alex M.’s Post

I found this image a few years ago and always keep it in my pocket when trying to explain what an actual "MVP" is to leaders and peers. Most think of agile methodology like the first row, slowly developing and iterating each component of the "final product" until the customer or end user can utilize what they actually asked for. But we should all be focused on the second row - What's the fastest/simplest usable thing I can deliver that focuses on the needs of the customer? Focusing on the underlying need of “I need to get from A to B faster”, row 2 gets to the "Fastest Testable Product", and allows you to iterate.

I attended today's Scrum.org webcast, "Moving to an Agile Product Operating Model - Evidence Based Approach to Delivering Products in the Digital Age." It was a great session focused on how organizations can leverage an Agile Product Operating Model to thrive in the fast-paced digital world. Here are some key takeaways that resonated with me: - The Need for Agility: The digital age demands constant adaptation. Traditional, heavyweight product development models struggle to keep pace. - The Agile Product Operating Model: This framework emphasizes evidence-based decision making, transparency, and empiricism. It empowers teams to deliver value iteratively and respond quickly to changing market needs. - Benefits of the Model: Reduced uncertainty, minimized risk, and increased likelihood of delivering successful products that meet customer needs. - Focus on Evidence-Based Management (EBM): Data-driven decisions based on inspection and adaptation throughout the development process. - Key Value Areas (KVAs): Using EBM, organizations can identify and focus on KVA's, which represent the goals, current state, responsiveness, and innovation capability related to delivering value. - Organizational Design and Culture: The success of an Agile Product Operating Model depends on fostering an agile culture that supports self-organization and continuous improvement. Overall, the session provided valuable insights into how organizations can transform their product development processes to be more agile and deliver greater value in the digital age.

❌ What we think Agile means: As an engineer, I don’t need to estimate effort for implementing stories or breakdown into tasks and discuss design approach with product ops team and test team. It’s the project manager and Product Manager’s responsibility. ✅ What Agile actually means: Team deliverables are governed and implementation approach is agreed upon with a collective responsibility with engineering, architecture, testing and users.

The big question *Is Agile dead?* seems to come up much more frequently.... To me this becomes "Are agile methods reaching the end of their 'technology adoption'... ie 'methodology adoption' lifecycle?" What do you think - where on the curve are we today? And whats the next big curve of product delivery uplift? Feedback below 📢 📢 👉👉 Also see in comments for a related deepdive by Simon Powers (AWA)

Do we have/want a Manifesto for the PRODUCT MODEL…? Yesterday, as I was presenting the core of Agile (FOLLOW THE VALUE) & the Product Model, I got the question from the management team: “What’s the Product Model’s equivalent to the Agile Manifesto?” A fair question! My humble attempt at answering: ⁃ Product over Process ⁃ Outcomes over Output ⁃ Customers over Stakeholders ⁃ Product Discovery over Requirements Analysis Questions for Marty Cagan and Teresa Torres and all the other talented pragmatic agilists out there: Is there a Product Model Manifesto? Should there be? Want to help me make my humble attempt better?

How Well Does the Agile Manifesto Align with Principles that Lead to Success in Product Development?’ https://lnkd.in/dJTWXAsy My detailed critical analysis of the principles and values. #agilemanifesto

Looking for the quickest way to get the essentials of Scrum? Look no further! Scrum in 60 is a lightning-fast mini-course to understanding the core components of Scrum—the world's most popular agile framework. Check out Scrum in 60 https://lnkd.in/evBkcmsf

Insightful analyses of Scrum metrics are always a game-changer in product development. Taking this course was a splendid way to review and dig into details on the vital ones.

Agile is all 'bout finding the shortest route to completion, again and again.

If Agile is Good, Why Product are so Bad? After 15 years in Tech i got my own insider answer: Agile in theory works, but in practice is a different story: Because:  It does not focus on simplicity. it does embrace continuity but not progress (rate of progress). It does not improve communication.