Score
54. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
55. How do you think the partners involved in Technical Reference Model would have defined success?
<--- Score
56. Is it clearly defined in and to your organization what you do?
<--- Score
57. What would be the goal or target for a Technical Reference Model’s improvement team?
<--- Score
58. How have you defined all Technical Reference Model requirements first?
<--- Score
59. How do you hand over Technical Reference Model context?
<--- Score
60. What customer feedback methods were used to solicit their input?
<--- Score
61. How is the team tracking and documenting its work?
<--- Score
62. What intelligence can you gather?
<--- Score
63. Are the Technical Reference Model requirements testable?
<--- Score
64. Has/have the customer(s) been identified?
<--- Score
65. If substitutes have been appointed, have they been briefed on the Technical Reference Model goals and received regular communications as to the progress to date?
<--- Score
66. What is the scope of the Technical Reference Model work?
<--- Score
67. Has your scope been defined?
<--- Score
68. What critical content must be communicated – who, what, when, where, and how?
<--- Score
69. 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
70. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
71. When is the estimated completion date?
<--- Score
72. What is the definition of Technical Reference Model excellence?
<--- Score
73. Are accountability and ownership for Technical Reference Model clearly defined?
<--- Score
74. Is Technical Reference Model currently on schedule according to the plan?
<--- Score
75. How often are the team meetings?
<--- Score
76. What are the Technical Reference Model use cases?
<--- Score
77. What is a worst-case scenario for losses?
<--- Score
78. What is out of scope?
<--- Score
79. What scope do you want your strategy to cover?
<--- Score
80. Are roles and responsibilities formally defined?
<--- Score
81. Do you all define Technical Reference Model in the same way?
<--- Score
82. Has a team charter been developed and communicated?
<--- Score
83. Is Technical Reference Model required?
<--- Score
84. Are the Technical Reference Model requirements complete?
<--- Score
85. How does the Technical Reference Model manager ensure against scope creep?
<--- Score
86. Why are you doing Technical Reference Model and what is the scope?
<--- Score
87. Is special Technical Reference Model user knowledge required?
<--- Score
88. How do you build the right business case?
<--- Score
89. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
90. How would you define the culture at your organization, how susceptible is it to Technical Reference Model changes?
<--- Score
91. How will variation in the actual durations of each activity be dealt with to ensure that the expected Technical Reference Model results are met?
<--- Score
92. Has the Technical Reference Model 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
93. What is out-of-scope initially?
<--- Score
94. Have all of the relationships been defined properly?
<--- Score
95. When is/was the Technical Reference Model start date?
<--- Score
96. Are there any constraints known that bear on the ability to perform Technical Reference Model work? How is the team addressing them?
<--- Score
