have reached your goal and need to set a new one?
<--- Score
71. Did you miss any major Software test engineering issues?
<--- Score
72. Would you recognize a threat from the inside?
<--- Score
73. What is the extent or complexity of the Software test engineering problem?
<--- Score
74. Will it solve real problems?
<--- Score
75. Consider your own Software test engineering project, what types of organizational problems do you think might be causing or affecting your problem, based on the work done so far?
<--- Score
76. What is the recognized need?
<--- Score
77. Are losses recognized in a timely manner?
<--- Score
78. What are the stakeholder objectives to be achieved with Software test engineering?
<--- Score
79. Who are your key stakeholders who need to sign off?
<--- Score
80. What else needs to be measured?
<--- Score
81. How are the Software test engineering’s objectives aligned to the group’s overall stakeholder strategy?
<--- Score
82. Think about the people you identified for your Software test engineering 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
83. How do you take a forward-looking perspective in identifying Software test engineering research related to market response and models?
<--- Score
84. How do you recognize an objection?
<--- Score
85. What are your needs in relation to Software test engineering skills, labor, equipment, and markets?
<--- Score
86. Do you recognize Software test engineering achievements?
<--- Score
87. Who should resolve the Software test engineering issues?
<--- Score
88. What Software test engineering events should you attend?
<--- Score
89. Do you know what you need to know about Software test engineering?
<--- Score
90. What vendors make products that address the Software test engineering needs?
<--- Score
91. Are employees recognized for desired behaviors?
<--- Score
92. Which issues are too important to ignore?
<--- Score
93. What would happen if Software test engineering weren’t done?
<--- Score
94. Which needs are not included or involved?
<--- Score
95. What is the Software test engineering problem definition? What do you need to resolve?
<--- Score
96. Do you have/need 24-hour access to key personnel?
<--- Score
97. Do you need to avoid or amend any Software test engineering activities?
<--- Score
98. How do you identify subcontractor relationships?
<--- Score
99. What activities does the governance board need to consider?
<--- 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 test engineering 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. Has the direction changed at all during the course of Software test engineering? If so, when did it change and why?
<--- Score
2. What is the scope?
<--- Score
3. Are accountability and ownership for Software test engineering clearly defined?
<--- Score
4. What is the scope of Software test engineering?
<--- Score
5. What customer feedback methods were used to solicit their input?
<--- Score
6. What is the scope of the Software test engineering effort?
<--- Score
7. What critical content must be communicated – who, what, when, where, and how?
<--- Score
8. What baselines are required to be defined and managed?
<--- Score
9.
