LITMIR.BIZ

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

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

      <--- Score

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

      <--- Score

      66. How do you build the right business case?

      <--- Score

      67. 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

      68. Have specific policy objectives been defined?

      <--- Score

      69. Is there a clear Document Engineering case definition?

      <--- Score

      70. 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

      71. What information should you gather?

      <--- Score

      72. Is there any additional Document Engineering definition of success?

      <--- Score

      73. Do you have a Document Engineering success story or case study ready to tell and share?

      <--- Score

      74. What sort of initial information to gather?

      <--- Score

      75. Who is gathering Document Engineering information?

      <--- Score

      76. What scope to assess?

      <--- Score

      77. What are the rough order estimates on cost savings/opportunities that Document Engineering brings?

      <--- Score

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

      <--- Score

      79. Are required metrics defined, what are they?

      <--- Score

      80. Does the team have regular meetings?

      <--- Score

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

      <--- Score

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

      <--- Score

      83. What are the requirements for audit information?

      <--- Score

      84. What Document Engineering services do you require?

      <--- Score

      85. How are consistent Document Engineering definitions important?

      <--- Score

      86. What is the scope of the Document Engineering effort?

      <--- Score

      87. Is Document Engineering required?

      <--- Score

      88. How do you manage unclear Document Engineering requirements?

      <--- Score

      89. Are all requirements met?

      <--- Score

      90. Is the Document Engineering scope manageable?

      <--- Score

      91. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?

      <--- Score

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

      <--- Score

      93. Has a project plan, Gantt chart, or similar been developed/completed?

      <--- Score

      94. What knowledge or experience is required?

      <--- Score

      95. Have all basic functions of Document Engineering been defined?

      <--- Score

      96. How will the Document Engineering team and the group measure complete success of Document Engineering?

      <--- Score

      97. Who approved the Document Engineering scope?

      <--- Score

      98. What gets examined?

      <--- Score

      99. What are the record-keeping requirements of Document Engineering activities?

      <--- Score

      100. How would you define the culture at your organization, how susceptible is it to Document Engineering changes?

      <--- Score

      101. How would you define Document Engineering leadership?

      <--- Score

      102. How have you defined all Document Engineering requirements first?

      <--- Score

      103. Is the current ‘as is’ process being followed? If not, what are the discrepancies?

      <--- Score

      104. How does the Document Engineering manager ensure against scope creep?

      <--- Score

      105. How do you gather Document Engineering requirements?

      <--- Score

      106. What intelligence can you gather?

      <--- Score

      107. What sources do you use to gather information for a Document Engineering study?

      <--- Score

      108. Are the Document Engineering requirements complete?

      <--- Score

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

      <--- Score

      110. Does the scope remain the same?

      <--- Score

      111. The political context: who holds power?

      <--- Score

      112. What is the scope?

      <--- Score

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

      <--- Score

      114. What is out of scope?

      <--- Score

      115. Are audit criteria, scope, frequency and methods defined?

      <--- Score

      116. What critical content must be communicated – who, what, when, where, and how?

      <--- Score

      117. How often are the team meetings?

      <--- Score

      118. Are different versions of process maps needed to account for the different types of inputs?

      <--- Score

      119. How do you manage scope?

      <--- Score

      120. Are accountability and ownership for Document Engineering clearly defined?

      <---

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