is on the distribution list?
<--- Score
12. What is in the scope and what is not in scope?
<--- Score
13. Who is gathering information?
<--- Score
14. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
15. Has a System Design Review requirement not been met?
<--- Score
16. Has a team charter been developed and communicated?
<--- Score
17. Is the System Design Review scope manageable?
<--- Score
18. What are the System Design Review use cases?
<--- Score
19. What scope to assess?
<--- Score
20. Is the team formed and are team leaders (Coaches and Management Leads) assigned?
<--- Score
21. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
22. What are the tasks and definitions?
<--- Score
23. Will a System Design Review production readiness review be required?
<--- Score
24. Are roles and responsibilities formally defined?
<--- Score
25. Are team charters developed?
<--- Score
26. What are the compelling stakeholder reasons for embarking on System Design Review?
<--- Score
27. What key stakeholder process output measure(s) does System Design Review leverage and how?
<--- Score
28. Is full participation by members in regularly held team meetings guaranteed?
<--- Score
29. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
30. How do you keep key subject matter experts in the loop?
<--- Score
31. Have all basic functions of System Design Review been defined?
<--- Score
32. How do you gather the stories?
<--- Score
33. Do you have a System Design Review success story or case study ready to tell and share?
<--- Score
34. How does the System Design Review manager ensure against scope creep?
<--- Score
35. What are the core elements of the System Design Review business case?
<--- Score
36. How do you catch System Design Review definition inconsistencies?
<--- Score
37. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
38. Are stakeholder processes mapped?
<--- Score
39. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
40. Is scope creep really all bad news?
<--- Score
41. How will variation in the actual durations of each activity be dealt with to ensure that the expected System Design Review results are met?
<--- Score
42. What is the scope of the System Design Review effort?
<--- Score
43. Will team members perform System Design Review work when assigned and in a timely fashion?
<--- Score
44. What intelligence can you gather?
<--- Score
45. Are there any constraints known that bear on the ability to perform System Design Review work? How is the team addressing them?
<--- Score
46. Are there different segments of customers?
<--- Score
47. Are required metrics defined, what are they?
<--- Score
48. When is/was the System Design Review start date?
<--- Score
49. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
50. Who are the System Design Review improvement team members, including Management Leads and Coaches?
<--- Score
51. Are accountability and ownership for System Design Review clearly defined?
<--- Score
52. What is in scope?
<--- Score
53. The political context: who holds power?
<--- Score
54. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
55. How do you hand over System Design Review
