Is Software as a secure service required?
<--- Score
52. Are stakeholder processes mapped?
<--- Score
53. Is the Software as a secure service scope complete and appropriately sized?
<--- Score
54. Is scope creep really all bad news?
<--- Score
55. Who are the Software as a secure service improvement team members, including Management Leads and Coaches?
<--- Score
56. What key stakeholder process output measure(s) does Software as a secure service leverage and how?
<--- Score
57. Are the Software as a secure service requirements complete?
<--- Score
58. Is the team equipped with available and reliable resources?
<--- Score
59. How do you think the partners involved in Software as a secure service would have defined success?
<--- Score
60. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
61. Is Software as a secure service currently on schedule according to the plan?
<--- Score
62. Is the work to date meeting requirements?
<--- Score
63. The political context: who holds power?
<--- Score
64. Have all basic functions of Software as a secure service been defined?
<--- Score
65. What is the definition of Software as a secure service excellence?
<--- Score
66. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
67. What was the context?
<--- Score
68. Is the team formed and are team leaders (Coaches and Management Leads) assigned?
<--- Score
69. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
70. Is there a clear Software as a secure service case definition?
<--- Score
71. What would be the goal or target for a Software as a secure service’s improvement team?
<--- Score
72. What is out-of-scope initially?
<--- Score
73. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
74. How do you keep key subject matter experts in the loop?
<--- Score
75. What are the requirements for audit information?
<--- Score
76. What are the record-keeping requirements of Software as a secure service activities?
<--- Score
77. Scope of sensitive information?
<--- Score
78. Do you all define Software as a secure service in the same way?
<--- Score
79. Are improvement team members fully trained on Software as a secure service?
<--- Score
80. How do you manage scope?
<--- Score
81. 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
82. Do you have a Software as a secure service success story or case study ready to tell and share?
<--- Score
83. What sort of initial information to gather?
<--- Score
84. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
85. How do you manage unclear Software as a secure service requirements?
<--- Score
86. Who is gathering information?
<--- Score
87. 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
88. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
89. How do you gather requirements?
<--- Score
90. What scope do you want your strategy to cover?
<--- Score
91. How would you define Software as a secure service leadership?
<--- Score
92. What is in scope?
<--- Score
93. Who is gathering Software as a secure service information?
<--- Score
94. How did the Software as a secure service manager receive input to the development of a Software as a secure service improvement plan and the estimated completion dates/times of each activity?
<---
