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