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