date?
<--- Score
44. How often are the team meetings?
<--- Score
45. What is the scope of Customer Information Control System?
<--- Score
46. How do you gather the stories?
<--- Score
47. What scope do you want your strategy to cover?
<--- Score
48. Have all of the relationships been defined properly?
<--- Score
49. What customer feedback methods were used to solicit their input?
<--- Score
50. How do you keep key subject matter experts in the loop?
<--- Score
51. Have specific policy objectives been defined?
<--- Score
52. What scope to assess?
<--- Score
53. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
54. Are approval levels defined for contracts and supplements to contracts?
<--- Score
55. What knowledge or experience is required?
<--- Score
56. Who defines (or who defined) the rules and roles?
<--- Score
57. What is the scope?
<--- Score
58. How do you build the right business case?
<--- Score
59. Has the Customer Information Control System 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
60. How have you defined all Customer Information Control System requirements first?
<--- Score
61. What sort of initial information to gather?
<--- Score
62. How do you hand over Customer Information Control System context?
<--- Score
63. Has your scope been defined?
<--- Score
64. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
65. What is the scope of the Customer Information Control System effort?
<--- Score
66. The political context: who holds power?
<--- Score
67. What is in scope?
<--- Score
68. How will variation in the actual durations of each activity be dealt with to ensure that the expected Customer Information Control System results are met?
<--- Score
69. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
70. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
71. Do you have organizational privacy requirements?
<--- Score
72. Have all basic functions of Customer Information Control System been defined?
<--- Score
73. What happens if Customer Information Control System’s scope changes?
<--- Score
74. Do you have a Customer Information Control System success story or case study ready to tell and share?
<--- Score
75. Who approved the Customer Information Control System scope?
<--- Score
76. What are the dynamics of the communication plan?
<--- Score
77. Are audit criteria, scope, frequency and methods defined?
<--- Score
78. What are the rough order estimates on cost savings/opportunities that Customer Information Control System brings?
<--- Score
79. What is the context?
<--- Score
80. How would you define the culture at your organization, how susceptible is it to Customer Information Control System changes?
<--- Score
81. What baselines are required to be defined and managed?
<--- Score
82. Is scope creep really all bad news?
<--- Score
83. Is the Customer Information Control System scope complete and appropriately sized?
<--- Score
84. Are task requirements clearly defined?
<--- Score
85. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
86. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
87. How would you define Customer Information Control System
