and what is not in scope?
<--- Score
10. Have specific policy objectives been defined?
<--- Score
11. What scope to assess?
<--- Score
12. How and when will the baselines be defined?
<--- Score
13. Do you have a Technical Reference Model success story or case study ready to tell and share?
<--- Score
14. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
15. What happens if Technical Reference Model’s scope changes?
<--- Score
16. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
17. What sources do you use to gather information for a Technical Reference Model study?
<--- Score
18. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
19. Who is gathering Technical Reference Model information?
<--- Score
20. Is there any additional Technical Reference Model definition of success?
<--- Score
21. What gets examined?
<--- Score
22. Is the Technical Reference Model scope complete and appropriately sized?
<--- Score
23. Are there different segments of customers?
<--- Score
24. What are the requirements for audit information?
<--- Score
25. How do you gather Technical Reference Model requirements?
<--- Score
26. What are the compelling stakeholder reasons for embarking on Technical Reference Model?
<--- Score
27. Has the direction changed at all during the course of Technical Reference Model? If so, when did it change and why?
<--- Score
28. Do you have organizational privacy requirements?
<--- Score
29. What sort of initial information to gather?
<--- Score
30. What are the tasks and definitions?
<--- Score
31. What is the worst case scenario?
<--- Score
32. What baselines are required to be defined and managed?
<--- Score
33. Is the Technical Reference Model scope manageable?
<--- Score
34. Is there a clear Technical Reference Model case definition?
<--- Score
35. Is Technical Reference Model linked to key stakeholder goals and objectives?
<--- Score
36. What are the Technical Reference Model tasks and definitions?
<--- Score
37. What is the definition of success?
<--- Score
38. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
39. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
40. What system do you use for gathering Technical Reference Model information?
<--- Score
41. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
42. What key stakeholder process output measure(s) does Technical Reference Model leverage and how?
<--- Score
43. How do you manage scope?
<--- Score
44. How do you keep key subject matter experts in the loop?
<--- Score
45. What Technical Reference Model services do you require?
<--- Score
46. The political context: who holds power?
<--- Score
47. How do you catch Technical Reference Model definition inconsistencies?
<--- Score
48. Are resources adequate for the scope?
<--- Score
49. Where can you gather more information?
<--- Score
50. How can the value of Technical Reference Model be defined?
<--- Score
51. 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
52. What is the context?
<--- Score
53. Who are the Technical Reference Model improvement team members, including Management Leads and Coaches?
<---
