Score
67. What is the worst case scenario?
<--- Score
68. What Software contract requirements should be gathered?
<--- Score
69. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
70. What was the context?
<--- Score
71. What critical content must be communicated – who, what, when, where, and how?
<--- Score
72. 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
73. The political context: who holds power?
<--- Score
74. Are all requirements met?
<--- Score
75. What is out of scope?
<--- Score
76. How do you think the partners involved in Software contract would have defined success?
<--- Score
77. What are the compelling stakeholder reasons for embarking on Software contract?
<--- Score
78. How do you gather requirements?
<--- Score
79. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
80. Who approved the Software contract scope?
<--- Score
81. Does the scope remain the same?
<--- Score
82. Has the direction changed at all during the course of Software contract? If so, when did it change and why?
<--- Score
83. Who are the Software contract improvement team members, including Management Leads and Coaches?
<--- Score
84. What is out-of-scope initially?
<--- Score
85. What are the Software contract use cases?
<--- Score
86. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
87. Is Software contract linked to key stakeholder goals and objectives?
<--- Score
88. What customer feedback methods were used to solicit their input?
<--- Score
89. Are accountability and ownership for Software contract clearly defined?
<--- Score
90. What sources do you use to gather information for a Software contract study?
<--- Score
91. What are the tasks and definitions?
<--- Score
92. What are the rough order estimates on cost savings/opportunities that Software contract brings?
<--- Score
93. Who defines (or who defined) the rules and roles?
<--- Score
94. What is in the scope and what is not in scope?
<--- Score
95. How would you define Software contract leadership?
<--- Score
96. Are roles and responsibilities formally defined?
<--- Score
97. What is the definition of Software contract excellence?
<--- Score
98. Is scope creep really all bad news?
<--- Score
99. What is the scope of Software contract?
<--- Score
100. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
101. Is the Software contract scope complete and appropriately sized?
<--- Score
102. Is Software contract currently on schedule according to the plan?
<--- Score
103. Are the Software contract requirements testable?
<--- Score
104. What information should you gather?
<--- Score
105. How do you manage scope?
<--- Score
106. What constraints exist that might impact the team?
<--- Score
107. Are there different segments of customers?
<--- Score
108. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
109. How did the Software contract manager receive input to the development of a Software contract improvement plan and the estimated completion dates/times of each activity?
<--- Score
110. What is the definition of success?
<--- Score
111. Have the customer needs been
