Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
55. Are there any constraints known that bear on the ability to perform System justification work? How is the team addressing them?
<--- Score
56. Has your scope been defined?
<--- Score
57. Has/have the customer(s) been identified?
<--- Score
58. 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
59. Are roles and responsibilities formally defined?
<--- Score
60. Are audit criteria, scope, frequency and methods defined?
<--- Score
61. Is System justification linked to key stakeholder goals and objectives?
<--- Score
62. How do you catch System justification definition inconsistencies?
<--- Score
63. How do you think the partners involved in System justification would have defined success?
<--- Score
64. 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
65. How do you gather the stories?
<--- Score
66. What scope to assess?
<--- Score
67. What are the compelling stakeholder reasons for embarking on System justification?
<--- Score
68. Do you have a System justification success story or case study ready to tell and share?
<--- Score
69. What is a worst-case scenario for losses?
<--- Score
70. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
71. Are resources adequate for the scope?
<--- Score
72. What scope do you want your strategy to cover?
<--- Score
73. What is in the scope and what is not in scope?
<--- Score
74. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
75. When is/was the System justification start date?
<--- Score
76. Is the System justification scope complete and appropriately sized?
<--- Score
77. What are the System justification tasks and definitions?
<--- Score
78. Has a System justification requirement not been met?
<--- Score
79. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
80. Who is gathering System justification information?
<--- Score
81. What System justification requirements should be gathered?
<--- Score
82. Have all basic functions of System justification been defined?
<--- Score
83. Have specific policy objectives been defined?
<--- Score
84. Are task requirements clearly defined?
<--- Score
85. Will a System justification production readiness review be required?
<--- Score
86. What information do you gather?
<--- Score
87. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
88. Scope of sensitive information?
<--- Score
89. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
90. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
91. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?
<--- Score
92. Who approved the System justification scope?
<--- Score
93. What are the record-keeping requirements of System justification activities?
<--- Score
94. Has the System justification 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
95. What baselines are required to be defined and managed?
<--- Score
96. Is System justification currently on schedule according to the plan?
<--- Score
97.
