Читать книгу Software Performance Engineering A Complete Guide - 2020 Edition - Gerardus Blokdyk - Страница 9
ОглавлениеCRITERION #3: MEASURE:
INTENT: Gather the correct data. Measure the current performance and evolution of the situation.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
1. Do you have any cost Software Performance Engineering limitation requirements?
<--- Score
2. What are the costs?
<--- Score
3. Have you included everything in your Software Performance Engineering cost models?
<--- Score
4. What is the root cause(s) of the problem?
<--- Score
5. Why do the measurements/indicators matter?
<--- Score
6. At what cost?
<--- Score
7. What are the strategic priorities for this year?
<--- Score
8. What are the costs of reform?
<--- Score
9. Who pays the cost?
<--- Score
10. How can you reduce the costs of obtaining inputs?
<--- Score
11. Does the Software Performance Engineering task fit the client’s priorities?
<--- Score
12. How long to keep data and how to manage retention costs?
<--- Score
13. What evidence is there and what is measured?
<--- Score
14. How can you reduce costs?
<--- Score
15. What is the total fixed cost?
<--- Score
16. Which measures and indicators matter?
<--- Score
17. How do you aggregate measures across priorities?
<--- Score
18. Has a cost center been established?
<--- Score
19. What are your key Software Performance Engineering organizational performance measures, including key short and longer-term financial measures?
<--- Score
20. How do you measure variability?
<--- Score
21. Do you have an issue in getting priority?
<--- Score
22. How are measurements made?
<--- Score
23. Why do you expend time and effort to implement measurement, for whom?
<--- Score
24. What are your operating costs?
<--- Score
25. Are the measurements objective?
<--- Score
26. How much does it cost?
<--- Score
27. What are the Software Performance Engineering key cost drivers?
<--- Score
28. Are the Software Performance Engineering benefits worth its costs?
<--- Score
29. What can be used to verify compliance?
<--- Score
30. How sensitive must the Software Performance Engineering strategy be to cost?
<--- Score
31. What causes mismanagement?
<--- Score
32. How can you measure the performance?
<--- Score
33. What are hidden Software Performance Engineering quality costs?
<--- Score
34. How will you measure your Software Performance Engineering effectiveness?
<--- Score
35. Is the cost worth the Software Performance Engineering effort ?
<--- Score
36. Have you made assumptions about the shape of the future, particularly its impact on your customers and competitors?
<--- Score
37. Which costs should be taken into account?
<--- Score
38. Are you taking your company in the direction of better and revenue or cheaper and cost?
<--- Score
39. Are actual costs in line with budgeted costs?
<--- Score
40. What are the operational costs after Software Performance Engineering deployment?
<--- Score
41. What users will be impacted?
<--- Score
42. What are the costs and benefits?
<--- Score
43. How do you measure success?
<--- Score
44. Who should receive measurement reports?
<--- Score
45. How is the value delivered by Software Performance Engineering being measured?
<--- Score
46. How can you measure Software Performance Engineering in a systematic way?
<--- Score
47. What are the types and number of measures to use?
<--- Score
48. What causes investor action?
<--- Score
49. What is your decision requirements diagram?
<--- Score
50. What are allowable costs?
<--- Score
51. How will effects be measured?
<--- Score
52. How do you verify performance?
<--- Score
53. How do you verify and develop ideas and innovations?
<--- Score
54. How do you verify your resources?
<--- Score
55. How is performance measured?
<--- Score
56. What relevant entities could be measured?
<--- Score
57. Is there an opportunity to verify requirements?
<--- Score
58. What are the Software Performance Engineering investment costs?
<--- Score
59. Was a business case (cost/benefit) developed?
<--- Score
60. Are there competing Software Performance Engineering priorities?
<--- Score
61. Do you effectively measure and reward individual and team performance?
<--- Score
62. How can you manage cost down?
<--- Score
63. Are you aware of what could cause a problem?
<--- Score
64. What does losing customers cost your organization?
<--- Score
65. Do you aggressively reward and promote the people who have the biggest impact on creating excellent Software Performance Engineering services/products?
<--- Score
66. How do you verify the authenticity of the data and information used?
<--- Score
67. How will your organization measure success?
<--- Score
68. Is the solution cost-effective?
<--- Score
69. What does your operating model cost?
<--- Score
70. What is an unallowable cost?
<--- Score
71. What is your Software Performance Engineering quality cost segregation study?
<--- Score
72. What is the cause of any Software Performance Engineering gaps?
<--- Score
73. What do you measure and why?
<--- Score
74. Does a Software Performance Engineering quantification method exist?
<--- Score
75. Where is it measured?
<--- Score
76. How do your measurements capture actionable Software Performance Engineering information for use in exceeding your customers expectations and securing your customers engagement?
<--- Score
77. How to cause the change?
<--- Score
78. How do you prevent mis-estimating cost?
<--- Score
79. How will success or failure be measured?
<--- Score
80. Are the units of measure consistent?
<--- Score
81. When a disaster occurs, who gets priority?
<--- Score
82. How will measures be used to manage and adapt?
<--- Score
83. What tests verify requirements?
<--- Score
84. How do you measure efficient delivery of Software Performance Engineering services?
<--- Score
85. What causes extra work or rework?
<--- Score
86. What is the cost of rework?
<--- Score
87. What happens if cost savings do not materialize?
<--- Score
88. Are there measurements based on task performance?
<--- Score
89. Do the benefits outweigh the costs?
<--- Score
90. Does management have the right priorities among projects?
<--- Score
91. What does a Test Case verify?
<--- Score
92. Are missed Software Performance Engineering opportunities costing your organization money?
<--- Score
93. Did you tackle the cause or the symptom?
<--- Score
94. Are supply costs steady or fluctuating?
<--- Score
95. What would be a real cause for concern?
<--- Score
96. What details are required of the Software Performance Engineering cost structure?
<--- Score
97. When are costs are incurred?
<--- Score
98. What disadvantage does this cause for the user?
<--- Score
99. Where is the cost?
<--- Score
100. What do people want to verify?
<--- Score
101. What are the uncertainties surrounding estimates of impact?
<--- Score
102. What is the Software Performance Engineering business impact?
<--- Score
103. Are there any easy-to-implement alternatives to Software Performance Engineering? Sometimes other solutions are available that do not require the cost implications of a full-blown project?
<--- Score
104. Are Software Performance Engineering vulnerabilities categorized and prioritized?
<--- Score
105. What are the current costs of the Software Performance Engineering process?
<--- Score
106. What are your primary costs, revenues, assets?
<--- Score
107. Are indirect costs charged to the Software Performance Engineering program?
<--- Score
108. What would it cost to replace your technology?
<--- Score
109. Are you able to realize any cost savings?
<--- Score
110. How are costs allocated?
<--- Score
111. What is measured? Why?
<--- Score
112. How can a Software Performance Engineering test verify your ideas or assumptions?
<--- Score
113. How do you verify if Software Performance Engineering is built right?
<--- Score
114. What could cause you to change course?
<--- Score
115. How do you quantify and qualify impacts?
<--- Score
116. What measurements are being captured?
<--- Score
117. Have design-to-cost goals been established?
<--- Score
118. What measurements are possible, practicable and meaningful?
<--- Score
119. Among the Software Performance Engineering product and service cost to be estimated, which is considered hardest to estimate?
<--- Score
120. When should you bother with diagrams?
<--- Score
121. How will you measure success?
<--- Score
122. What could cause delays in the schedule?
<--- Score
123. How frequently do you track Software Performance Engineering measures?
