Software Contract A Complete Guide - 2020 Edition. Gerardus Blokdyk

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 translated into specific, measurable requirements? How?

      <--- Score

      112. Are approval levels defined for contracts and supplements to contracts?

      <--- Score

      113. How will the Software contract team and the group measure complete success of Software contract?

      <--- Score

      114. What would be the goal or target for a Software contract’s improvement team?

      <--- Score

      115. When are meeting minutes sent out? Who is on the distribution list?

      <--- Score

      116. What is in scope?

      <--- Score

      117. What scope do you want your strategy to cover?

      <--- Score

      118. In what way can you redefine the criteria of choice clients have in your category in your favor?

      <--- Score

      119. What key stakeholder process output measure(s) does Software contract leverage and how?

      <--- Score

      120. What are the requirements for audit information?

      <--- Score

      121. Are there any constraints known that bear on the ability to perform Software contract work? How is the team addressing them?

      <--- Score

      122. Has the Software contract 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

      123. What gets examined?

      <--- Score

      124. What is the scope of the Software contract effort?

      <--- Score

      125. Is the work to date meeting requirements?

      <--- Score

      126. How is the team tracking and documenting its work?

      <--- Score

      127. What is a worst-case scenario for losses?

      <--- Score

      128. Are there special functional requirements for assistance systems in electric vehicles?

      <--- Score

      129. If substitutes have been appointed, have they been briefed on the Software contract goals and received regular communications as to the progress to date?

      <--- Score

      130. Has a Software contract requirement not been met?

      <--- Score

      131. How do you keep key subject matter experts in the loop?

      <--- Score

      132.