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