126. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
127. What is the scope of the Backend as a service work?
<--- Score
128. What are the compelling stakeholder reasons for embarking on Backend as a service?
<--- Score
129. Have all of the relationships been defined properly?
<--- Score
130. What Backend as a service requirements should be gathered?
<--- Score
131. How do you manage scope?
<--- 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 Backend as a service Index at the beginning of the Self-Assessment.
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. What are your primary costs, revenues, assets?
<--- Score
2. Are actual costs in line with budgeted costs?
<--- Score
3. What are the Backend as a service key cost drivers?
<--- Score
4. What methods are feasible and acceptable to estimate the impact of reforms?
<--- Score
5. How can you manage cost down?
<--- Score
6. How to cause the change?
<--- Score
7. What are your customers expectations and measures?
<--- Score
8. How do you measure success?
<--- Score
9. Have you made assumptions about the shape of the future, particularly its impact on your customers and competitors?
<--- Score
10. What are the costs of delaying Backend as a service action?
<--- Score
11. At what cost?
<--- Score
12. What is your Backend as a service quality cost segregation study?
<--- Score
13. What causes investor action?
<--- Score
14. Has a cost center been established?
<--- Score
15. What evidence is there and what is measured?
<--- Score
16. How will you measure success?
<--- Score
17. How is the value delivered by Backend as a service being measured?
<--- Score
18. What could cause delays in the schedule?
<--- Score
19. How is performance measured?
<--- Score
20. What measurements are being captured?
<--- Score
21. Do you aggressively reward and promote the people who have the biggest impact on creating excellent Backend as a service services/products?
<--- Score
22. Who pays the cost?
<--- Score
23. Are Backend as a service vulnerabilities categorized and prioritized?
<--- Score
24. Are there competing Backend as a service priorities?
<--- Score
25. Are missed Backend as a service opportunities costing your organization money?
<--- Score
26. How is progress measured?
<--- Score
27. What are the types and number of measures to use?
<--- Score
28. What causes innovation to fail or succeed in your organization?
<--- Score
29. Among the Backend as a service product and service cost to be estimated, which is considered hardest to estimate?
<--- Score
30. What are hidden Backend as a service quality costs?
<--- Score
31. Does the Backend as a service task fit the client’s priorities?
<--- Score
32. Do you effectively measure and reward individual and team performance?
<--- Score
33. What would it cost to replace your technology?
<--- Score
34. What does a Test Case verify?
<--- Score
35. How do you prevent mis-estimating cost?
<--- Score
36. Which measures and indicators matter?
<--- Score
37. What are your operating costs?
<--- Score
38. Which costs should be taken into account?
<--- Score
39. What are the uncertainties surrounding estimates of impact?
<--- Score
40. How will you measure your Backend as a service effectiveness?
<--- Score
41. Will Backend as a service have an impact on current business continuity, disaster recovery processes and/or infrastructure?
<--- Score
42. How will success or failure be measured?
<--- Score
43. Are the Backend as a service benefits worth its costs?
<--- Score
44. What happens if cost savings do not materialize?
<--- Score
45. How do you aggregate measures across priorities?
<--- Score
46. How do you verify your resources?
<--- Score
47. How are measurements made?
<--- Score
48. Is the cost worth the Backend as a service effort ?
<--- Score
49.