Читать книгу Software Test Engineering A Complete Guide - 2020 Edition - Gerardus Blokdyk - Страница 8
Оглавление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. How do you catch Software test engineering definition inconsistencies?
<--- Score
10. How often are the team meetings?
<--- Score
11. Are the Software test engineering requirements complete?
<--- Score
12. The political context: who holds power?
<--- Score
13. What was the context?
<--- Score
14. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
15. How do you build the right business case?
<--- Score
16. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
17. How would you define the culture at your organization, how susceptible is it to Software test engineering changes?
<--- Score
18. What is the scope of the Software test engineering work?
<--- Score
19. What are the requirements for audit information?
<--- Score
20. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
21. Are audit criteria, scope, frequency and methods defined?
<--- Score
22. Does the team have regular meetings?
<--- Score
23. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
24. What gets examined?
<--- Score
25. Is it clearly defined in and to your organization what you do?
<--- Score
26. Have all basic functions of Software test engineering been defined?
<--- Score
27. Have all of the relationships been defined properly?
<--- Score
28. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
29. What are the rough order estimates on cost savings/opportunities that Software test engineering brings?
<--- Score
30. How is the team tracking and documenting its work?
<--- Score
31. What is the definition of Software test engineering excellence?
<--- Score
32. What system do you use for gathering Software test engineering information?
<--- Score
33. Who is gathering Software test engineering information?
<--- Score
34. Are approval levels defined for contracts and supplements to contracts?
<--- Score
35. What are the compelling stakeholder reasons for embarking on Software test engineering?
<--- Score
36. How do you gather requirements?
<--- Score
37. What are (control) requirements for Software test engineering Information?
<--- Score
38. What key stakeholder process output measure(s) does Software test engineering leverage and how?
<--- Score
39. What is the context?
<--- Score
40. Are resources adequate for the scope?
<--- Score
41. What defines best in class?
<--- Score
42. How have you defined all Software test engineering requirements first?
<--- Score
43. Is special Software test engineering user knowledge required?
<--- Score
44. What is out-of-scope initially?
<--- Score
45. Is there any additional Software test engineering definition of success?
<--- Score
46. Is there a Software test engineering management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
47. Is Software test engineering required?
<--- Score
48. What happens if Software test engineering’s scope changes?
<--- Score
49. Has a team charter been developed and communicated?
<--- Score
50. What sort of initial information to gather?
<--- Score
51. Has the Software test engineering work been fairly and/or equitably divided and delegated among team members who are qualified and capable to perform the work? Has everyone contributed?
<--- Score
52. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
53. Do you have organizational privacy requirements?
<--- Score
54. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
55. What is the definition of success?
<--- Score
56. What are the Software test engineering use cases?
<--- Score
57. What is a worst-case scenario for losses?
<--- Score
58. What information should you gather?
<--- Score
59. Is the Software test engineering scope manageable?
<--- Score
60. How do you keep key subject matter experts in the loop?
<--- Score
61. Has a Software test engineering requirement not been met?
<--- Score
62. How do you hand over Software test engineering context?
<--- Score
63. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
64. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
65. Do you have a Software test engineering success story or case study ready to tell and share?
<--- Score
66. Scope of sensitive information?
<--- Score
67. Has your scope been defined?
<--- Score
68. How do you manage unclear Software test engineering requirements?
<--- Score
69. How will variation in the actual durations of each activity be dealt with to ensure that the expected Software test engineering results are met?
<--- Score
70. What are the Software test engineering tasks and definitions?
<--- Score
71. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
72. 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
73. What are the tasks and definitions?
<--- Score
74. What is in scope?
<--- Score
75. How do you manage scope?
<--- Score
76. Do you all define Software test engineering in the same way?
<--- Score
77. If substitutes have been appointed, have they been briefed on the Software test engineering goals and received regular communications as to the progress to date?
<--- Score
78. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
79. Has/have the customer(s) been identified?
<--- Score
80. Is Software test engineering currently on schedule according to the plan?
<--- Score
81. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
82. What would be the goal or target for a Software test engineering’s improvement team?
<--- Score
83. Is the Software test engineering scope complete and appropriately sized?
<--- Score
84. What sources do you use to gather information for a Software test engineering study?
<--- Score
85. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
86. How can the value of Software test engineering be defined?
<--- Score
87. When is the estimated completion date?
<--- Score
88. How do you think the partners involved in Software test engineering would have defined success?
<--- Score
89. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
90. Is there a critical path to deliver Software test engineering results?
<--- Score
91. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
92. Are the Software test engineering requirements testable?
<--- Score
93. Have specific policy objectives been defined?
<--- Score
94. What is the worst case scenario?
<--- Score
95. Is there a clear Software test engineering case definition?
<--- Score
96. Is scope creep really all bad news?
<--- Score
97. Is the team equipped with available and reliable resources?
<--- Score
98. Is the improvement team aware of the different versions of a process: what they think it is vs. what it actually is vs. what it should be vs. what it could be?
<--- Score
99. Are roles and responsibilities formally defined?
<--- Score
100. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?
<--- Score
101. How do you gather Software test engineering requirements?
<--- Score
102. Are there any constraints known that bear on the ability to perform Software test engineering work? How is the team addressing them?
<--- Score
103. How do you manage changes in Software test engineering requirements?
<--- Score
104. Are there different segments of customers?
<--- Score
105. When is/was the Software test engineering start date?
<--- Score
106. How does the Software test engineering manager ensure against scope creep?
<--- Score
107. How do you gather the stories?
<--- Score
108. Who are the Software test engineering improvement team members, including Management Leads and Coaches?
<--- Score
109. Who is gathering information?
<--- Score
110. How will the Software test engineering team and the group measure complete success of Software test engineering?
<--- Score
111. What are the record-keeping requirements of Software test engineering activities?
<--- Score
112. What Software test engineering requirements should be gathered?
<--- Score
113. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
114. How are consistent Software test engineering definitions important?
<--- Score
115. What intelligence can you gather?
<--- Score
116. Are all requirements met?
<--- Score
117. How and when will the baselines be defined?
<--- Score
118. Who approved the Software test engineering scope?
<--- Score
119. Is the work to date meeting requirements?
<--- Score
120. What are the core elements of the Software test engineering business case?
<--- Score
121. What information do you gather?
<--- Score
122. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
123. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
124. What is in the scope and what is not in scope?
<--- Score
125. How did the Software test engineering manager receive input to the development of a Software test engineering improvement plan and the estimated completion dates/times of each activity?
<--- Score
126. Is the scope of Software test engineering defined?
<--- Score
127. Who defines (or who defined) the rules and roles?
<--- Score
128. What are the dynamics of the communication plan?
<--- Score
129. Are task requirements clearly defined?
<--- Score
130. How would you define Software test engineering leadership?
<--- Score
131. Where can you gather more information?
<--- Score
132. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
133. What constraints exist that might impact the team?
<--- Score
134. What Software test engineering services do you require?
<--- Score
135. Does the scope remain the same?
<--- Score
136. Is Software test engineering linked to key stakeholder goals and objectives?
<--- Score
137. What scope do you want your strategy to cover?
<--- 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.
