Have all of the relationships been defined properly?
<--- Score
15. What are (control) requirements for Document processing Information?
<--- Score
16. What customer feedback methods were used to solicit their input?
<--- Score
17. Has the Document processing 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
18. How will variation in the actual durations of each activity be dealt with to ensure that the expected Document processing results are met?
<--- Score
19. Why are you doing Document processing and what is the scope?
<--- Score
20. What key stakeholder process output measure(s) does Document processing leverage and how?
<--- Score
21. Will team members regularly document their Document processing work?
<--- Score
22. What are the requirements for audit information?
<--- Score
23. Has the direction changed at all during the course of Document processing? If so, when did it change and why?
<--- Score
24. Has a Document processing requirement not been met?
<--- Score
25. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
26. What sort of initial information to gather?
<--- Score
27. What information do you gather?
<--- Score
28. How do you keep key subject matter experts in the loop?
<--- Score
29. What is a worst-case scenario for losses?
<--- Score
30. How do you manage unclear Document processing requirements?
<--- Score
31. What are the boundaries of the scope? What is in bounds and what is not? What is the start point? What is the stop point?
<--- Score
32. How do you gather Document processing requirements?
<--- Score
33. Is there any additional Document processing definition of success?
<--- Score
34. Are accountability and ownership for Document processing clearly defined?
<--- Score
35. Is the Document processing scope manageable?
<--- Score
36. What Document processing services do you require?
<--- Score
37. How do you think the partners involved in Document processing would have defined success?
<--- Score
38. Has a team charter been developed and communicated?
<--- Score
39. What are the Document processing tasks and definitions?
<--- Score
40. Has/have the customer(s) been identified?
<--- Score
41. Do you have organizational privacy requirements?
<--- Score
42. How does the Document processing manager ensure against scope creep?
<--- Score
43. What are the record-keeping requirements of Document processing activities?
<--- Score
44. Are task requirements clearly defined?
<--- Score
45. Is Document processing required?
<--- Score
46. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
47. How would you define Document processing leadership?
<--- Score
48. Are approval levels defined for contracts and supplements to contracts?
<--- Score
49. The political context: who holds power?
<--- Score
50. What scope to assess?
<--- Score
51. When is/was the Document processing start date?
<--- Score
52. Is the Document processing scope complete and appropriately sized?
<--- Score
53. Are the Document processing requirements testable?
<--- Score
54. Are improvement team members fully trained on Document processing?
<--- Score
55. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
56. Have specific policy objectives been defined?
<--- Score
57. What are the rough order estimates on cost savings/opportunities that Document processing brings?
<--- Score
58.
