LITMIR.BIZ

Скачать книгу

What gets examined?

      <--- Score

      66. Does the scope remain the same?

      <--- Score

      67. How will variation in the actual durations of each activity be dealt with to ensure that the expected Firmware as a Service results are met?

      <--- Score

      68. What sources do you use to gather information for a Firmware as a Service study?

      <--- Score

      69. What Firmware as a Service requirements should be gathered?

      <--- Score

      70. Does the team have regular meetings?

      <--- Score

      71. Have the customer needs been translated into specific, measurable requirements? 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. How do you manage unclear Firmware as a Service requirements?

      <--- Score

      74. Is Firmware as a Service required?

      <--- Score

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

      <--- Score

      76. Have all of the relationships been defined properly?

      <--- Score

      77. Do you have organizational privacy requirements?

      <--- Score

      78. Is there a clear Firmware as a Service case definition?

      <--- Score

      79. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?

      <--- Score

      80. What sort of initial information to gather?

      <--- Score

      81. Has/have the customer(s) been identified?

      <--- Score

      82. What is the scope of Firmware as a Service?

      <--- Score

      83. Are resources adequate for the scope?

      <--- Score

      84. What would be the goal or target for a Firmware as a Service’s improvement team?

      <--- Score

      85. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?

      <--- Score

      86. What is the scope?

      <--- Score

      87. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?

      <--- Score

      88. What happens if Firmware as a Service’s scope changes?

      <--- Score

      89. What is the context?

      <--- Score

      90. What defines best in class?

      <--- Score

      91. How would you define Firmware as a Service leadership?

      <--- Score

      92. Is it clearly defined in and to your organization what you do?

      <--- Score

      93. Who defines (or who defined) the rules and roles?

      <--- Score

      94. What is out-of-scope initially?

      <--- Score

      95. How often are the team meetings?

      <--- Score

      96. How do you gather Firmware as a Service requirements?

      <--- Score

      97. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?

      <--- Score

      98. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?

      <--- Score

      99. Is the Firmware as a Service scope complete and appropriately sized?

      <--- Score

      100. Are customer(s) identified and segmented according to their different needs and requirements?

      <--- Score

      101. How do you hand over Firmware as a Service context?

      <--- Score

      102. Are required metrics defined, what are they?

      <--- Score

      103. What key stakeholder process output measure(s) does Firmware as a Service leverage and how?

      <--- Score

      104. When is/was the Firmware as a Service start date?

      <--- Score

      105. How do you build the right business case?

      <--- Score

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

      <--- Score

      107. What are the Firmware as a Service tasks and definitions?

      <--- Score

      108. Are task requirements clearly defined?

      <--- Score

      109. Will team members perform Firmware as a Service work when assigned and in a timely fashion?

      <--- Score

      110. Are roles and responsibilities formally defined?

      <--- Score

      111. What is in the scope and what is not in scope?

      <--- Score

      112. How do you gather requirements?

      <--- Score

      113. Are the Firmware as a Service requirements complete?

      <--- Score

      114. Who are the Firmware as a Service improvement team members, including Management Leads and Coaches?

      <--- Score

      115. What intelligence can you gather?

      <--- Score

      116. Why are you doing Firmware as a Service and what is the scope?

      <--- Score

      117. What is in scope?

      <--- Score

      118. When is the estimated completion date?

      <--- Score

      119. Are there any constraints known that bear on the ability to perform Firmware as a Service work? How is the team addressing them?

      <--- Score

      120. What customer feedback methods were used to solicit their input?

      <--- Score

      121. Is data collected and displayed to better understand customer(s) critical needs and requirements.

      <---

Скачать книгу