10.1 Delivery Needs Assessment

Delivery Needs Assessment is the structured evaluation of a project's characteristics, constraints, and environment conducted to determine the requirements a delivery approach must satisfy, providing the factual foundation on which a specific agile framework or hybrid method is subsequently selected. Rather than choosing a delivery approach based on preference or familiarity, this assessment grounds the decision in a clear-eyed understanding of what the project actually demands.

Purpose of the Assessment

Establishing an Evidence-Based Foundation

A delivery needs assessment ensures that the choice of delivery approach rests on a genuine understanding of the project's specific circumstances rather than on assumptions carried over from previous, potentially dissimilar projects.

Surfacing Constraints Early

Conducting the assessment before committing to an approach helps surface constraints — such as regulatory requirements, stakeholder availability, or technical dependencies — early enough that they can shape the delivery approach itself, rather than being discovered only after a poorly suited approach has already caused friction.

Dimensions Evaluated

Uncertainty and Complexity

The assessment examines how well understood the project's requirements and solution are, since higher uncertainty generally favors approaches built around frequent inspection and adaptation, while lower uncertainty may tolerate more predictive planning.

Pace and Predictability of Work Arrival

Some projects involve a steady, predictable stream of similarly sized work, while others involve unpredictable, variably sized demands, and this pattern significantly influences whether a fixed-cadence or continuous-flow approach will serve the team better.

Team Structure and Availability

The assessment considers whether the work will be handled by a single stable team or requires coordination across multiple teams, as well as how much dedicated time team members can realistically commit, both of which shape what delivery structures are practically achievable.

Stakeholder Engagement Capacity

Because many agile approaches depend on regular, structured stakeholder involvement, the assessment evaluates how available and willing relevant stakeholders are to participate in reviews and feedback sessions at the cadence a given approach would require.

Regulatory and Organizational Constraints

Formal documentation, audit, or approval requirements imposed by regulation or organizational policy are identified during the assessment, since these constraints may necessitate specific process elements regardless of which underlying agile approach is otherwise preferred.

Conducting the Assessment

Gathering Input from Relevant Parties

A thorough assessment draws on input from the prospective delivery team, sponsors, and other key stakeholders, since each group holds different, relevant knowledge about constraints and expectations that shape what delivery approach will actually work in practice.

Reviewing Comparable Past Projects

Examining how similar past projects were delivered, and what worked or did not work about their chosen approach, can provide valuable evidence to inform the assessment, provided the comparison accounts for meaningful differences between the projects.

Documenting Findings

The assessment is typically documented in a form that can be directly compared against the characteristics of candidate delivery approaches, translating a project's specific circumstances into criteria that make the subsequent selection process more objective and transparent.

Using Assessment Results

Matching Findings to Candidate Approaches

Once completed, the assessment's findings are compared against the strengths and assumptions of available delivery approaches, identifying which framework or combination of practices best addresses the project's specific profile of needs and constraints.

Informing Hybrid or Tailored Approaches

Where no single established framework fits every identified need, the assessment provides the basis for deliberately combining or adapting elements from multiple approaches, ensuring that any customization is grounded in specific, articulated requirements rather than arbitrary preference.

Reassessing Needs Over Time

Responding to Changing Circumstances

Because project characteristics can shift as work progresses — through changes in team composition, evolving requirements, or new organizational constraints — periodically revisiting the delivery needs assessment helps confirm that the chosen approach remains appropriate.

Feeding Continuous Improvement

Insights gathered during delivery, particularly through retrospectives, can refine the understanding of what the project genuinely needs, allowing the team to adjust its approach based on accumulated experience rather than only its initial assessment.

Delivery Needs Assessment provides the disciplined, evidence-based groundwork that ensures a project's chosen delivery approach is selected to fit its actual characteristics and constraints, rather than adopted by default or habit.