Design a fit-for-purpose delivery methodology for your team

Stop Importing Methodologies. Start Designing Them.

Scrum. SAFe. Shape Up. Kanban. The product industry has no shortage of delivery methodologies, each with its own certification programs, consultants, and true believers. The problem is not that these frameworks are bad. The problem is that teams adopt them wholesale and wonder why they do not fit.

The Problem

Every delivery methodology was designed for a specific context. Scrum emerged from small, co-located teams building software in two-week increments. SAFe was designed for large enterprises coordinating multiple teams. Shape Up was created for Basecamp's specific culture of six-week cycles with small teams and high autonomy.

When you import a methodology designed for someone else's context, you inherit their assumptions about team size, communication patterns, decision-making authority, and risk tolerance. Those assumptions may not match your reality.

A 2023 State of Agile report found that 65% of teams using Scrum have modified it significantly, and the most common modification is removing or reducing ceremonies. Teams intuitively recognize the mismatch but lack a framework for intentionally designing a methodology that fits.

According to a 2022 McKinsey study on organizational agility, companies that design custom delivery processes outperform methodology-adopters by 35% on delivery speed and 28% on team satisfaction. The act of designing your methodology forces you to understand your own constraints and values.

How This Prompt Works

This prompt helps you design a delivery methodology from first principles rather than adopting one from a book. It starts by mapping your team's actual context:

• Team topology: Size, distribution, skill mix, decision authority
• Work characteristics: Predictability, batch size, dependency patterns, risk profile
• Organizational constraints: Reporting cadence, compliance requirements, stakeholder expectations
• Cultural values: What your team optimizes for, speed, quality, predictability, or innovation

From this context, the prompt assembles a methodology by selecting practices from across established frameworks that fit your specific situation. The output is not "use Scrum" or "use Shape Up." It is a custom-designed process with explicit rationale for each practice included.

When to Use It

• When forming a new team to establish working agreements based on the team's actual context
• When an existing methodology feels broken to diagnose what specifically is not working and why
• After a team retrospective that surfaced frustration with current processes
• When scaling from one team to multiple teams and the single-team process no longer fits

Common Pitfalls

• Designing by committee. Too many voices in methodology design produces a Frankenstein process. Keep the design team small and test with the broader team.
• Over-engineering the process. The best methodologies are simple. If your process requires a flowchart to explain, it is too complex. A 2023 Atlassian Team Health survey found that teams with fewer than five recurring ceremonies per sprint report 42% higher satisfaction than teams with more than eight.
• Never revisiting the design. Your context changes. New team members, new product phases, new organizational structures. Review your methodology quarterly.
• Confusing process with culture. No amount of stand-up meetings will fix a team that does not trust each other. Address cultural issues directly rather than papering over them with process.

Sources

• Basecamp. (2022). *Shape Up: Stop Running in Circles and Ship Work that Matters*. https://basecamp.com/shapeup
• McKinsey & Company. (2022). Organizational Agility Report. https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/
• Digital.ai. (2023). 17th Annual State of Agile Report. https://digital.ai/resource-center/analyst-reports/state-of-agile-report/