Is Agile Right for My Project? (draft)

About the Project

1. Impact

Small-scale transformation with minimal change management
Large-scale transformation with a lot of change management

2. Requirements

Not well-defined from the beginning
Well-defined from the beginning

3. Product

Software with primarily front-end technology
Software which has back-end and front-end technology
Hardware and software components (equally important)
Not software-based

4. Project Duration

Less than a month
More than a month and less than a year
Greater than a year and funding is certain
Greater than a year and funding is uncertain

5. Scope / Schedule

Scope and the order of scope is flexible but the schedule is fixed
Scope and the order of scope is not flexible but the schedule can be stretched

6. Feature Prioritization

Open to prioritization by value to ensure the most valuable features are implemented first
Have a "do everything we agreed upon" and "all or nothing" approach

7. Project task characteristics

Change day to day at a rapid pace
Take weeks and don't change day-by-day

8. Length of development cycles/sprints

Less than 6 weeks
Greater than 6 weeks

About the Project

9. Customer Availability

Available throughout the project
Minimally involved throughout the project

10. Product Owner^{Footnote 1}

Product owner is engaged, empowered, readily available, knowledgeable and can provide the development team with constant feedback
Product owner is not very engaged, not readily available, not knowledgeable or can't provide the development team with constant feedback

11. Team

Project has smaller, dedicated teams with a high degree of coordination and synchronization.
Project limits team coordination / synchronization to handoff points.

12. Teamwork and Collaboration

Project consists of dedicated team members, cross-functional expertise, is collaborative and shows initiative
Project is spread across multiple government departments and does not consist of dedicated team members but does include cross-functional expertise, is collaborative and shows initiative
Project does not have dedicated team members, cross-functional expertise, is not collaborative and does not show initiative

13. Co-location

Project team members are co-located (and would benefit from daily scrums to discuss status, roadblocks and input from the product owner)
Project team members are not co-located

14. Experience

Client, product owner and project teams are experienced and could keep up with a fast-paced environment
Client, product owner or project teams lack experience and could not keep up with a fast-paced environment

Governance and Oversight

15. Funding

Funding model supports an iterative approach (e.g., each team is given a funding envelope and they have the ability to cashflow as they need month to month, reforecast and move money around as long as its within their envelope)
Funding agreements are needed up-front and costs are scrutinized by line item

16. Project Oversight

Project is overseen by a program, Project Management Office or Project Controls Office
Project is not overseen by a program, Project Management Office or Project Controls Office

17. Required Documentation

Essential project-related documentation
Project and legal/regulatory documentation

18. Risk and Governance

Project is not high risk and does not have heavy governance
Project is high risk with heavy governance, involving meeting compliance, legal or regulatory requirements

19. Track Record of Success

Project failure rate for previous projects managed using a waterfall approach is unacceptably high
Projects have been delivering successfully with a waterfall approach

20. Willingness to Fail and Learn

My organization (supporting management, client, etc.) is amenable to failing fast and learning faster
My organization (supporting management, client, etc.) sees failure as a negative thing

Criteria	Selected answer	Agile score	Hybrid score	Non-agile score
Impact	1 2	10 0	10 5	5 10
Requirements	1 2	10 0	0 10	0 10
Product	1 2 3 4	10 5 5 0	5 10 10 0	0 5 5 10
Project Duration	1 2 3 4	0 10 10 0	0 10 10 0	10 5 5 10
Scope / Schedule	1 2	10 0	0 10	0 10
Feature Prioritization	1 2	10 0	10 0	0 10
Project task characteristics	1 2	10 0	5 0	0 10
Length of development cycles/sprints	1 2	10 0	10 0	0 10
Customer Availability	1 2	10 0	10 0	0 10
Product Owner	1 2	10 0	10 0	0 10
Team	1 2	10 0	10 0	0 10
Teamwork and Collaboration	1 2 3	10 5 0	5 5 5	0 0 10
Co-location	1 2	10 0	10 0	0 10
Experience	1 2	10 0	5 5	5 10
Funding	1 2	10 0	10 0	0 10
Project Oversight	1 2	10 0	10 0	5 10
Required Documentation	1 2	10 0	10 0	5 10
Risk and Governance	1 2	10 0	10 5	5 10
Track Record of Success	1 2	10 0	10 0	0 10
Willingness to Fail and Learn	1 2	10 0	0 10	0 10
Summary	Not applicable	0 out of 0 0%	0 out of 0 0%	0 out of 0 0%

Search and menus

Search

Introduction

Questionnaire

About the Project

About the Project

Governance and Oversight

Results

Questionnaire completed

Recommendation

Detailed results