Systems Assurance A Complete Guide - 2020 Edition. Gerardus Blokdyk
Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
71. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
72. Is Systems assurance linked to key stakeholder goals and objectives?
<--- Score
73. How do you manage scope?
<--- Score
74. Is there a critical path to deliver Systems assurance results?
<--- Score
75. Are task requirements clearly defined?
<--- Score
76. Who is gathering Systems assurance information?
<--- Score
77. Has the direction changed at all during the course of Systems assurance? If so, when did it change and why?
<--- Score
78. What information should you gather?
<--- Score
79. What are the tasks and definitions?
<--- Score
80. Where can you gather more information?
<--- Score
81. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
82. Are stakeholder processes mapped?
<--- Score
83. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
84. How will the Systems assurance team and the group measure complete success of Systems assurance?
<--- Score
85. What are the Systems assurance tasks and definitions?
<--- Score
86. Have all basic functions of Systems assurance been defined?
<--- Score
87. How do you gather the stories?
<--- Score
88. Is the team equipped with available and reliable resources?
<--- Score
89. What gets examined?
<--- Score
90. How did the Systems assurance manager receive input to the development of a Systems assurance improvement plan and the estimated completion dates/times of each activity?
<--- Score
91. Is the team formed and are team leaders (Coaches and Management Leads) assigned?
<--- Score
92. Are team charters developed?
<--- Score
93. Is the Systems assurance scope complete and appropriately sized?
<--- Score
94. How do you catch Systems assurance definition inconsistencies?
<--- Score
95. How do you think the partners involved in Systems assurance would have defined success?
<--- Score
96. Have specific policy objectives been defined?
<--- Score
97. Is the Systems assurance scope manageable?
<--- Score
98. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
99. Does the team have regular meetings?
<--- Score
100. Has the Systems assurance 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
101. Is there a Systems assurance management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
102. Has a team charter been developed and communicated?
<--- Score
103. What critical content must be communicated – who, what, when, where, and how?
<--- Score
104. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
105. How do you manage unclear Systems assurance requirements?
<--- Score
106. Are accountability and ownership for Systems assurance clearly defined?
<--- Score
107. Are all requirements met?
<--- Score
108. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
109. What is the worst case scenario?
<--- Score
110. 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
111. Do you have organizational privacy requirements?
<--- Score
112. How have you defined all Systems assurance requirements first?
<--- Score
113. Is there any additional Systems assurance definition of success?
<--- Score
114. Is the work to date meeting requirements?
<--- Score
115. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
116. What Systems assurance requirements should be gathered?
<--- Score
117. Has a Systems assurance requirement not been met?
<--- Score
118. What is a worst-case scenario for losses?
<--- Score
119. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
120. What would be the goal or target for a Systems assurance’s improvement team?
<--- Score
121. What is the definition of success?
<--- Score
122. What are the compelling stakeholder reasons for embarking on Systems assurance?
<--- Score
123. 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
124.