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
