so, when did it change and why?
<--- Score
56. What is out-of-scope initially?
<--- Score
57. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
58. How did the Document Engineering manager receive input to the development of a Document Engineering improvement plan and the estimated completion dates/times of each activity?
<--- Score
59. What are the compelling stakeholder reasons for embarking on Document Engineering?
<--- Score
60. What information do you gather?
<--- Score
61. Do you all define Document Engineering in the same way?
<--- Score
62. Where can you gather more information?
<--- Score
63. Has/have the customer(s) been identified?
<--- Score
64. 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
