start point? What is the stop point?
<--- Score
52. How do you keep key subject matter experts in the loop?
<--- Score
53. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
54. Scope of sensitive information?
<--- Score
55. Is the Systems Architecture Service scope manageable?
<--- Score
56. If substitutes have been appointed, have they been briefed on the Systems Architecture Service goals and received regular communications as to the progress to date?
<--- Score
57. Is the scope of Systems Architecture Service defined?
<--- Score
58. Are resources adequate for the scope?
<--- Score
59. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
60. What are the core elements of the Systems Architecture Service business case?
<--- Score
61. Is Systems Architecture Service required?
<--- Score
62. Is special Systems Architecture Service user knowledge required?
<--- Score
63. How would you define Systems Architecture Service leadership?
<--- Score
64. What baselines are required to be defined and managed?
<--- Score
65. What is out of scope?
<--- Score
66. How would you define the culture at your organization, how susceptible is it to Systems Architecture Service changes?
<--- Score
67. Is Systems Architecture Service linked to key stakeholder goals and objectives?
<--- Score
68. Are there any constraints known that bear on the ability to perform Systems Architecture Service work? How is the team addressing them?
<--- Score
69. Is there a Systems Architecture Service management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
70. Have all basic functions of Systems Architecture Service been defined?
<--- Score
71. Have specific policy objectives been defined?
<--- Score
72. What defines best in class?
<--- Score
73. Has the direction changed at all during the course of Systems Architecture Service? If so, when did it change and why?
<--- Score
74. What is a worst-case scenario for losses?
<--- Score
75. What is the scope of the Systems Architecture Service work?
<--- Score
76. What Systems Architecture Service requirements should be gathered?
<--- Score
77. Is it clearly defined in and to your organization what you do?
<--- Score
78. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
79. How do you think the partners involved in Systems Architecture Service would have defined success?
<--- Score
80. How have you defined all Systems Architecture Service requirements first?
<--- Score
81. What intelligence can you gather?
<--- Score
82. What gets examined?
<--- Score
83. What is out-of-scope initially?
<--- Score
84. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
85. Are approval levels defined for contracts and supplements to contracts?
<--- Score
86. Are roles and responsibilities formally defined?
<--- Score
87. What happens if Systems Architecture Service’s scope changes?
<--- Score
88. What are the dynamics of the communication plan?
<--- Score
89. What information do you gather?
<--- Score
90. Is Systems Architecture Service currently on schedule according to the plan?
<--- Score
91. What Systems Architecture Service services do you require?
<--- Score
92. What constraints exist that might impact the team?
<--- Score
93. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
94. What sources do you use to gather information for a Systems
