<--- Score
31. Are you dealing with any of the same issues today as yesterday? What can you do about this?
<--- Score
32. For your Systems assurance project, identify and describe the business environment, is there more than one layer to the business environment?
<--- Score
33. Is the quality assurance team identified?
<--- Score
34. Who needs to know about Systems assurance?
<--- Score
35. Who needs what information?
<--- Score
36. Why the need?
<--- Score
37. Consider your own Systems assurance project, what types of organizational problems do you think might be causing or affecting your problem, based on the work done so far?
<--- Score
38. Who needs to know?
<--- Score
39. Where is training needed?
<--- Score
40. What are the stakeholder objectives to be achieved with Systems assurance?
<--- Score
41. Are losses recognized in a timely manner?
<--- Score
42. What should be considered when identifying available resources, constraints, and deadlines?
<--- Score
43. How do you take a forward-looking perspective in identifying Systems assurance research related to market response and models?
<--- Score
44. Are problem definition and motivation clearly presented?
<--- Score
45. What information do users need?
<--- Score
46. What creative shifts do you need to take?
<--- Score
47. Why is this needed?
<--- Score
48. How does it fit into your organizational needs and tasks?
<--- Score
49. What do you need to start doing?
<--- Score
50. How do you recognize an Systems assurance objection?
<--- Score
51. What is the problem and/or vulnerability?
<--- Score
52. Who needs budgets?
<--- Score
53. Who else hopes to benefit from it?
<--- Score
54. Did you miss any major Systems assurance issues?
<--- Score
55. Which issues are too important to ignore?
<--- Score
56. How are the Systems assurance’s objectives aligned to the group’s overall stakeholder strategy?
<--- Score
57. What are the Systems assurance resources needed?
<--- Score
58. What resources or support might you need?
<--- Score
59. What are the expected benefits of Systems assurance to the stakeholder?
<--- Score
60. Whom do you really need or want to serve?
<--- Score
61. How do you assess your Systems assurance workforce capability and capacity needs, including skills, competencies, and staffing levels?
<--- Score
62. Are there recognized Systems assurance problems?
<--- Score
63. Are your goals realistic? Do you need to redefine your problem? Perhaps the problem has changed or maybe you have reached your goal and need to set a new one?
<--- Score
64. Would you recognize a threat from the inside?
<--- Score
65. Do you know what you need to know about Systems assurance?
<--- Score
66. How do you recognize an objection?
<--- Score
67. Will new equipment/products be required to facilitate Systems assurance delivery, for example is new software needed?
<--- Score
68. Looking at each person individually – does every one have the qualities which are needed to work in this group?
<--- Score
69. Are there any revenue recognition issues?
<--- Score
70. How much are sponsors, customers, partners, stakeholders involved in Systems assurance? In other words, what are the risks, if Systems assurance does not deliver successfully?
<--- Score
71. Where do you need to exercise leadership?
<--- Score
72. How do you identify the kinds of information that you will need?
<--- Score
73. Which information does the Systems assurance business case need to include?
<--- Score
74. Will a response program recognize when a crisis occurs and provide some level of response?
<---
