Score
65. What was the context?
<--- Score
66. Are the Carbon project requirements testable?
<--- Score
67. Is Carbon project required?
<--- Score
68. Scope of sensitive information?
<--- Score
69. What is in scope?
<--- Score
70. What is the definition of success?
<--- Score
71. How do you hand over Carbon project context?
<--- Score
72. How do you manage scope?
<--- Score
73. How will the Carbon project team and the group measure complete success of Carbon project?
<--- Score
74. Is Carbon project linked to key stakeholder goals and objectives?
<--- Score
75. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
76. Who approved the Carbon project scope?
<--- Score
77. How would you define the culture at your organization, how susceptible is it to Carbon project changes?
<--- Score
78. What is the context?
<--- Score
79. What information should you gather?
<--- Score
80. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?
<--- Score
81. What constraints exist that might impact the team?
<--- Score
82. What gets examined?
<--- Score
83. What are the core elements of the Carbon project business case?
<--- Score
84. What sources do you use to gather information for a Carbon project study?
<--- Score
85. 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
86. What is the worst case scenario?
<--- Score
87. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
88. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
89. What customer feedback methods were used to solicit their input?
<--- Score
90. How do you keep key subject matter experts in the loop?
<--- Score
91. If substitutes have been appointed, have they been briefed on the Carbon project goals and received regular communications as to the progress to date?
<--- Score
92. How is the team tracking and documenting its work?
<--- Score
93. Who defines (or who defined) the rules and roles?
<--- Score
94. What is a worst-case scenario for losses?
<--- Score
95. What defines best in class?
<--- Score
96. Are approval levels defined for contracts and supplements to contracts?
<--- Score
97. What is out of scope?
<--- Score
98. How do you gather the stories?
<--- Score
99. How would you define Carbon project leadership?
<--- Score
100. How do you build the right business case?
<--- Score
101. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
102. How did the Carbon project manager receive input to the development of a Carbon project improvement plan and the estimated completion dates/times of each activity?
<--- Score
103. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
104. Are all requirements met?
<--- Score
105. Are there any constraints known that bear on the ability to perform Carbon project work? How is the team addressing them?
<--- Score
106. What scope do you want your strategy to cover?
<--- Score
107. Do you have organizational privacy requirements?
<--- Score
108. Is scope creep really all bad news?
<--- Score
109. Is the Carbon project scope manageable?
