Скачать книгу

definitions important?

      <--- Score

      115. What intelligence can you gather?

      <--- Score

      116. Are all requirements met?

      <--- Score

      117. How and when will the baselines be defined?

      <--- Score

      118. Who approved the Software test engineering scope?

      <--- Score

      119. Is the work to date meeting requirements?

      <--- Score

      120. What are the core elements of the Software test engineering business case?

      <--- Score

      121. What information do you gather?

      <--- Score

      122. Has everyone on the team, including the team leaders, been properly trained?

      <--- Score

      123. Are different versions of process maps needed to account for the different types of inputs?

      <--- Score

      124. What is in the scope and what is not in scope?

      <--- Score

      125. How did the Software test engineering manager receive input to the development of a Software test engineering improvement plan and the estimated completion dates/times of each activity?

      <--- Score

      126. Is the scope of Software test engineering defined?

      <--- Score

      127. Who defines (or who defined) the rules and roles?

      <--- Score

      128. What are the dynamics of the communication plan?

      <--- Score

      129. Are task requirements clearly defined?

      <--- Score

      130. How would you define Software test engineering leadership?

      <--- Score

      131. Where can you gather more information?

      <--- Score

      132. Has a high-level ‘as is’ process map been completed, verified and validated?

      <--- Score

      133. What constraints exist that might impact the team?

      <--- Score

      134. What Software test engineering services do you require?

      <--- Score

      135. Does the scope remain the same?

      <--- Score

      136. Is Software test engineering linked to key stakeholder goals and objectives?

      <--- Score

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

      <--- 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 Software test engineering Index at the beginning of the Self-Assessment.

      CRITERION #3: MEASURE:

      INTENT: Gather the correct data. Measure the current performance and evolution of the situation.

      In my belief, the answer to this question is clearly defined:

      5 Strongly Agree

      4 Agree

      3 Neutral

      2 Disagree

      1 Strongly Disagree

      1. Is the solution cost-effective?

      <--- Score

      2. At what cost?

      <--- Score

      3. How is progress measured?

      <--- Score

      4. What causes innovation to fail or succeed in your organization?

      <--- Score

      5. What are the costs and benefits?

      <--- Score

      6. How will your organization measure success?

      <--- Score

      7. Why a Software test engineering focus?

      <--- Score

      8. What is an unallowable cost?

      <--- Score

      9. How do you verify the authenticity of the data and information used?

      <--- Score

      10. What causes investor action?

      <--- Score

      11. What are the types and number of measures to use?

      <--- Score

      12. What are the operational costs after Software test engineering deployment?

      <--- Score

      13. Do the benefits outweigh the costs?

      <--- Score

      14. Do you aggressively reward and promote the people who have the biggest impact on creating excellent Software test engineering services/products?

      <--- Score

      15. Which measures and indicators matter?

      <--- Score

      16. How can you manage cost down?

      <--- Score

      17. Are you aware of what could cause a problem?

      <--- Score

      18. How do you aggregate measures across priorities?

      <--- Score

      19. What are the Software test engineering investment costs?

      <--- Score

      20. Where is it measured?

      <--- Score

      21. Is it possible to estimate the impact of unanticipated complexity such as wrong or failed assumptions, feedback, etcetera on proposed reforms?

      <--- Score

      22. How do your measurements capture actionable Software test engineering information for use in exceeding your customers expectations and securing your customers engagement?

      <--- Score

      23. What could cause delays in the schedule?

      <--- Score

      24. How frequently do you track Software test engineering measures?

      <--- Score

      25. What are your key Software test engineering organizational performance measures, including key short and longer-term financial measures?

      <--- Score

      26. Why do the measurements/indicators matter?

      <--- Score

      27. How do you verify and develop ideas and innovations?

      <--- Score

      28. What are the estimated costs of proposed changes?

      <--- Score

      29. Among the Software test engineering product and service cost to be estimated, which is considered hardest to estimate?

Скачать книгу