defined success?
<--- Score
61. What customer feedback methods were used to solicit their input?
<--- Score
62. What sort of initial information to gather?
<--- Score
63. What is in scope?
<--- Score
64. Do you have a Source coding success story or case study ready to tell and share?
<--- Score
65. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
66. Is it clearly defined in and to your organization what you do?
<--- Score
67. What knowledge or experience is required?
<--- Score
68. What are the Source coding use cases?
<--- Score
69. How does the Source coding manager ensure against scope creep?
<--- Score
70. How did the Source coding manager receive input to the development of a Source coding improvement plan and the estimated completion dates/times of each activity?
<--- 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.
