## Appendix A The Questionnaire
\begin{tabular}{c c} \hline \hline
**Code** & **Item** & **Answer 6** \\ \hline ME1 & Budget vs. actual cost \\ ME2 & Burn-up chart \\ ME3 & Business value delivered \\ ME4 & Cumulative flow chart \\ ME5 & Customer retention \\ ME6 & Customer/user satisfaction \\ ME7 & Cycle time \\ ME8 & Defect resolution \\ ME9 & Defects into production \\ ME10 & Defects over time \\ ME11 & Earned value \\ ME12 & Estimation accuracy \\ ME13 & Individual hours per iteration/week \\ ME14 & Iteration burndown \\ ME15 & Planned vs. actual release dates \\ ME16 & Planned vs. actual stories per iteration \\ ME17 & Product utilization \\ ME18 & Release burndown \\ ME19 & Revenue sales impact \\ ME20 & Scope change in a release \\ \hline \hline \end{tabular}   
\({}^{5}\) The answers for the items (excluding IP14) were predefined with the following list of five items: (1) Strongly disagree, (2) Disagree, (3) Neither agree nor disagree, (4) Agree, and (5) Strongly agree. **Q8. ** How has your organization measured the success of Agile delivery? \begin{tabular}{c c} \hline \hline
**Code** & **Item** & **Answer 6** \\ \hline ME21 & Team morale \\ ME22 & Test pass/fail over time \\ ME23 & Velocity \\ ME24 & WIP, Work in Progress \\ ME25 & Other? Please specify: \\ \hline \hline \end{tabular}   
Footnote 6: The answers for the items (excluding ME25) were predefined with a list of two items:(1) No, and (2) Yes. **Q8. ** What are the most significant barriers to adopting Agile practices? \begin{tabular}{c c} \hline \hline
**Code** & **Item** & **Answer 7** \\ \hline BA1 & Fragmented tooling and project-related data/measurements \\ BA2 & General organization resistance to change \\ BA3 & Inadequate management support and sponsorship \\ BA4 & Inconsistent processes and practices across teams \\ BA5 & Insufficient training and education \\ BA6 & Lack of business/customer/product understanding \\ BA7 & Lack of skills/experience with agile methods \\ BA8 & Minimal collaboration and knowledge pairing \\ BA9 & Not enough leadership participation \\ BA10 & Organizational culture at odds with agile values \\ BA11 & Pervasiveness of traditional development methods \\ BA12 & Regulatory compliance or government issue \\ BA13 & Unwilling to admit mistakes and learn from delivery failure \\ BA14 & I don't know \\ BA15 & Other? Please specify: \\ \hline \hline \end{tabular}   
7: The answers for the items (excluding BA15) were predefined with the following list of five items: (1) Strongly disagree, (2) Disagree, (3) Neither agree nor disagree, (4) Agree, and (5) Strongly agree. **Q9. ** What are the benefits of adopting the release planning (TP10) technique? \begin{tabular}{c c} \hline \hline
**Code** & **Item** & **Answer 8** \\ \hline B1-TP10 & Eliminating Waste in the Planning Process \\ B2-TP10 & Increased Flexibility and Decreased \\ B3-TP10 & Development Lead Time \\ B4-TP10 & Increased Motivation of the Developers \\ B5-TP10 & Increased efficiency by highlighting the goals or \\ deadline for release \\ B6-TP10 & Making high-quality plans \\ B7-TP10 & Increased visualization potential of release \\ planning problems \\ B8-TP10 & Setting clear expectations about the objectives \\ and product features \\ B9-TP10 & Early identification of feature dependencies \\ B10-TP10 & Helping team members stay on track and \\ complete their tasks on time \\ B11-TP10 & Supporting the identification and mitigation of \\ potential issues and risks \\ B12-TP10 & Other? Please specify: \\ \hline \hline \end{tabular}   
8: The answers for the items (excluding B12) were predefined with the following list of five items: (1) Definitely Not, (2) Probably Not, (3) Possibly, (4) Probably Yes, (5) Definitely Yes. **Q10. ** What are the benefits of adopting the short iterations (TP12) technique?