Methodology Map

⏱ 3 min  ·  📅 2026

The methodology map is a visual representation that places the main project management frameworks and methodologies along two axes: the degree of evolutionary management versus predictive management (vertical axis) and the degree of agility (people's tacit knowledge) versus process engineering (horizontal axis). It is a Scrum Manager conceptual artifact for contextualizing the relative position of each methodology.

How to read the map

• Vertical axis (predictive management ↔ evolutionary management): the higher a methodology sits, the more it relies on fixed upfront planning; the lower it sits, the more iterative and incremental it is.
• Horizontal axis (process engineering ↔ agility / people): the further to the right, the more focused on processes and engineering; the further to the left, the more focused on people's knowledge and collaboration.

Position of the Main Frameworks

• Sequential engineering: predictive management + process engineering. The quadrant of classic waterfall models.
• Concurrent engineering / Unified Process: evolutionary management + process engineering. Iterative development, but based on quality processes.
• Technical Scrum: evolutionary management + agility (people). The quadrant of pure agile frameworks.
• Kanban with continuous increment: within the agile quadrant, without timeboxing.

What It Is For

The map helps to:

• Understand why different frameworks are used in different contexts: no methodology is universally superior.
• Identify which axis is most misaligned with the project's needs in order to select the most suitable approach.
• Clearly communicate to stakeholders why an organization chooses a particular approach.

Common mistake

Using the map to rank methodologies instead of to contextualize them. The map does not say that agility is better than process engineering or that evolutionary management is superior to predictive management: it says that they are different approaches for different contexts. A critical infrastructure project may need sequential engineering; a startup validating market hypotheses may need Scrum. The map is for choosing with sound judgement, not for justifying a prior preference.

See also

Agility Evolutionary management Predictive management Concurrent engineering Sequential engineering Knowledge spiral

Want to advance in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.

Search calls

Agile Club