Читать книгу On Demand Software A Complete Guide - 2020 Edition - Gerardus Blokdyk - Страница 8

Оглавление

CRITERION #2: DEFINE:

INTENT: Formulate the stakeholder problem. Define the problem, needs and objectives.

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

5 Strongly Agree

4 Agree

3 Neutral

2 Disagree

1 Strongly Disagree

1. What are the requirements for audit information?

<--- Score

2. Is there a clear On-demand software case definition?

<--- Score

3. What is out of scope?

<--- Score

4. What gets examined?

<--- Score

5. What is in scope?

<--- Score

6. Is data collected and displayed to better understand customer(s) critical needs and requirements.

<--- Score

7. What On-demand software services do you require?

<--- Score

8. How did the On-demand software manager receive input to the development of a On-demand software improvement plan and the estimated completion dates/times of each activity?

<--- Score

9. What is the context?

<--- Score

10. How do you manage scope?

<--- Score

11. How and when will the baselines be defined?

<--- Score

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

<--- Score

13. How do you manage unclear On-demand software requirements?

<--- Score

14. Has your scope been defined?

<--- Score

15. How often are the team meetings?

<--- Score

16. In what way can you redefine the criteria of choice clients have in your category in your favor?

<--- Score

17. What happens if On-demand software’s scope changes?

<--- Score

18. Is the work to date meeting requirements?

<--- Score

19. Why are you doing On-demand software and what is the scope?

<--- Score

20. Are task requirements clearly defined?

<--- Score

21. Have the customer needs been translated into specific, measurable requirements? How?

<--- Score

22. What are the rough order estimates on cost savings/opportunities that On-demand software brings?

<--- Score

23. How do you manage changes in On-demand software requirements?

<--- Score

24. Are there different segments of customers?

<--- Score

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

<--- Score

26. What is in the scope and what is not in scope?

<--- Score

27. What constraints exist that might impact the team?

<--- Score

28. What information should you gather?

<--- Score

29. Do you have a On-demand software success story or case study ready to tell and share?

<--- Score

30. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?

<--- Score

31. Has a On-demand software requirement not been met?

<--- Score

32. Has the direction changed at all during the course of On-demand software? If so, when did it change and why?

<--- Score

33. Is there a On-demand software management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?

<--- Score

34. What information do you gather?

<--- Score

35. How does the On-demand software manager ensure against scope creep?

<--- Score

36. Are customer(s) identified and segmented according to their different needs and requirements?

<--- Score

37. What intelligence can you gather?

<--- Score

38. What is the scope of the On-demand software effort?

<--- Score

39. When are meeting minutes sent out? Who is on the distribution list?

<--- Score

40. What is the scope of On-demand software?

<--- Score

41. The political context: who holds power?

<--- Score

42. What is the worst case scenario?

<--- Score

43. What specifically is the problem? Where does it occur? When does it occur? What is its extent?

<--- Score

44. How do you think the partners involved in On-demand software would have defined success?

<--- Score

45. If substitutes have been appointed, have they been briefed on the On-demand software goals and received regular communications as to the progress to date?

<--- Score

46. Is the current ‘as is’ process being followed? If not, what are the discrepancies?

<--- Score

47. When is the estimated completion date?

<--- Score

48. What are the On-demand software tasks and definitions?

<--- Score

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

<--- Score

50. Will team members regularly document their On-demand software work?

<--- Score

51. What are the core elements of the On-demand software business case?

<--- Score

52. Is it clearly defined in and to your organization what you do?

<--- Score

53. Are approval levels defined for contracts and supplements to contracts?

<--- Score

54. Will team members perform On-demand software work when assigned and in a timely fashion?

<--- Score

55. Is On-demand software linked to key stakeholder goals and objectives?

<--- Score

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

<--- Score

57. Is On-demand software currently on schedule according to the plan?

<--- Score

58. Are the On-demand software requirements testable?

<--- Score

59. Has a project plan, Gantt chart, or similar been developed/completed?

<--- Score

60. Are different versions of process maps needed to account for the different types of inputs?

<--- Score

61. How do you keep key subject matter experts in the loop?

<--- Score

62. Is the On-demand software scope complete and appropriately sized?

<--- Score

63. What is out-of-scope initially?

<--- Score

64. What is the scope of the On-demand software work?

<--- Score

65. Are all requirements met?

<--- Score

