Was a detailed process map created to amplify critical steps of the ‘as is’ stakeholder process?
<--- Score
39. What are the main activities in a software process?
<--- Score
40. What quality tools were used to get through the analyze phase?
<--- Score
41. Is the gap/opportunity displayed and communicated in financial terms?
<--- Score
42. How to leverage big and fast data architecture patterns?
<--- Score
43. Have the problem and goal statements been updated to reflect the additional knowledge gained from the analyze phase?
<--- Score
44. Are gaps between current performance and the goal performance identified?
<--- Score
45. Is the data collection method adequately described?
<--- Score
46. What are alternatives to test-driven development?
<--- Score
47. Who holds ultimate decision rights for data management issues?
<--- Score
48. What are the processes for audit reporting and management?
<--- Score
49. What is your organizations system for selecting qualified vendors?
<--- Score
50. Are Agile software changes recognized early enough to be approved through the regular process?
<--- Score
51. What are the revised rough estimates of the financial savings/opportunity for Agile software improvements?
<--- Score
52. What were the crucial ‘moments of truth’ on the process map?
<--- Score
53. What tools were used to narrow the list of possible causes?
<--- Score
54. Is data and process analysis, root cause analysis and quantifying the gap/opportunity in place?
<--- Score
55. Is the performance gap determined?
<--- Score
56. Was a cause-and-effect diagram used to explore the different types of causes (or sources of variation)?
<--- Score
57. How will corresponding data be collected?
<--- Score
58. How will the data be checked for quality?
<--- Score
59. Why are developers adopting evolutionary, and more often, agile software processes?
<--- Score
60. What are the Agile software design outputs?
<--- Score
61. What were the financial benefits resulting from any ‘ground fruit or low-hanging fruit’ (quick fixes)?
<--- Score
62. What Agile software data should be managed?
<--- Score
63. Have any additional benefits been identified that will result from closing all or most of the gaps?
<--- Score
64. How is your agile software development process?
<--- Score
65. What did the team gain from developing a sub-process map?
<--- Score
66. What tools do you use to manage Agile processes and activities?
<--- Score
67. Do test environments have the capacity to detect data breaches?
<--- Score
68. How can the metrics be effectively incorporated in an agile software development process?
<--- Score
69. How does the organization define, manage, and improve its Agile software processes?
<--- Score
70. What conclusions were drawn from the team’s data collection and analysis? How did the team reach these conclusions?
<--- Score
71. Were any designed experiments used to generate additional insight into the data analysis?
<--- Score
72. How much top-down data management?
<--- Score
73. Has an output goal been set?
<--- Score
74. How do enterprise architects enable agile software delivery using DevOps without over-engineering or setting up too-rigid parameters in the process?
<--- Score
75. Do you see use cases generated during the development process?
<--- Score
76. Did any additional data need to be collected?
<--- Score
77. How is data used for program management and improvement?
<--- Score
78. Did any value-added analysis or ‘lean thinking’ take place to identify some of the gaps shown on the ‘as is’ process map?
<--- Score
79. What is next for test-drIven development?
<--- Score
80. What type of performance and process optimization measurement should be performed in agile software development?
<--- Score
