Difference between revisions of "Project Approach Questionnaire (PAQ)"

From AgilePM wiki
Jump to: navigation, search
(Table)
 
(24 intermediate revisions by the same user not shown)
Line 1: Line 1:
  
This the AgilePM Project Approach Questionnaire (PAQ)  
+
'''The Project Approach Questionnaire (PAQ)'''
 +
* This checklist can be used to identify and confirm the level of achievement of all factors and to assess potential risk areas to be addressed.
 +
* Normally this PAQ questionnaire should be completed during Feasibility and re-assessed as part of Foundations.
 +
* The Project Approach Questionnaire provides a series of questions, the responses to which, from key project participants and stakeholders, will influence the overall project approach.
 +
* This is normally filled in by the Project Manager
  
* All members of the project understand and accept the DSDM approach (Philosophy, Principles and Practices)
 
* The Business Sponsor and the Business Visionary demonstrate clear and proactive ownership of the project.
 
* The business vision driving the project is clearly stated and understood by all members of the project team
 
* All project participants understand and accept that on-time delivery of an acceptable solution is the primary measure of success for the project
 
* The requirements can be prioritised and there is confidence that cost and time commitments can be met by flexing the scope of what's delivered.
 
* All members of the project team accept that requirements should only be defined at a high level in the early phases of the project and that detail will emerge as development progresses.
 
* All members of the project team accept that change in requirements is inevitable and that it is only by embracing change that the right solution will be delivered.
 
* The Business Sponsor and Business Visionary understand that active business involvement is essential and have the willingness and authority to commit appropriate business resources to the project.
 
* It is possible for the business and solution development members of the Solution Development Team to work collaboratively throughout the project.
 
* Empowerment of all members of the Solution Development Teaam is appropriate and sufficient to support the day-to-day decision-making needed to rapidly evolve the solution in short, focussed Timeboxes
 
* The DSDM roles and responsibilities are appropriately allocated and all role holders understand and accept the responsibilities associated with their role.
 
* The Solution Development team has the appropriate collective knowledge and skills (soft skills and technical skills) to collaboratively evolve an optimal business solution.
 
* Solution Development Team members are allocated to the project at an appropriate and consistent level sufficient to fully support the DSDM timeboxing practice
 
* Tools and collaborative working practices within the Solution Development Team are sufficient to allow effective Iterative Development of the solution.
 
* All necessary review and testing activity is fully integrated within the Iterative Development practice.
 
* Project progress is measured primarily through the incremental, demonstrable delivery of business value.
 
* There are no mandatory standards or other constraints in place that will prevent the application of the DSDM Philosophy and Practices on this project.
 
== Table ==
 
  
 
