Читать книгу Systems Architecture Service A Complete Guide - 2020 Edition - Gerardus Blokdyk - Страница 8
ОглавлениеCRITERION #2: DEFINE:
INTENT: Formulate the stakeholder problem. Define the problem, needs and objectives.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
1. How do you hand over Systems Architecture Service context?
<--- Score
2. When is the estimated completion date?
<--- Score
3. Who are the Systems Architecture Service improvement team members, including Management Leads and Coaches?
<--- Score
4. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
5. Are the Systems Architecture Service requirements testable?
<--- Score
6. Has/have the customer(s) been identified?
<--- Score
7. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
8. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
9. How do you build the right business case?
<--- Score
10. What scope do you want your strategy to cover?
<--- Score
11. Has a team charter been developed and communicated?
<--- Score
12. Who approved the Systems Architecture Service scope?
<--- Score
13. What is the context?
<--- Score
14. How is the team tracking and documenting its work?
<--- Score
15. What would be the goal or target for a Systems Architecture Service’s improvement team?
<--- Score
16. How do you manage unclear Systems Architecture Service requirements?
<--- Score
17. What are the rough order estimates on cost savings/opportunities that Systems Architecture Service brings?
<--- Score
18. How do you catch Systems Architecture Service definition inconsistencies?
<--- Score
19. How will the Systems Architecture Service team and the group measure complete success of Systems Architecture Service?
<--- Score
20. Are there different segments of customers?
<--- Score
21. Does the team have regular meetings?
<--- Score
22. What was the context?
<--- Score
23. What are the tasks and definitions?
<--- Score
24. Is there a clear Systems Architecture Service case definition?
<--- Score
25. Is there any additional Systems Architecture Service definition of success?
<--- Score
26. How can the value of Systems Architecture Service be defined?
<--- Score
27. Do you have a Systems Architecture Service success story or case study ready to tell and share?
<--- Score
28. Why are you doing Systems Architecture Service and what is the scope?
<--- Score
29. What are the compelling stakeholder reasons for embarking on Systems Architecture Service?
<--- Score
30. Have all of the relationships been defined properly?
<--- Score
31. What customer feedback methods were used to solicit their input?
<--- Score
32. Who is gathering information?
<--- Score
33. How will variation in the actual durations of each activity be dealt with to ensure that the expected Systems Architecture Service results are met?
<--- Score
34. How are consistent Systems Architecture Service definitions important?
<--- Score
35. How do you manage changes in Systems Architecture Service requirements?
<--- Score
36. What are the Systems Architecture Service use cases?
<--- Score
37. Has the Systems Architecture Service 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
38. How do you gather Systems Architecture Service requirements?
<--- Score
39. Are accountability and ownership for Systems Architecture Service clearly defined?
<--- Score
40. Are task requirements clearly defined?
<--- Score
41. How do you gather the stories?
<--- Score
42. Where can you gather more information?
<--- Score
43. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
44. How does the Systems Architecture Service manager ensure against scope creep?
<--- Score
45. What is the scope of Systems Architecture Service?
<--- Score
46. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
47. Who defines (or who defined) the rules and roles?
<--- Score
48. What are the requirements for audit information?
<--- Score
49. Is the team equipped with available and reliable resources?
<--- Score
50. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
51. 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
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 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.
<--- Score
114. What scope to assess?
<--- Score
115. What are the Systems Architecture Service tasks and definitions?
<--- Score
116. 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
117. Is the Systems Architecture Service scope complete and appropriately sized?
<--- Score
118. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
119. What are the record-keeping requirements of Systems Architecture Service activities?
<--- Score
120. Do you have organizational privacy requirements?
<--- Score
121. Who is gathering Systems Architecture Service information?
<--- Score
122. What information should you gather?
<--- Score
123. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
124. How do you gather requirements?
<--- Score
125. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
126. What are (control) requirements for Systems Architecture Service Information?
<--- Score
127. 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
128. Has a Systems Architecture Service requirement not been met?
<--- Score
129. What is the definition of Systems Architecture Service excellence?
<--- Score
130. What knowledge or experience is required?
<--- Score
131. Is there a critical path to deliver Systems Architecture Service results?
<--- Score
132. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
133. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
134. What is in scope?
<--- Score
135. The political context: who holds power?
<--- Score
136. What key stakeholder process output measure(s) does Systems Architecture Service leverage and how?
<--- Score
Add up total points for this section: _____ = Total points for this section
Divided by: ______ (number of statements answered) = ______ Average score for this section
Transfer your score to the Systems Architecture Service Index at the beginning of the Self-Assessment.
