Method Frameworks are like isolated islands.
This brief and light video explains why we can't continue with how we describe our most popular methods and frameworks such as DA, LeSS, Nexus, SAFe as if they were isolated islands when they in fact share so much but hide it behind different barriers: vocabulary, viewpoints, presentations (guides, web sites, books,...), strucures...you name it. We need to REFOUND the way we describe and APPLY our methods. Using Essence, which is a common ground for all methods, is an answer.
Why don't you try to get "under the skin of" Essence and its use cases. Browsing "stuff" won't help. A serious effort to understand it is needed. And, frankly, to my knowledge everyone who has done that won't go back to the old (current) way of dealing with methods. For instance: Jeff Sutherland with Scrum and Scrum at Scale and Scott W. Ambler with Disciplined Agile, or Sam Zawadi with Agnostic Agile, or prof. Pekka Abrahamsson and many others with education at university level.
There are many ways to get your "head around” Essence and its use cases. A good start is ‘The Essentials of Modern Software Engineering’ book. Or read the ACM Queue paper “Tear Down the Method Prisons! Set Free the Practices!”
You are most welcome to join us!
Product Advisor | Agile Coach | Investor |
4 年Great innovation Ivar! Good overview, visualisations and explanation on picking the right tool (practice) for the right problem you need to fix as a team or organization.
Independent Professional-, Agile & Senior Management Coach | Trusted Advisor | Founder & Co-Author Agnostic Agile (NPO) | Co-Founder & Co-Author Agile 2 | Change Catalyst | SW Developer | 15K+
5 年Hi Ivar, great video! It aligns in various ways with our #agnosticagile?messaging.? (for more on the #agnosticagile?principles and motivation, see www.agnosticagile.org )
A mí me va bien, si a Ud. le va bien
5 年Thank you for sharing. A must read indeed. I will try it. While I undestood the intentions to integrate and to find a "theory of everything" between those sets of valuable methods/frameworks perhaps a layer can be addedd before to create user stories and that layer could be a related set of Uses Cases. In my personal opinion and experience Use Cases are the most usefull tool to understand the system, where systeme is not software system, is the organization as a whole. It will help to integrate the whole mainly when you face actual organizational architectures which are silos oriented.