Who defines (or who defined) the rules and roles?
<--- Score
15. Will team members regularly document their Systems assurance work?
<--- Score
16. Has/have the customer(s) been identified?
<--- Score
17. Do you all define Systems assurance in the same way?
<--- Score
18. How can the value of Systems assurance be defined?
<--- Score
19. Are there different segments of customers?
<--- Score
20. What constraints exist that might impact the team?
<--- Score
21. Are improvement team members fully trained on Systems assurance?
<--- Score
22. Is the team sponsored by a champion or stakeholder leader?
<--- Score
23. Is special Systems assurance user knowledge required?
<--- Score
24. How would you define Systems assurance leadership?
<--- Score
25. If substitutes have been appointed, have they been briefed on the Systems assurance goals and received regular communications as to the progress to date?
<--- Score
26. How and when will the baselines be defined?
<--- Score
27. Is Systems assurance required?
<--- Score
28. When is the estimated completion date?
<--- Score
29. Is the scope of Systems assurance defined?
<--- Score
30. Are audit criteria, scope, frequency and methods defined?
<--- Score
31. Are required metrics defined, what are they?
<--- Score
32. What is in scope?
<--- Score
33. How will variation in the actual durations of each activity be dealt with to ensure that the expected Systems assurance results are met?
<--- Score
34. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
35. Are the Systems assurance requirements testable?
<--- Score
36. How are consistent Systems assurance definitions important?
<--- Score
37. What scope to assess?
<--- Score
38. What intelligence can you gather?
<--- Score
39. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
40. What are the requirements for audit information?
<--- Score
41. Are the Systems assurance requirements complete?
<--- Score
42. What scope do you want your strategy to cover?
<--- Score
43. Are resources adequate for the scope?
<--- Score
44. Who are the Systems assurance improvement team members, including Management Leads and Coaches?
<--- Score
45. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
46. Is scope creep really all bad news?
<--- Score
47. What was the context?
<--- Score
48. What is the scope of Systems assurance?
<--- Score
49. What is the scope?
<--- Score
50. The political context: who holds power?
<--- Score
51. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
52. Who is gathering information?
<--- Score
53. Does the scope remain the same?
<--- Score
54. Is full participation by members in regularly held team meetings guaranteed?
<--- Score
55. What happens if Systems assurance’s scope changes?
<--- Score
56. Who approved the Systems assurance scope?
<--- Score
57. What information do you gather?
<--- Score
58. Will team members perform Systems assurance work when assigned and in a timely fashion?
<--- Score
59. What is in the scope and what is not in scope?
<--- Score
60.
