.

What is the start point? What is the stop point?

      <--- Score

      63. Are task requirements clearly defined?

      <--- Score

      64. Is there a critical path to deliver Control Systems Engineer results?

      <--- Score

      65. What is out-of-scope initially?

      <--- Score

      66. Have all basic functions of Control Systems Engineer been defined?

      <--- Score

      67. What information do you gather?

      <--- Score

      68. Are resources adequate for the scope?

      <--- Score

      69. Does the team have regular meetings?

      <--- Score

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

      <--- Score

      71. What constraints exist that might impact the team?

      <--- Score

      72. What are the rough order estimates on cost savings/opportunities that Control Systems Engineer brings?

      <--- Score

      73. Are accountability and ownership for Control Systems Engineer clearly defined?

      <--- Score

      74. Do you have organizational privacy requirements?

      <--- Score

      75. Who is gathering Control Systems Engineer information?

      <--- Score

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

      <--- Score

      77. Is the Control Systems Engineer scope manageable?

      <--- Score

      78. What key stakeholder process output measure(s) does Control Systems Engineer leverage and how?

      <--- Score

      79. What is out of scope?

      <--- Score

      80. What are the compelling stakeholder reasons for embarking on Control Systems Engineer?

      <--- Score

      81. When is the estimated completion date?

      <--- Score

      82. How will the Control Systems Engineer team and the group measure complete success of Control Systems Engineer?

      <--- Score

      83. Have specific policy objectives been defined?

      <--- Score

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

      <--- Score

      85. What is the definition of success?

      <--- Score

      86. How have you defined all Control Systems Engineer requirements first?

      <--- Score

      87. When is/was the Control Systems Engineer start date?

      <--- Score

      88. How often are the team meetings?

      <--- Score

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

      <--- Score

      90. Are all requirements met?

      <--- Score

      91. How are consistent Control Systems Engineer definitions important?

      <--- Score

      92. Are roles and responsibilities formally defined?

      <--- Score

      93. How can the value of Control Systems Engineer be defined?

      <--- Score

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

      <--- Score

      95. How do you gather requirements?

      <--- Score

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

      <--- Score

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

      <--- Score

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

      99. How does the Control Systems Engineer manager ensure against scope creep?

      <--- Score

      100. What Control Systems Engineer requirements should be gathered?

      <--- Score

      101. Has your scope been defined?

      <--- Score

      102. What are the tasks and definitions?

      <--- Score

      103. How do you think the partners involved in Control Systems Engineer would have defined success?

      <--- Score

      104. Are there any constraints known that bear on the ability to perform Control Systems Engineer work? How is the team addressing them?

      <--- Score

      105. How did the Control Systems Engineer manager receive input to the development of a Control Systems Engineer improvement plan and the estimated completion dates/times of each activity?

      <--- Score

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

      <--- Score

      107. How was the ‘as is’ process map developed, reviewed, verified and validated?

      <--- Score

      108. How do you manage changes in Control Systems Engineer requirements?

      <--- Score

      109. Are there different segments of customers?

      <--- Score

      110. Has the direction changed at all during the course of Control Systems Engineer? If so, when did it change and why?

      <--- Score

      111. What scope to assess?

      <--- Score

      112. Has a Control Systems Engineer requirement not been met?

      <--- Score

      113. What are the requirements for audit information?

      <--- Score

      114. Have all of the relationships been defined properly?

      <--- Score

      115. What gets examined?

      <--- Score

      116. Does the scope remain the same?

      <--- Score

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

      <--- Score

      118. The political context: who holds power?