the scope?
<--- Score
11. How do you manage changes in Document Engineering requirements?
<--- Score
12. What is the definition of Document Engineering excellence?
<--- Score
13. Scope of sensitive information?
<--- Score
14. Are the Document Engineering requirements testable?
<--- Score
15. What is the worst case scenario?
<--- Score
16. How and when will the baselines be defined?
<--- Score
17. What are the Document Engineering tasks and definitions?
<--- Score
18. Will a Document Engineering production readiness review be required?
<--- Score
19. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
20. What is in scope?
<--- Score
21. Has a Document Engineering requirement not been met?
<--- Score
22. Are task requirements clearly defined?
<--- Score
23. What are the core elements of the Document Engineering business case?
<--- Score
24. Is Document Engineering linked to key stakeholder goals and objectives?
<--- Score
25. When is/was the Document Engineering start date?
<--- Score
26. What are (control) requirements for Document Engineering Information?
<--- Score
27. When is the estimated completion date?
<--- Score
28. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
29. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
30. Is there a Document Engineering management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
31. How do you think the partners involved in Document Engineering would have defined success?
<--- Score
32. What constraints exist that might impact the team?
<--- Score
33. What Document Engineering requirements should be gathered?
<--- Score
34. Do you have organizational privacy requirements?
<--- Score
35. How do you gather requirements?
<--- Score
36. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
37. Is scope creep really all bad news?
<--- Score
38. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
39. Who is gathering information?
<--- Score
40. What is the scope of the Document Engineering work?
<--- Score
41. What is the scope of Document Engineering?
<--- Score
42. Is the work to date meeting requirements?
<--- Score
43. Why are you doing Document Engineering and what is the scope?
<--- Score
44. What is the context?
<--- Score
45. How do you catch Document Engineering definition inconsistencies?
<--- Score
46. How can the value of Document Engineering be defined?
<--- Score
47. What customer feedback methods were used to solicit their input?
<--- Score
48. How is the team tracking and documenting its work?
<--- Score
49. What system do you use for gathering Document Engineering information?
<--- Score
50. How will variation in the actual durations of each activity be dealt with to ensure that the expected Document Engineering results are met?
<--- Score
51. Is there a critical path to deliver Document Engineering results?
<--- Score
52. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
53. Is the scope of Document Engineering defined?
<--- Score
54. What are the dynamics of the communication plan?
<--- Score
55. Has the direction changed at all during the course of Document Engineering?
