Читать книгу Software Reliability Testing A Complete Guide - 2020 Edition - Gerardus Blokdyk - Страница 7
ОглавлениеCRITERION #1: RECOGNIZE
INTENT: Be aware of the need for change. Recognize that there is an unfavorable variation, problem or symptom.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
1. Will it solve real problems?
<--- Score
2. Who else hopes to benefit from it?
<--- Score
3. Are there Software reliability testing problems defined?
<--- Score
4. What are the expected benefits of Software reliability testing to the stakeholder?
<--- Score
5. What are the minority interests and what amount of minority interests can be recognized?
<--- Score
6. What are your needs in relation to Software reliability testing skills, labor, equipment, and markets?
<--- Score
7. What situation(s) led to this Software reliability testing Self Assessment?
<--- Score
8. Consider your own Software reliability testing project, what types of organizational problems do you think might be causing or affecting your problem, based on the work done so far?
<--- Score
9. What information do users need?
<--- Score
10. Do you recognize Software reliability testing achievements?
<--- Score
11. Are employees recognized or rewarded for performance that demonstrates the highest levels of integrity?
<--- Score
12. Is it clear when you think of the day ahead of you what activities and tasks you need to complete?
<--- Score
13. Which needs are not included or involved?
<--- Score
14. Why the need?
<--- Score
15. Which issues are too important to ignore?
<--- Score
16. Will Software reliability testing deliverables need to be tested and, if so, by whom?
<--- Score
17. What needs to be done?
<--- Score
18. Is the need for organizational change recognized?
<--- Score
19. When a Software reliability testing manager recognizes a problem, what options are available?
<--- Score
20. Who needs to know about Software reliability testing?
<--- Score
21. Does the problem have ethical dimensions?
<--- Score
22. Who defines the rules in relation to any given issue?
<--- Score
23. What Software reliability testing problem should be solved?
<--- Score
24. What does Software reliability testing success mean to the stakeholders?
<--- Score
25. As a sponsor, customer or management, how important is it to meet goals, objectives?
<--- Score
26. Who needs what information?
<--- Score
27. What tools and technologies are needed for a custom Software reliability testing project?
<--- Score
28. Are controls defined to recognize and contain problems?
<--- Score
29. What are the timeframes required to resolve each of the issues/problems?
<--- Score
30. What Software reliability testing events should you attend?
<--- Score
31. What are the stakeholder objectives to be achieved with Software reliability testing?
<--- Score
32. What problems are you facing and how do you consider Software reliability testing will circumvent those obstacles?
<--- Score
33. Are problem definition and motivation clearly presented?
<--- Score
34. To what extent would your organization benefit from being recognized as a award recipient?
<--- Score
35. What Software reliability testing coordination do you need?
<--- Score
36. Do you need different information or graphics?
<--- Score
37. What else needs to be measured?
<--- Score
38. Have you identified your Software reliability testing key performance indicators?
<--- Score
39. Will a response program recognize when a crisis occurs and provide some level of response?
<--- Score
40. What prevents you from making the changes you know will make you a more effective Software reliability testing leader?
<--- Score
41. How do you take a forward-looking perspective in identifying Software reliability testing research related to market response and models?
<--- Score
42. Do you need to avoid or amend any Software reliability testing activities?
<--- Score
43. What do you need to start doing?
<--- Score
44. Where do you need to exercise leadership?
<--- Score
45. Who should resolve the Software reliability testing issues?
<--- Score
46. What is the recognized need?
<--- Score
47. Are you dealing with any of the same issues today as yesterday? What can you do about this?
<--- Score
48. What resources or support might you need?
<--- Score
49. Are your goals realistic? Do you need to redefine your problem? Perhaps the problem has changed or maybe you have reached your goal and need to set a new one?
<--- Score
50. Looking at each person individually – does every one have the qualities which are needed to work in this group?
<--- Score
51. Does Software reliability testing create potential expectations in other areas that need to be recognized and considered?
<--- Score
52. How much are sponsors, customers, partners, stakeholders involved in Software reliability testing? In other words, what are the risks, if Software reliability testing does not deliver successfully?
<--- Score
53. Would you recognize a threat from the inside?
<--- Score
54. Do you have/need 24-hour access to key personnel?
<--- Score
55. Does your organization need more Software reliability testing education?
<--- Score
56. Who needs budgets?
<--- Score
57. What is the problem or issue?
<--- Score
58. What needs to stay?
<--- Score
59. Are employees recognized for desired behaviors?
<--- Score
60. Are losses recognized in a timely manner?
<--- Score
61. Who needs to know?
<--- Score
62. What extra resources will you need?
<--- Score
63. Which information does the Software reliability testing business case need to include?
<--- Score
64. Are there regulatory / compliance issues?
<--- Score
65. What activities does the governance board need to consider?
<--- Score
66. Think about the people you identified for your Software reliability testing project and the project responsibilities you would assign to them, what kind of training do you think they would need to perform these responsibilities effectively?
<--- Score
67. What should be considered when identifying available resources, constraints, and deadlines?
<--- Score
68. How many trainings, in total, are needed?
<--- Score
69. Whom do you really need or want to serve?
<--- Score
70. How are the Software reliability testing’s objectives aligned to the group’s overall stakeholder strategy?
<--- Score
71. What creative shifts do you need to take?
<--- Score
72. Are there any specific expectations or concerns about the Software reliability testing team, Software reliability testing itself?
<--- Score
73. How do you identify subcontractor relationships?
<--- Score
74. For your Software reliability testing project, identify and describe the business environment, is there more than one layer to the business environment?
<--- Score
75. How can auditing be a preventative security measure?
<--- Score
76. What is the extent or complexity of the Software reliability testing problem?
<--- Score
77. How are you going to measure success?
<--- Score
78. To what extent does each concerned units management team recognize Software reliability testing as an effective investment?
<--- Score
79. How do you identify the kinds of information that you will need?
<--- Score
80. Is the quality assurance team identified?
<--- Score
81. Is it needed?
<--- Score
82. Are there any revenue recognition issues?
<--- Score
83. How does it fit into your organizational needs and tasks?
<--- Score
84. Are there recognized Software reliability testing problems?
<--- Score
85. What vendors make products that address the Software reliability testing needs?
<--- Score
86. Who are your key stakeholders who need to sign off?
<--- Score
87. What would happen if Software reliability testing weren’t done?
<--- Score
88. What is the smallest subset of the problem you can usefully solve?
<--- Score
89. What is the problem and/or vulnerability?
<--- Score
90. Will new equipment/products be required to facilitate Software reliability testing delivery, for example is new software needed?
<--- Score
91. How do you recognize an objection?
<--- Score
92. How do you recognize an Software reliability testing objection?
<--- Score
93. Why is this needed?
<--- 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 Software reliability testing Index at the beginning of the Self-Assessment.
