Score project agile suitability across nine delivery criteria
Drag nine sliders to map project and team characteristics. The radar redraws in real time, plotting team, culture, and project factors on a 1–10 scale where 1 is fully agile and 10 is fully plan-driven.
Drag the sliders to map project and team characteristics. The radar redraws in real time, plotting nine criteria across three dimensions — team, culture, and project — on a 1–10 scale where 1 is fully agile and 10 is fully plan-driven.
About this tool
The tool above scores a project against nine characteristics that practitioners use to decide between agile, hybrid, and plan-driven delivery. It is not a checklist that produces a correct answer — it is a structured way to have the conversation.
Each criterion sits on a 1–10 scale. The zone bands group the average into agile (1–3.5), hybrid (3.6–7), and plan-driven (7.1–10). The three dimension sectors — team, culture, and project — show where the pressures cluster, so you can see whether the constraint is organisational, cultural, or technical.
Detailed definitions for each of the nine criteria will follow below.
The nine dimensions
The filter scores a project across nine dimensions. Each one is a conversation, not a number — the slider is there to make the discussion concrete, not to settle it.
Access to Customer — How readily the team can reach the customer, or a proxy, for feedback and decisions.
Approach Buy-in — How firmly the stakeholders back the chosen way of working.
Trust in Team — How much autonomy the organization gives the team to decide and act.
Team Decision Making — How capable the team is of making sound calls without escalating every choice.
Incremental Delivery — Whether the solution can ship in small, usable releases rather than one big launch.
Criticality of Product — What failure costs, from a minor inconvenience to serious financial, legal, or reputational damage.
Change Likelihood — How much the requirements are expected to shift as the market, stakeholders, or scope evolve.
Team Size — How many people the initiative needs; small teams stay flexible, larger ones need more structure.
Experience Levels — How seasoned the team is with the business domain, the tools, and this way of delivering.