<--- Score
71. How is the team tracking and documenting its work?
<--- Score
72. What scope do you want your strategy to cover?
<--- Score
73. What is the scope of Source coding?
<--- Score
74. Has your scope been defined?
<--- Score
75. How do you hand over Source coding context?
<--- Score
76. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
77. What is out of scope?
<--- Score
78. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
79. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
80. Is there a critical path to deliver Source coding results?
<--- Score
81. How do you gather requirements?
<--- Score
82. Is special Source coding user knowledge required?
<--- Score
83. Have all of the relationships been defined properly?
<--- Score
84. Does the team have regular meetings?
<--- Score
85. How do you manage scope?
<--- Score
86. How will variation in the actual durations of each activity be dealt with to ensure that the expected Source coding results are met?
<--- Score
87. What constraints exist that might impact the team?
<--- Score
88. Are required metrics defined, what are they?
<--- Score
89. How often are the team meetings?
<--- Score
90. Why are you doing Source coding and what is the scope?
<--- Score
91. Does the scope remain the same?
<--- Score
92. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
93. How are consistent Source coding definitions important?
<--- Score
94. What is the worst case scenario?
<--- Score
95. Has/have the customer(s) been identified?
<--- Score
96. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
97. What is the definition of Source coding excellence?
<--- Score
98. What is a worst-case scenario for losses?
<--- Score
99. How will the Source coding team and the group measure complete success of Source coding?
<--- Score
100. What gets examined?
<--- Score
101. Do you all define Source coding in the same way?
<--- Score
102. What information do you gather?
<--- Score
103. What Source coding services do you require?
<--- Score
104. Are resources adequate for the scope?
<--- Score
105. Who are the Source coding improvement team members, including Management Leads and Coaches?
<--- Score
106. The political context: who holds power?
<--- Score
107. Is Source coding currently on schedule according to the plan?
<--- Score
108. Is Source coding linked to key stakeholder goals and objectives?
<--- Score
109. How do you gather the stories?
<--- Score
110. What system do you use for gathering Source coding information?
<--- Score
111. What are (control) requirements for Source coding Information?
<--- Score
112. Are roles and responsibilities formally defined?
<--- Score
113. 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
114. Are task requirements clearly defined?
<--- Score
115. What defines best in class?
<--- Score
116. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
117. Will a Source coding production readiness review be required?
<--- Score
118. Where can you gather more information?
<--- Score
119. What is in the scope and what is not in scope?
<--- Score
120. Have specific policy objectives been defined?
<--- Score
121. Is there a Source coding management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
122. Who is gathering information?
<--- Score
123. Is scope creep really all bad news?
<--- Score
124. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
125. How would you define Source coding leadership?
<--- Score
126. How do you keep key subject matter experts in the loop?
<--- Score
127. Are audit criteria, scope, frequency and methods defined?
<--- Score
128. What Source coding requirements should be gathered?
<--- Score
129.