18. How will the Expert Software team and the group measure complete success of Expert Software?
<--- Score
19. What are the tasks and definitions?
<--- Score
20. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
21. What are the compelling stakeholder reasons for embarking on Expert Software?
<--- Score
22. Is the Expert Software scope complete and appropriately sized?
<--- Score
23. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
24. What is the worst case scenario?
<--- Score
25. Has/have the customer(s) been identified?
<--- Score
26. Has a Expert Software requirement not been met?
<--- Score
27. Do you have a Expert Software success story or case study ready to tell and share?
<--- Score
28. Are all requirements met?
<--- Score
29. Have all basic functions of Expert Software been defined?
<--- Score
30. Is there a clear Expert Software case definition?
<--- Score
31. Is there any additional Expert Software definition of success?
<--- Score
32. 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
33. What are the Expert Software tasks and definitions?
<--- Score
34. What is out of scope?
<--- Score
35. How and when will the baselines be defined?
<--- Score
36. Are accountability and ownership for Expert Software clearly defined?
<--- Score
37. What are (control) requirements for Expert Software Information?
<--- Score
38. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
39. How do you gather requirements?
<--- Score
40. Who are the Expert Software improvement team members, including Management Leads and Coaches?
<--- Score
41. How do you hand over Expert Software context?
<--- Score
42. Who is gathering information?
<--- Score
43. Has a team charter been developed and communicated?
<--- Score
44. Has the direction changed at all during the course of Expert Software? If so, when did it change and why?
<--- Score
45. Is special Expert Software user knowledge required?
<--- Score
46. If substitutes have been appointed, have they been briefed on the Expert Software goals and received regular communications as to the progress to date?
<--- Score
47. Are required metrics defined, what are they?
<--- Score
48. What is in the scope and what is not in scope?
<--- Score
49. What is the definition of success?
<--- Score
50. How did the Expert Software manager receive input to the development of a Expert Software improvement plan and the estimated completion dates/times of each activity?
<--- Score
51. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
52. What are the rough order estimates on cost savings/opportunities that Expert Software brings?
<--- Score
53. What is out-of-scope initially?
<--- Score
54. When is the estimated completion date?
<--- Score
55. Have specific policy objectives been defined?
<--- Score
56. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
57. What intelligence can you gather?
<--- Score
58. Are audit criteria, scope, frequency and methods defined?
<--- Score
59. How have you defined all Expert Software requirements first?
<--- Score
60. What is in scope?
<--- Score
61. Is the Expert Software scope manageable?
<--- Score
62.
