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?
<---
