substitutes have been appointed, have they been briefed on the Information systems discipline goals and received regular communications as to the progress to date?
<--- Score
49. Is the scope of Information systems discipline defined?
<--- Score
50. What sort of initial information to gather?
<--- Score
51. Is the Information systems discipline scope complete and appropriately sized?
<--- Score
52. What are the tasks and definitions?
<--- Score
53. What key stakeholder process output measure(s) does Information systems discipline leverage and how?
<--- Score
54. How have you defined all Information systems discipline requirements first?
<--- Score
55. Are all requirements met?
<--- Score
56. Does the scope remain the same?
<--- Score
57. Do you have a Information systems discipline success story or case study ready to tell and share?
<--- Score
58. What is the scope of Information systems discipline?
<--- Score
59. What gets examined?
<--- Score
60. The political context: who holds power?
<--- Score
61. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
62. Scope of sensitive information?
<--- Score
63. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
64. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
65. Who defines (or who defined) the rules and roles?
<--- Score
66. What are (control) requirements for Information systems discipline Information?
<--- Score
67. Why are you doing Information systems discipline and what is the scope?
<--- Score
68. What information should you gather?
<--- Score
69. Is it clearly defined in and to your organization what you do?
<--- Score
70. What are the rough order estimates on cost savings/opportunities that Information systems discipline brings?
<--- Score
71. Are there any constraints known that bear on the ability to perform Information systems discipline work? How is the team addressing them?
<--- Score
72. Are required metrics defined, what are they?
<--- Score
73. What defines best in class?
<--- Score
74. Who are the Information systems discipline improvement team members, including Management Leads and Coaches?
<--- Score
75. Are roles and responsibilities formally defined?
<--- Score
76. What is the context?
<--- Score
77. Are the Information systems discipline requirements complete?
<--- Score
78. What Information systems discipline requirements should be gathered?
<--- Score
79. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
80. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
81. Is the Information systems discipline scope manageable?
<--- Score
82. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
83. How do you keep key subject matter experts in the loop?
<--- Score
84. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
85. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
86. What scope do you want your strategy to cover?
<--- Score
87. Has a Information systems discipline requirement not been met?
<--- Score
88. How and when will the baselines be defined?
<--- Score
89. How do you manage unclear Information systems discipline requirements?
<--- Score
90. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
91. When are meeting minutes sent out? Who is on the distribution list?
