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.
CRITERION #2: DEFINE:
INTENT: Formulate the stakeholder problem. Define the problem, needs and objectives.
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 often are the team meetings?
<--- Score
2. When is the estimated completion date?
<--- Score
3. What are the boundaries of the scope? What is in bounds and what is not? What is the start point? What is the stop point?
<--- Score
4. How would you define the culture at your organization, how susceptible is it to Software reliability testing changes?
<--- Score
5. Do you have organizational privacy requirements?
<--- Score
6. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
7. What information should you gather?
<--- Score
8. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
9. Is there a Software reliability testing management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
10. Is scope creep really all bad news?
<--- Score
11. What are the compelling stakeholder reasons for embarking on Software reliability testing?
<--- Score
12. How does the Software reliability testing manager ensure against scope creep?
<---
