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