Скачать книгу

work? How is the team addressing them?

      <--- Score

      114. What information should you gather?

      <--- Score

      115. Are required metrics defined, what are they?

      <--- Score

      116. What knowledge or experience is required?

      <--- Score

      117. How can the value of Software as a secure service be defined?

      <--- Score

      118. What baselines are required to be defined and managed?

      <--- Score

      119. What are the core elements of the Software as a secure service business case?

      <--- Score

      120. Does the scope remain the same?

      <--- Score

      121. Are audit criteria, scope, frequency and methods defined?

      <--- Score

      122. If substitutes have been appointed, have they been briefed on the Software as a secure service goals and received regular communications as to the progress to date?

      <--- Score

      123. Are roles and responsibilities formally defined?

      <--- Score

      124. Is the scope of Software as a secure service defined?

      <--- Score

      125. When is/was the Software as a secure service start date?

      <--- Score

      126. Will a Software as a secure service production readiness review be required?

      <--- Score

      127. How do you hand over Software as a secure service context?

      <--- Score

      128. How is the team tracking and documenting its work?

      <--- Score

      129. How do you gather the stories?

      <--- Score

      130. How have you defined all Software as a secure service requirements first?

      <--- Score

      131. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?

      <--- Score

      132. What system do you use for gathering Software as a secure service information?

      <--- Score

      133. What is the scope of the Software as a secure service effort?

      <--- Score

      134. Are task requirements clearly defined?

      <--- Score

      135. What customer feedback methods were used to solicit their input?

      <--- Score

      136. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?

      <--- Score

      137. How would you define the culture at your organization, how susceptible is it to Software as a secure service changes?

      <--- Score

      138. Has/have the customer(s) been identified?

      <--- Score

      139. What Software as a secure service services do you require?

      <--- Score

      140. What are the dynamics of the communication plan?

      <--- Score

      141. How does the Software as a secure service manager ensure against scope creep?

      <--- Score

      Add up total points for this section: _____ = Total points for this section

      Divided by: ______ (number of statements answered) = ______ Average score for this section

      Transfer your score to the Software as a secure service Index at the beginning of the Self-Assessment.

      CRITERION #3: MEASURE:

      INTENT: Gather the correct data. Measure the current performance and evolution of the situation.

      In my belief, the answer to this question is clearly defined:

      5 Strongly Agree

      4 Agree

      3 Neutral

      2 Disagree

      1 Strongly Disagree

      1. Which measures and indicators matter?

      <--- Score

      2. What measurements are being captured?

      <--- Score

      3. Where is the cost?

      <--- Score

      4. What is the total cost related to deploying Software as a secure service, including any consulting or professional services?

      <--- Score

      5. What are the costs and benefits?

      <--- Score

      6. Do you have any cost Software as a secure service limitation requirements?

      <--- Score

      7. What is an unallowable cost?

      <--- Score

      8. What are hidden Software as a secure service quality costs?

      <--- Score

      9. Do you have an issue in getting priority?

      <--- Score

      10. How is the value delivered by Software as a secure service being measured?

      <--- Score

      11. Is there an opportunity to verify requirements?

      <--- Score

      12. What are your primary costs, revenues, assets?

      <--- Score

      13. Are Software as a secure service vulnerabilities categorized and prioritized?

      <--- Score

      14. What are the costs of reform?

      <--- Score

      15. What are the strategic priorities for this year?

      <--- Score

      16. What are the estimated costs of proposed changes?

      <--- Score

      17. What causes extra work or rework?

      <--- Score

      18. What is measured? Why?

      <--- Score

      19. What is the Software as a secure service business impact?

      <--- Score

      20. What are your customers expectations and measures?

      <--- Score

      21. Has a cost center been established?

      <--- Score

      22. What are you verifying?

      <--- Score

      23. What users will be impacted?

      <--- Score

      24. Are missed Software as a secure service opportunities costing your organization money?

      <---

Скачать книгу