<--- Score
14. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
15. What are (control) requirements for Collaborative tools Information?
<--- Score
16. Are accountability and ownership for Collaborative tools clearly defined?
<--- Score
17. Do you have a Collaborative tools success story or case study ready to tell and share?
<--- Score
18. How will variation in the actual durations of each activity be dealt with to ensure that the expected Collaborative tools results are met?
<--- Score
19. What are the record-keeping requirements of Collaborative tools activities?
<--- Score
20. How do you hand over Collaborative tools context?
<--- Score
21. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
22. How do you build the right business case?
<--- Score
23. What scope to assess?
<--- Score
24. What baselines are required to be defined and managed?
<--- Score
25. What scope do you want your strategy to cover?
<--- Score
26. Does the team have regular meetings?
<--- Score
27. Scope of sensitive information?
<--- Score
28. What are the rough order estimates on cost savings/opportunities that Collaborative tools brings?
<--- Score
29. How often are the team meetings?
<--- Score
30. What is a worst-case scenario for losses?
<--- Score
31. How do you keep key subject matter experts in the loop?
<--- Score
32. What sources do you use to gather information for a Collaborative tools study?
<--- Score
33. What is the definition of success?
<--- Score
34. Has the direction changed at all during the course of Collaborative tools? If so, when did it change and why?
<--- Score
35. Is the work to date meeting requirements?
<--- Score
36. What are the Collaborative tools use cases?
<--- Score
37. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
38. Is Collaborative tools currently on schedule according to the plan?
<--- Score
39. How is the team tracking and documenting its work?
<--- Score
40. How do you manage scope?
<--- Score
41. Are there different segments of customers?
<--- Score
42. The political context: who holds power?
<--- Score
43. What are the compelling stakeholder reasons for embarking on Collaborative tools?
<--- Score
44. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
45. Why are you doing Collaborative tools and what is the scope?
<--- Score
46. Who is gathering information?
<--- Score
47. What constraints exist that might impact the team?
<--- Score
48. Are the Collaborative tools requirements complete?
<--- Score
49. What happens if Collaborative tools’s scope changes?
<--- Score
50. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
51. Have all of the relationships been defined properly?
<--- Score
52. What is out-of-scope initially?
<--- Score
53. What defines best in class?
<--- Score
54. Is it clearly defined in and to your organization what you do?
<--- Score
55. If substitutes have been appointed, have they been briefed on the Collaborative tools goals and received regular communications as to the progress to date?
<--- Score
56. Are improvement team members fully trained on Collaborative tools?
<--- Score
57. Are resources adequate for the scope?
<--- Score
58. What are the core elements of the Collaborative tools business case?
<--- Score
59. 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
60. What is the definition of Collaborative tools excellence?
<--- Score
61. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
62. What information do you gather?
<--- Score
63. What key stakeholder process output measure(s) does Collaborative tools leverage and how?
<--- Score
64. Are audit criteria, scope, frequency and methods defined?
<--- Score
65. Where can you gather more information?
<--- Score
66. What Collaborative tools requirements should be gathered?
<--- Score
67. Is full participation by members in regularly held team meetings guaranteed?
<--- Score
68. Are roles and responsibilities formally defined?
<--- Score
69. Is there a Collaborative tools management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and