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?
<--- Score
95. Are approval levels defined for contracts and supplements to contracts?
<--- Score
96. What information do you gather?
<--- Score
97. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
98. How will variation in the actual durations of each activity be dealt with to ensure that the expected Software as a secure service results are met?
<--- Score
99. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
100. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
101. What scope to assess?
<--- Score
102. Has a team charter been developed and communicated?
<--- Score
103. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
104. Who defines (or who defined) the rules and roles?
<--- Score
105. What is the scope of the Software as a secure service work?
<--- Score
106. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
107. What is the scope?
<--- Score
108. What constraints exist that might impact the team?
<--- Score
109. What is the scope of Software as a secure service?
<--- Score
110. What defines best in class?
<--- Score
111. Is there any additional Software as a secure service definition of success?
<--- Score
112. What are the Software as a secure service use cases?
<--- Score
113. Are there any constraints known that bear on the ability to perform Software as a secure