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