<--- Score
56. What information should you gather?
<--- Score
57. Will team members regularly document their System Design Review work?
<--- Score
58. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
59. What customer feedback methods were used to solicit their input?
<--- Score
60. Is it clearly defined in and to your organization what you do?
<--- Score
61. How often are the team meetings?
<--- Score
62. Who defines (or who defined) the rules and roles?
<--- Score
63. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
64. Has the System Design Review 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
65. Do you all define System Design Review in the same way?
<--- Score
66. What System Design Review services do you require?
<--- Score
67. Is there a clear System Design Review case definition?
<--- Score
68. When is the estimated completion date?
<--- Score
69. 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
70. What information do you gather?
<--- Score
71. Is special System Design Review user knowledge required?
<--- Score
72. What is the worst case scenario?
<--- Score
73. What is the scope of System Design Review?
<--- Score
74. Do you have organizational privacy requirements?
<--- Score
75. How and when will the baselines be defined?
<--- Score
76. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
77. Who approved the System Design Review scope?
<--- Score
78. How do you gather requirements?
<--- Score
79. What is the definition of success?
<--- Score
80. What is the scope?
<--- Score
81. What is out of scope?
<--- Score
82. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
83. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
84. What defines best in class?
<--- Score
85. Does the team have regular meetings?
<--- Score
86. What is the scope of the System Design Review work?
<--- Score
87. What is the definition of System Design Review excellence?
<--- Score
88. What System Design Review requirements should be gathered?
<--- Score
89. If substitutes have been appointed, have they been briefed on the System Design Review goals and received regular communications as to the progress to date?
<--- Score
90. Is the team equipped with available and reliable resources?
<--- Score
91. Is the scope of System Design Review defined?
<--- Score
92. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
93. Is there any additional System Design Review definition of success?
<--- Score
94. Has the direction changed at all during the course of System Design Review? If so, when did it change and why?
<--- Score
95. Are improvement team members fully trained on System Design Review?
<--- Score
96. Has/have the customer(s) been identified?
<--- Score
97. Have specific policy objectives been defined?
<--- Score
98. What are (control) requirements for System Design Review Information?
<--- Score
99. 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
