Systems Architecture Service A Complete Guide - 2020 Edition. Gerardus Blokdyk

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 Architecture Service study?

      <--- Score

      95. Do you all define Systems Architecture Service in the same way?

      <--- Score

      96. Are audit criteria, scope, frequency and methods defined?

      <--- Score

      97. When is/was the Systems Architecture Service start date?

      <--- Score

      98. Has a project plan, Gantt chart, or similar been developed/completed?

      <--- Score

      99. Are all requirements met?

      <--- Score

      100. What is the scope of the Systems Architecture Service effort?

      <--- Score

      101. What critical content must be communicated – who, what, when, where, and how?

      <--- Score

      102. Has your scope been defined?

      <--- Score

      103. How and when will the baselines be defined?

      <--- Score

      104. Will a Systems Architecture Service production readiness review be required?

      <--- Score

      105. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?

      <--- Score

      106. How did the Systems Architecture Service manager receive input to the development of a Systems Architecture Service improvement plan and the estimated completion dates/times of each activity?

      <--- Score

      107. What is the definition of success?

      <--- Score

      108. How often are the team meetings?

      <--- Score

      109. Does the scope remain the same?

      <--- Score

      110. How do you manage scope?

      <--- Score

      111. What is the worst case scenario?

      <--- Score

      112. What system do you use for gathering Systems Architecture Service information?

      <--- Score

      113. Is data collected and displayed to better understand customer(s) critical needs and requirements.