Читать книгу Information Systems Analysis And Design 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 scope to assess?
<--- Score
2. Has/have the customer(s) been identified?
<--- Score
3. Is the work to date meeting requirements?
<--- Score
4. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
5. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
6. Is it clearly defined in and to your organization what you do?
<--- Score
7. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
8. Are task requirements clearly defined?
<--- Score
9. What is the scope of the Information systems analysis and design effort?
<--- Score
10. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
11. Have all of the relationships been defined properly?
<--- Score
12. What are the rough order estimates on cost savings/opportunities that Information systems analysis and design brings?
<--- Score
13. What are the tasks and definitions?
<--- Score
14. What are the compelling stakeholder reasons for embarking on Information systems analysis and design?
<--- Score
15. What sort of initial information to gather?
<--- Score
16. What is the context?
<--- Score
17. What is the scope?
<--- Score
18. What information should you gather?
<--- Score
19. Does the team have regular meetings?
<--- Score
20. What is the scope of Information systems analysis and design?
<--- Score
21. Is the Information systems analysis and design scope complete and appropriately sized?
<--- Score
22. Are all requirements met?
<--- Score
23. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
24. What are the Information systems analysis and design use cases?
<--- Score
25. What are (control) requirements for Information systems analysis and design Information?
<--- Score
26. Has the direction changed at all during the course of Information systems analysis and design? If so, when did it change and why?
<--- Score
27. Has a team charter been developed and communicated?
<--- Score
28. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
29. What Information systems analysis and design services do you require?
<--- Score
30. Have all basic functions of Information systems analysis and design been defined?
<--- Score
31. What Information systems analysis and design requirements should be gathered?
<--- Score
32. Will a Information systems analysis and design production readiness review be required?
<--- Score
33. What happens if Information systems analysis and design’s scope changes?
<--- Score
34. How and when will the baselines be defined?
<--- Score
35. What is a worst-case scenario for losses?
<--- Score
36. How do you manage unclear Information systems analysis and design requirements?
<--- Score
37. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
38. Are the Information systems analysis and design requirements testable?
<--- Score
39. Have specific policy objectives been defined?
<--- Score
40. What is out-of-scope initially?
<--- Score
41. What are the dynamics of the communication plan?
<--- Score
42. Are there any constraints known that bear on the ability to perform Information systems analysis and design work? How is the team addressing them?
<--- Score
43. What is the worst case scenario?
<--- Score
44. What system do you use for gathering Information systems analysis and design information?
<--- Score
45. Do you all define Information systems analysis and design in the same way?
<--- Score
46. Who are the Information systems analysis and design improvement team members, including Management Leads and Coaches?
<--- Score
47. Scope of sensitive information?
<--- Score
48. 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
49. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
50. What scope do you want your strategy to cover?
<--- Score
51. What is the definition of success?
<--- Score
52. What key stakeholder process output measure(s) does Information systems analysis and design leverage and how?
<--- Score
53. How would you define the culture at your organization, how susceptible is it to Information systems analysis and design changes?
<--- Score
54. How do you keep key subject matter experts in the loop?
<--- Score
55. Is the scope of Information systems analysis and design defined?
<--- Score
56. How will variation in the actual durations of each activity be dealt with to ensure that the expected Information systems analysis and design results are met?
<--- Score
57. How do you think the partners involved in Information systems analysis and design would have defined success?
<--- Score
58. Do you have a Information systems analysis and design success story or case study ready to tell and share?
<--- Score
59. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
60. How is the team tracking and documenting its work?
<--- Score
61. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
62. What would be the goal or target for a Information systems analysis and design’s improvement team?
<--- Score
63. How are consistent Information systems analysis and design definitions important?
<--- Score
64. When is/was the Information systems analysis and design start date?
<--- Score
65. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
66. How does the Information systems analysis and design manager ensure against scope creep?
<--- Score
67. What is in the scope and what is not in scope?
<--- Score
68. Are roles and responsibilities formally defined?
<--- Score
69. What baselines are required to be defined and managed?
<--- Score
70. Is there a Information systems analysis and design management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
71. What knowledge or experience is required?
<--- Score
72. How do you gather the stories?
<--- Score
73. Are approval levels defined for contracts and supplements to contracts?
<--- Score
74. What gets examined?
<--- Score
75. What was the context?
<--- Score
76. Is there any additional Information systems analysis and design definition of success?
<--- Score
77. Has your scope been defined?
<--- Score
78. The political context: who holds power?
<--- Score
79. Is special Information systems analysis and design user knowledge required?
<--- Score
80. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
81. What information do you gather?
<--- Score
82. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
83. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
84. Who is gathering Information systems analysis and design information?
<--- Score
85. Is scope creep really all bad news?
<--- Score
86. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
87. How would you define Information systems analysis and design leadership?
<--- Score
88. Is there a clear Information systems analysis and design case definition?
<--- Score
89. How will the Information systems analysis and design team and the group measure complete success of Information systems analysis and design?
<--- Score
90. Are accountability and ownership for Information systems analysis and design clearly defined?
<--- Score
91. What critical content must be communicated – who, what, when, where, and how?
<--- Score
92. What defines best in class?
<--- Score
93. 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
94. Is Information systems analysis and design required?
<--- Score
95. Is the Information systems analysis and design scope manageable?
<--- Score
96. What constraints exist that might impact the team?
<--- Score
97. How have you defined all Information systems analysis and design requirements first?
<--- Score
98. How do you gather requirements?
<--- Score
99. If substitutes have been appointed, have they been briefed on the Information systems analysis and design goals and received regular communications as to the progress to date?
<--- Score
100. What customer feedback methods were used to solicit their input?
<--- Score
101. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
102. Is there a critical path to deliver Information systems analysis and design results?
<--- Score
103. What are the Information systems analysis and design tasks and definitions?
<--- Score
104. Does the scope remain the same?
<--- Score
105. Has the Information systems analysis and design 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
106. How can the value of Information systems analysis and design be defined?
<--- Score
107. How do you manage changes in Information systems analysis and design requirements?
<--- Score
108. Are there different segments of customers?
<--- Score
109. 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
110. When is the estimated completion date?
<--- Score
111. How do you manage scope?
<--- Score
112. How often are the team meetings?
<--- Score
113. What sources do you use to gather information for a Information systems analysis and design study?
<--- Score
114. What are the requirements for audit information?
<--- Score
115. Is Information systems analysis and design currently on schedule according to the plan?
<--- Score
116. What is the definition of Information systems analysis and design excellence?
<--- Score
117. Are audit criteria, scope, frequency and methods defined?
<--- Score
118. How do you hand over Information systems analysis and design context?
<--- Score
119. What are the core elements of the Information systems analysis and design business case?
<--- Score
120. How did the Information systems analysis and design manager receive input to the development of a Information systems analysis and design improvement plan and the estimated completion dates/times of each activity?
<--- Score
121. How do you build the right business case?
<--- Score
122. What is the scope of the Information systems analysis and design work?
<--- Score
123. Is Information systems analysis and design linked to key stakeholder goals and objectives?
<--- Score
124. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
125. Why are you doing Information systems analysis and design and what is the scope?
<--- Score
126. What are the record-keeping requirements of Information systems analysis and design activities?
<--- Score
127. What intelligence can you gather?
<--- Score
128. What is out of scope?
<--- Score
129. How do you catch Information systems analysis and design definition inconsistencies?
<--- Score
130. Are resources adequate for the scope?
<--- Score
131. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
132. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
133. Who defines (or who defined) the rules and roles?
<--- Score
134. Has a Information systems analysis and design requirement not been met?
<--- Score
135. Are the Information systems analysis and design requirements complete?
<--- 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 Information systems analysis and design Index at the beginning of the Self-Assessment.