{| class="wikitable"
 
{| class="wikitable"
 
|+ Project Approach Questionnaire (PAQ)
 
|+ Project Approach Questionnaire (PAQ)
! style="padding-right: 10em;" | Project:   
+
! style="width: 50px; text-align: left;" | Project:   
! style="padding-right: 10em;" | Name:
+
! style="padding-right: 10em; text-align: left; width: 350px;" | Name:
 
|-
 
|-
! style="padding-right: 10em;" | Date:
+
! style="text-align: left;"|Date:
! style="padding-right: 10em;" | Position:
+
! style="padding-right: 10em; text-align: left;width: 350px;" | Position:
 
|-
 
|-
! style="width: 150px;" |Ref
+
! style="width: 50px; text-align: left;" | Ref
! Statement
+
! style="text-align: left;width: 350px;"| Statement
 
! Strongly Agree
 
! Strongly Agree
 
! Agree
 
! Agree
Line 36: Line 22:
 
! Disagree
 
! Disagree
 
! Strongly Disagree
 
! Strongly Disagree
! style="padding-left: 10em;" |
 
 
|-
 
|-
| 1
+
| style="text-align: center; |1
| All members of the project understand and accept the DSDM approach (Philosophy, Principles and Practices)
+
| ! style="width: 350px;" | All members of the project understand and accept the DSDM approach (Philosophy, Principles and Practices)
 
|  
 
|  
 
|  
 
|  
Line 47: Line 32:
 
|  
 
|  
 
|-
 
|-
| 2
+
| style="text-align: center; |2
 
| The Business Sponsor and the Business Visionary demonstrate clear and proactive ownership of the project.
 
| The Business Sponsor and the Business Visionary demonstrate clear and proactive ownership of the project.
 
|  
 
|  
Line 56: Line 41:
 
|  
 
|  
 
|-
 
|-
| 3
+
| style="text-align: center; |3
 
| The business vision driving the project is clearly stated and understood by all members of the project team
 
| The business vision driving the project is clearly stated and understood by all members of the project team
 
|  
 
|  
Line 65: Line 50:
 
|  
 
|  
 
|-
 
|-
| 4
+
| style="text-align: center; |4
 
| All project participants understand and accept that on-time delivery of an acceptable solution is the primary measure of success for the project
 
| All project participants understand and accept that on-time delivery of an acceptable solution is the primary measure of success for the project
 
|  
 
|  
Line 74: Line 59:
 
|  
 
|  
 
|-
 
|-
| 5
+
| style="text-align: center; |5
 
| The requirements can be prioritised and there is confidence that cost and time commitments can be met by flexing the scope of what's delivered.
 
| The requirements can be prioritised and there is confidence that cost and time commitments can be met by flexing the scope of what's delivered.
 
|  
 
|  
Line 83: Line 68:
 
|  
 
|  
 
|-
 
|-
| 6
+
| style="text-align: center; |6
 
| All members of the project team accept that requirements should only be defined at a high level in the early phases of the project and that detail will emerge as development progresses.
 
| All members of the project team accept that requirements should only be defined at a high level in the early phases of the project and that detail will emerge as development progresses.
 
|  
 
|  
Line 92: Line 77:
 
|  
 
|  
 
|-
 
|-
| 7
+
| style="text-align: center; | 7
 
| All members of the project team accept that change in requirements is inevitable and that it is only by embracing change that the right solution will be delivered.
 
| All members of the project team accept that change in requirements is inevitable and that it is only by embracing change that the right solution will be delivered.
 
|  
 
|  
Line 101: Line 86:
 
|  
 
|  
 
|-
 
|-
| 8
+
| style="text-align: center; | 8
 
| The Business Sponsor and Business Visionary understand that active business involvement is essential and have the willingness and authority to commit appropriate business resources to the project.
 
| The Business Sponsor and Business Visionary understand that active business involvement is essential and have the willingness and authority to commit appropriate business resources to the project.
 
|  
 
|  
Line 110: Line 95:
 
|  
 
|  
 
|-
 
|-
| 9
+
| style="text-align: center; |9
 
| It is possible for the business and solution development members of the Solution Development Team to work collaboratively throughout the project.
 
| It is possible for the business and solution development members of the Solution Development Team to work collaboratively throughout the project.
 
|  
 
|  
Line 119: Line 104:
 
|  
 
|  
 
|-
 
|-
| 10
+
| style="text-align: center; |10
 
| Empowerment of all members of the Solution Development Teaam is appropriate and sufficient to support the day-to-day decision-making needed to rapidly evolve the solution in short, focussed Timeboxes
 
| Empowerment of all members of the Solution Development Teaam is appropriate and sufficient to support the day-to-day decision-making needed to rapidly evolve the solution in short, focussed Timeboxes
 
|  
 
|  
Line 128: Line 113:
 
|  
 
|  
 
|-
 
|-
| 11
+
| style="text-align: center; |11
 
| The DSDM roles and responsibilities are appropriately allocated and all role holders understand and accept the responsibilities associated with their role.
 
| The DSDM roles and responsibilities are appropriately allocated and all role holders understand and accept the responsibilities associated with their role.
 
|  
 
|  
Line 137: Line 122:
 
|  
 
|  
 
|-
 
|-
| 12
+
| style="text-align: center; | 12
 
| The Solution Development team has the appropriate collective knowledge and skills (soft skills and technical skills) to collaboratively evolve an optimal business solution.
 
| The Solution Development team has the appropriate collective knowledge and skills (soft skills and technical skills) to collaboratively evolve an optimal business solution.
 
|  
 
|  
Line 146: Line 131:
 
|  
 
|  
 
|-
 
|-
| 13
+
| style="text-align: center; |13
 
| Solution Development Team members are allocated to the project at an appropriate and consistent level sufficient to fully support the DSDM timeboxing practice
 
| Solution Development Team members are allocated to the project at an appropriate and consistent level sufficient to fully support the DSDM timeboxing practice
 
|  
 
|  
Line 155: Line 140:
 
|  
 
|  
 
|-
 
|-
| 14
+
| style="text-align: center; |14
 
| Tools and collaborative working practices within the Solution Development Team are sufficient to allow effective Iterative Development of the solution.
 
| Tools and collaborative working practices within the Solution Development Team are sufficient to allow effective Iterative Development of the solution.
 
|  
 
|  
Line 164: Line 149:
 
|  
 
|  
 
|-
 
|-
| 15
+
| style="text-align: center; | 15
 
| All necessary review and testing activity is fully integrated within the Iterative Development practice.
 
| All necessary review and testing activity is fully integrated within the Iterative Development practice.
 
|  
 
|  
Line 173: Line 158:
 
|  
 
|  
 
|-
 
|-
| 16
+
| style="text-align: center; | 16
 
| Project progress is measured primarily through the incremental, demonstrable delivery of business value.
 
| Project progress is measured primarily through the incremental, demonstrable delivery of business value.
 
|  
 
|  
Line 182: Line 167:
 
|  
 
|  
 
|-
 
|-
| 17
+
| style="text-align: center; | 17
 
| There are no mandatory standards or other constraints in place that will prevent the application of the DSDM Philosophy and Practices on this project.
 
| There are no mandatory standards or other constraints in place that will prevent the application of the DSDM Philosophy and Practices on this project.
 
|  
 
|  

Latest revision as of 14:33, 21 December 2016

The Project Approach Questionnaire (PAQ)

  • This checklist can be used to identify and confirm the level of achievement of all factors and to assess potential risk areas to be addressed.
  • Normally this PAQ questionnaire should be completed during Feasibility and re-assessed as part of Foundations.
  • The Project Approach Questionnaire provides a series of questions, the responses to which, from key project participants and stakeholders, will influence the overall project approach.
  • This is normally filled in by the Project Manager


Project Approach Questionnaire (PAQ)
Project: Name:
Date: Position:
Ref Statement Strongly Agree Agree Neutral Disagree Strongly Disagree
1 All members of the project understand and accept the DSDM approach (Philosophy, Principles and Practices)
2 The Business Sponsor and the Business Visionary demonstrate clear and proactive ownership of the project.
3 The business vision driving the project is clearly stated and understood by all members of the project team
4 All project participants understand and accept that on-time delivery of an acceptable solution is the primary measure of success for the project
5 The requirements can be prioritised and there is confidence that cost and time commitments can be met by flexing the scope of what's delivered.
6 All members of the project team accept that requirements should only be defined at a high level in the early phases of the project and that detail will emerge as development progresses.
7 All members of the project team accept that change in requirements is inevitable and that it is only by embracing change that the right solution will be delivered.
8 The Business Sponsor and Business Visionary understand that active business involvement is essential and have the willingness and authority to commit appropriate business resources to the project.
9 It is possible for the business and solution development members of the Solution Development Team to work collaboratively throughout the project.
10 Empowerment of all members of the Solution Development Teaam is appropriate and sufficient to support the day-to-day decision-making needed to rapidly evolve the solution in short, focussed Timeboxes
11 The DSDM roles and responsibilities are appropriately allocated and all role holders understand and accept the responsibilities associated with their role.
12 The Solution Development team has the appropriate collective knowledge and skills (soft skills and technical skills) to collaboratively evolve an optimal business solution.
13 Solution Development Team members are allocated to the project at an appropriate and consistent level sufficient to fully support the DSDM timeboxing practice
14 Tools and collaborative working practices within the Solution Development Team are sufficient to allow effective Iterative Development of the solution.
15 All necessary review and testing activity is fully integrated within the Iterative Development practice.
16 Project progress is measured primarily through the incremental, demonstrable delivery of business value.
17 There are no mandatory standards or other constraints in place that will prevent the application of the DSDM Philosophy and Practices on this project.
General comments on suitability or risk associated with the DSDM approach :