Читать книгу Call Data Record 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. How was the ‘as is’ process map developed, reviewed, verified and validated?

<--- Score

2. Is the work to date meeting requirements?

<--- Score

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

<--- Score

4. Is there a clear Call data record case definition?

<--- Score

5. Will team members regularly document their Call data record work?

<--- Score

6. Has the Call data record 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

7. Will team members perform Call data record work when assigned and in a timely fashion?

<--- Score

8. What constraints exist that might impact the team?

<--- Score

9. What knowledge or experience is required?

<--- Score

10. How can the value of Call data record be defined?

<--- Score

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

<--- Score

12. What Call data record requirements should be gathered?

<--- Score

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

<--- Score

14. Has the direction changed at all during the course of Call data record? If so, when did it change and why?

<--- Score

15. Are resources adequate for the scope?

<--- Score

16. Has your scope been defined?

<--- Score

17. How have you defined all Call data record requirements first?

<--- Score

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

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

<--- Score

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

<--- Score

21. What information do you gather?

<--- Score

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

<--- Score

23. What are the rough order estimates on cost savings/opportunities that Call data record brings?

<--- Score

24. How do you hand over Call data record context?

<--- Score

25. Is special Call data record user knowledge required?

<--- Score

26. Is the team formed and are team leaders (Coaches and Management Leads) assigned?

<--- Score

27. How do you manage scope?

<--- Score

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

<--- Score

29. Have all basic functions of Call data record been defined?

<--- Score

30. Is there a Call data record management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?

<--- Score

31. Have all of the relationships been defined properly?

<--- Score

32. What is out-of-scope initially?

<--- Score

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

<--- Score

34. What is the context?

<--- Score

35. What information should you gather?

<--- Score

36. Has a Call data record requirement not been met?

<--- Score

37. Do you all define Call data record in the same way?

<--- Score

38. What scope to assess?

<--- Score

39. What is the definition of success?

<--- Score

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

<--- Score

41. What are the compelling stakeholder reasons for embarking on Call data record?

<--- Score

42. Does the scope remain the same?

<--- Score

43. Who is gathering Call data record information?

<--- Score

44. What is in scope?

<--- Score

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

<--- Score

46. Do you have a Call data record success story or case study ready to tell and share?

<--- Score

47. Are there any constraints known that bear on the ability to perform Call data record work? How is the team addressing them?

<--- Score

48. What would be the goal or target for a Call data record’s improvement team?

<--- Score

49. Are accountability and ownership for Call data record clearly defined?

<--- Score

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

<--- Score

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

<--- Score

52. Why are you doing Call data record and what is the scope?

<--- Score

53. How will variation in the actual durations of each activity be dealt with to ensure that the expected Call data record results are met?

<--- Score

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

<--- Score

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

<--- Score

56. Are there different segments of customers?

<--- Score

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

<--- Score

58. How do you think the partners involved in Call data record would have defined success?

<--- Score

59. What are (control) requirements for Call data record Information?

<--- Score

60. What are the Call data record tasks and definitions?

<--- Score

61. How does the Call data record manager ensure against scope creep?

<--- Score

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

<--- Score

63. Are required metrics defined, what are they?

<--- Score

64. What are the Call data record use cases?

<--- Score

65. Does the team have regular meetings?

<--- Score

66. How and when will the baselines be defined?

<--- Score

67. Is full participation by members in regularly held team meetings guaranteed?

<--- Score

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

<--- Score

69. Is Call data record linked to key stakeholder goals and objectives?

<--- Score

70. Is there any additional Call data record definition of success?

<--- Score

71. When is the estimated completion date?

<--- Score

72. How do you manage changes in Call data record requirements?

<--- Score

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

<--- Score

74. What system do you use for gathering Call data record information?

<--- Score

75. Have specific policy objectives been defined?

<--- Score

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

<--- Score

77. How did the Call data record manager receive input to the development of a Call data record improvement plan and the estimated completion dates/times of each activity?

<--- Score

78. What happens if Call data record’s scope changes?

<--- Score

79. If substitutes have been appointed, have they been briefed on the Call data record goals and received regular communications as to the progress to date?

<--- Score

80. Are task requirements clearly defined?

<--- Score

81. What intelligence can you gather?

<--- Score

82. Who is gathering information?

<--- Score

83. Are the Call data record requirements complete?

<--- Score

84. Are the Call data record requirements testable?

<--- Score

85. What Call data record services do you require?

<--- Score

86. Is there a critical path to deliver Call data record results?

<--- Score

87. Will a Call data record production readiness review be required?

<--- Score

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

<--- Score

89. Are improvement team members fully trained on Call data record?

<--- Score

90. Where can you gather more information?

<--- Score

91. Are all requirements met?

<--- Score

92. What key stakeholder process output measure(s) does Call data record leverage and how?

<--- Score

93. How will the Call data record team and the group measure complete success of Call data record?

<--- Score

94. When is/was the Call data record start date?

<--- Score

95. The political context: who holds power?

<--- Score

96. Has a team charter been developed and communicated?

<--- Score

97. What are the dynamics of the communication plan?

<--- Score

98. How do you manage unclear Call data record requirements?

<--- Score

99. How do you gather requirements?

<--- Score

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

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

<--- Score

102. How often are the team meetings?

<--- Score

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

<--- Score

104. Is the team sponsored by a champion or stakeholder leader?

<--- Score

105. What is the scope of the Call data record effort?

<--- Score

106. What sort of initial information to gather?

<--- Score

107. What is out of scope?

<--- Score

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

<--- Score

109. How are consistent Call data record definitions important?

<--- Score

110. Is the Call data record scope manageable?

<--- Score

111. Who are the Call data record improvement team members, including Management Leads and Coaches?

<--- Score

112. What are the requirements for audit information?

<--- Score

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

<--- Score

114. Is the scope of Call data record defined?

<--- Score

115. Is the Call data record scope complete and appropriately sized?

<--- Score

116. Is Call data record currently on schedule according to the plan?

<--- Score

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

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

<--- Score

119. How would you define Call data record leadership?

<--- Score

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

<--- Score

121. Are roles and responsibilities formally defined?

<--- Score

122. What sources do you use to gather information for a Call data record study?

<--- Score

123. What is the scope of Call data record?

<--- Score

124. What are the tasks and definitions?

<--- Score

125. Do you have organizational privacy requirements?

<--- Score

126. Is Call data record required?

<--- Score

127. Who approved the Call data record scope?

<--- Score

128. What are the record-keeping requirements of Call data record activities?

<--- Score

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

<--- Score

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

<--- Score

131. What is the worst case scenario?

<--- Score

132. What is the scope of the Call data record work?

<--- Score

133. What are the core elements of the Call data record business case?

<--- Score

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

<--- Score

135. What defines best in class?

<--- 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 Call data record changes?

<--- Score

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

<--- Score

139. How do you gather the stories?

<--- Score

140. What was the context?

<--- Score

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

<--- 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 Call data record Index at the beginning of the Self-Assessment.

Call Data Record A Complete Guide - 2020 Edition

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