Comparing Methods
A little guide to comparing methods.
Here are some handy questions based on the AMMERSE values that you can use to understand the method better. It will help you decide whether it is best for you and your context.
I used a custom AMMERSE GPT prompt to generate the initial set of questions.
https://chatgpt.com/g/g-AmKpGlf25-ammerse
You can play with it yourself. (It’s not great, but a good starting point.)
10 Deep Dive Questions for Evaluating Methods
Agile (A)
Does the method allow for continuous adaptation and change?
Does the method allow its structure to change over time, or is it rigid?
Can teams dynamically modify how they work within the method without breaking it?
Does the method assume a fixed sequence of activities, or does it encourage emergent behaviours?
How does the method handle unexpected changes? Does it resist or embrace them?
Are there feedback loops in the method that lead to structural adjustments or only minor improvements?
Does the method enforce a predefined workflow or evolve based on team needs?
Can different teams implement the method uniquely, or must they follow one approach?
Does the method emphasize iteration as an adaptive practice or a delivery mechanism?
Are there built-in mechanisms to inspect and adapt the method itself?
Is the method primarily execution-focused (rigid) or learning-focused (adaptive)?
Minimal (Mi)
Does the method minimize structure, roles, and processes?
How many distinct roles are mandated by the method?
Does the method require specific artefacts (documents, boards, reports)?
How many layers of governance does the method introduce?
Is there a core set of rules or an extensive framework to follow?
Can the method be implemented with minimal documentation and structure?
Does the method introduce hierarchy, or is it flat?
How much overhead (meetings, approvals, reviews) does the method introduce?
Is the method primarily designed to be lightweight, or does it expand over time?
Are its rules strict and necessary, or are they often seen as overhead?
Can the method be learned and applied quickly, or does it require extensive training?
Maintainable (M)
Does the method enforce long-term system sustainability?
Does the method explicitly prevent system degradation over time?
Does the method require ongoing effort to keep it functioning, or does it sustain itself naturally?
Are there mechanisms to reduce unnecessary complexity as the system evolves?
Does the method require a governance model to ensure sustainability?
Can the system be handed over to new people without significantly losing continuity?
How does the method handle accumulating inefficiencies? Does it have built-in cleanup mechanisms?
Does the method force teams to consider long-term viability or only short-term results?
Are there explicit constraints that prevent technical or organizational debt?
Does the method scale without breaking its core structure?
How does the method handle the maintenance of knowledge, documentation, and best practices?
Environmental (E)
Does the method enforce strict control over the working environment?
Does the method impose predefined roles (Scrum Master, Product Owner, etc.)?
Are there mandated ceremonies or meetings that must take place at specific intervals?
Does the method enforce a specific reporting structure or hierarchy?
Are there formal rules on how work must flow through the system?
Can teams freely self-organize, or must they conform to predefined structures?
How rigid is the method’s approach to decision-making? Is it centralized or decentralized?
Does the method dictate a specific way of interacting with stakeholders?
Are leadership and management tightly embedded in the method, or is it self-managing?
Does the method require dedicated tools, technologies, or physical environments?
Is the method resistant to external changes, or does it allow for environmental shifts?
Reachable (R)
Does the method ensure goals and deliverables are realistically planned and achievable?
Does the method enforce predictable delivery cycles?
Are work units timeboxed or structured in a way that guarantees incremental progress?
Does the method prevent overcommitment, or does it allow scope creep?
How does the method ensure that commitments align with actual capacity?
Are estimation techniques required, or is work planned informally?
Does the method provide a way to measure actual vs. expected progress?
Is prioritization a core function, or does the method assume teams will handle it?
Does the method include constraints to prevent unrealistic goal-setting?
Are external dependencies accounted for in planning, or is it purely internal-facing?
How does the method handle failure to reach the goal? Does it adjust or enforce accountability?
Solvable (S)
Does the method actively enable people to solve problems creatively within its structure?
Does the method encourage root cause analysis of problems?
Are there built-in mechanisms to explore solutions, or does it focus only on execution?
How does the method handle ambiguity? Does it provide structured problem-solving tools?
Does the method encourage cross-functional collaboration to address issues?
Are problems surfacing quickly, or is issue resolution an afterthought?
Does the method foster an experimental mindset, or does it discourage deviation?
How does the method deal with unforeseen obstacles? Does it absorb them or resist them?
Are creative solutions rewarded within the method, or does it push toward predefined solutions?
Does the method assume that the team should solve problems, or does it rely on external intervention?
Are decisions made based on heuristics and learning or predefined rules?
Extensible (Ex)
Does the method allow for modifications, adaptations, or configurations without breaking its core structure?
Can the method be customized while remaining true to its original intent?
Are teams encouraged to modify elements of the method to fit their needs?
Does the method allow integration with other approaches, or does it require full adoption?
How easily can new concepts be introduced without disrupting the core method?
Does the method assume a fixed structure or have optional components?
Are modifications expected and encouraged, or considered violations of the method?
Can the method scale in different ways without introducing conflicts?
Are practitioners resistant to change within the method, or is flexibility embedded?
Does the method require certification to modify, or can anyone adapt it?
How does the method react to innovation? Does it integrate or reject them?
What are your weighted comparisons?
The following is from the AMMERSE Method.
https://www.lucidocean.com/services/p/the-ammerse-method
