Читать книгу Agile Software A Complete Guide - 2020 Edition - Gerardus Blokdyk - Страница 10

CRITERION #4: ANALYZE:

INTENT: Analyze causes, assumptions and hypotheses.

In my belief, the answer to this question is clearly defined:

5 Strongly Agree

4 Agree

3 Neutral

2 Disagree

1 Strongly Disagree

1. How can UX-related work practices and processes be integrated with agile software processes?

<--- Score

2. Does your organization have a distinct quality program that support continuous process improvement?

<--- Score

3. What types of data do your Agile software indicators require?

<--- Score

4. How do agile software development processes, open-source programming or embedded systems affect the possibilities and alternatives for interaction design management?

<--- Score

5. Do you evaluate quality assurance in Agile processes?

<--- Score

6. How to transform requirements management process to better enable agile software development?

<--- Score

7. What is so special about Test Driven Development?

<--- Score

8. What is the Agile software Driver?

<--- Score

9. How was the detailed process map generated, verified, and validated?

<--- Score

10. Is there a strict change management process?

<--- Score

11. When should a process be art not science?

<--- Score

12. Who will facilitate the team and process?

<--- Score

13. Does test-driven development improve the program code?

<--- Score

14. How much bottom-up data management?

<--- Score

15. Is the amount of data the system should operate with reasonable?

<--- Score

16. Does programming involve processes that are similar to engineering?

<--- Score

17. Were there any improvement opportunities identified from the process analysis?

<--- Score

18. What tools were used to generate the list of possible causes?

<--- Score

19. How does customer feedback change the test or the development process?

<--- Score

20. Do you value individuals and interactions over processes and tools?

<--- Score

21. Were Pareto charts (or similar) used to portray the ‘heavy hitters’ (or key sources of variation)?

<--- Score

22. Does it insist on mixing data representation and control?

<--- Score

23. How does the Agile software development process work?

<--- Score

24. What are the measurement goals in an agile software development process?

<--- Score

25. Is the Agile software process severely broken such that a re-design is necessary?

<--- Score

26. What Agile software data will be collected?

<--- Score

27. Is there any way to speed up the process?

<--- Score

28. What are the most commonly used architecture documenting practices in agile development processes?

<--- Score

29. What are the personnel training and qualifications required?

<--- Score

30. Is agile software development process more successful?

<--- Score

31. What are the most important problems with the Agile software development process of the B2C department?

<--- Score

32. How are UX-related work practices and processes integrated with agile software processes in practice in a web-related environment?

<--- Score

33. Which agile software engineering processes and practices consider artifacts to which extent?

<--- Score

34. What is the cost of poor quality as supported by the team’s analysis?

<--- Score

35. What is the complexity of the output produced?

<--- Score

36. What does the data say about the performance of the stakeholder process?

<--- Score

37. What systems/processes must you excel at?

<--- Score

38. 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

81. How does the customer feedback change the test or the development process?

<--- Score

82. How do you do testing in an incremental software development process?

<--- Score

83. How does the contracting process work in Agile software projects?

<--- Score

84. Is there a culture of testing on the team, so that test-driven development practices will be consistently followed?

<--- Score

85. What is role of the process abstraction in your organization?

<--- Score

86. How is it possible to integrate agile software development methods to organizational processes and activities and to achieve agility?

<--- Score

87. What is the relationship between process maturity models and agile software development methods?

<--- Score

Add up total points for this section: _____ = Total points for this section

Divided by: ______ (number of statements answered) = ______ Average score for this section

Transfer your score to the Agile software Index at the beginning of the Self-Assessment.