66. Is there any additional On-demand software definition of success?

<--- Score

67. What is a worst-case scenario for losses?

<--- Score

68. Has a high-level ‘as is’ process map been completed, verified and validated?

<--- Score

69. Are required metrics defined, what are they?

<--- Score

70. 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

71. Have all of the relationships been defined properly?

<--- Score

72. How do you gather On-demand software requirements?

<--- Score

73. Does the team have regular meetings?

<--- Score

74. Is scope creep really all bad news?

<--- Score

75. What would be the goal or target for a On-demand software’s improvement team?

<--- Score

76. How do you hand over On-demand software context?

<--- Score

77. What are the tasks and definitions?

<--- Score

78. Are accountability and ownership for On-demand software clearly defined?

<--- Score

79. How do you gather the stories?

<--- Score

80. What key stakeholder process output measure(s) does On-demand software leverage and how?

<--- Score

81. What defines best in class?

<--- Score

82. What sources do you use to gather information for a On-demand software study?

<--- Score

83. How are consistent On-demand software definitions important?

<--- Score

84. What scope do you want your strategy to cover?

<--- Score

85. Has a team charter been developed and communicated?

<--- Score

86. Scope of sensitive information?

<--- Score

87. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?

<--- Score

88. Who is gathering On-demand software information?

<--- Score

89. 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

90. Is the team equipped with available and reliable resources?

<--- Score

91. Who defines (or who defined) the rules and roles?

<--- Score

92. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?

<--- Score

93. How was the ‘as is’ process map developed, reviewed, verified and validated?

<--- Score

94. When is/was the On-demand software start date?

<--- Score

95. How do you gather requirements?

<--- Score

96. How can the value of On-demand software be defined?

<--- Score

97. Is special On-demand software user knowledge required?

<--- Score

98. Who approved the On-demand software scope?

<--- Score

99. Has the On-demand software work been fairly and/or equitably divided and delegated among team members who are qualified and capable to perform the work? Has everyone contributed?

<--- Score

100. What are the compelling stakeholder reasons for embarking on On-demand software?

<--- Score

101. Are roles and responsibilities formally defined?

<--- Score

102. Has everyone on the team, including the team leaders, been properly trained?

<--- Score

103. Do you have organizational privacy requirements?

<--- Score

104. How do you catch On-demand software definition inconsistencies?

<--- Score

105. What are the On-demand software use cases?

<--- Score

106. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?

<--- Score

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

<--- Score

108. Are the On-demand software requirements complete?

<--- Score

109. How do you build the right business case?

<--- Score

110. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?

<--- Score

111. What knowledge or experience is required?

<--- Score

112. What On-demand software requirements should be gathered?

<--- Score

113. Are there any constraints known that bear on the ability to perform On-demand software work? How is the team addressing them?

<--- Score

114. How would you define On-demand software leadership?

<--- Score

115. What critical content must be communicated – who, what, when, where, and how?

<--- Score

116. Is the On-demand software scope manageable?

<--- Score

117. Who are the On-demand software improvement team members, including Management Leads and Coaches?

<--- Score

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

<--- Score

119. Have all basic functions of On-demand software been defined?

<--- Score

120. Are resources adequate for the scope?

<--- Score

121. What are the dynamics of the communication plan?

<--- Score

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

<--- Score

123. Is the improvement team aware of the different versions of a process: what they think it is vs. what it actually is vs. what it should be vs. what it could be?

<--- Score

124. Do you all define On-demand software in the same way?

<--- Score

125. What is the definition of success?

<--- Score

126. How will the On-demand software team and the group measure complete success of On-demand software?

<--- Score

127. What are the record-keeping requirements of On-demand software activities?

<--- Score

128. How will variation in the actual durations of each activity be dealt with to ensure that the expected On-demand software results are met?

<--- Score

129. What are (control) requirements for On-demand software Information?

<--- Score

130. Is there a critical path to deliver On-demand software results?

<--- Score

131. What is the definition of On-demand software excellence?

<--- Score

132. How have you defined all On-demand software requirements first?

<--- Score

133. Will a On-demand software production readiness review be required?

<--- Score

134. Who is gathering information?

<--- Score

135. Where can you gather more information?

<--- 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 On-demand software Index at the beginning of the Self-Assessment.

On Demand Software A Complete Guide - 2020 Edition

Подняться наверх