Диалог во времени. Жизнь и творчество А.П. Чехова. Отсутствует

      56. What Software reliability problem should be solved?

      <--- Score

      57. Do you recognize Software reliability achievements?

      <--- Score

      58. How do you identify the kinds of information that you will need?

      <--- Score

      59. Are employees recognized or rewarded for performance that demonstrates the highest levels of integrity?

      <--- Score

      60. Who defines the rules in relation to any given issue?

      <--- Score

      61. How do you recognize an objection?

      <--- Score

      62. What prevents you from making the changes you know will make you a more effective Software reliability leader?

      <--- Score

      63. Are there any revenue recognition issues?

      <--- Score

      64. What is the problem or issue?

      <--- Score

      65. Is the quality assurance team identified?

      <--- Score

      66. Is the need for organizational change recognized?

      <--- Score

      67. Who needs what information?

      <--- Score

      68. What needs to stay?

      <--- Score

      69. What is the smallest subset of the problem you can usefully solve?

      <--- Score

      70. Which information does the Software reliability business case need to include?

      <--- Score

      71. Does your organization need more Software reliability education?

      <--- Score

      72. What is the recognized need?

      <--- Score

      73. Are you dealing with any of the same issues today as yesterday? What can you do about this?

      <--- Score

      74. Does the problem have ethical dimensions?

      <--- Score

      75. Who needs budgets?

      <--- Score

      76. Is it clear when you think of the day ahead of you what activities and tasks you need to complete?

      <--- Score

      77. Which needs are not included or involved?

      <--- Score

      78. Why is this needed?

      <--- Score

      79. Who should resolve the Software reliability issues?

      <--- Score

      80. Why the need?

      <--- Score

      81. What would happen if Software reliability weren’t done?

      <--- Score

      82. What are the timeframes required to resolve each of the issues/problems?

      <--- Score

      83. Whom do you really need or want to serve?

      <--- Score

      84. What are your needs in relation to Software reliability skills, labor, equipment, and markets?

      <--- Score

      85. What extra resources will you need?

      <--- Score

      86. What creative shifts do you need to take?

      <--- Score

      87. What resources or support might you need?

      <--- Score

      88. What else needs to be measured?

      <--- Score

      89. Do you know what you need to know about Software reliability?

      <--- Score

      90. Who needs to know?

      <--- Score

      91. For your Software reliability project, identify and describe the business environment, is there more than one layer to the business environment?

      <--- Score

      92. How do you take a forward-looking perspective in identifying Software reliability research related to market response and models?

      <--- Score

      93. Are employees recognized for desired behaviors?

      <--- Score

      94. Who needs to know about Software reliability?

      <--- Score

      95. Consider your own Software reliability project, what types of organizational problems do you think might be causing or affecting your problem, based on the work done so far?

      <--- Score

      96. To what extent would your organization benefit from being recognized as a award recipient?

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

      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. Has a Software reliability requirement not been met?

      <--- Score

      2. How can the value of Software reliability be defined?

      <--- Score

      3. What critical content must be communicated – who, what, when, where, and how?

      <--- Score

      4. What system do you use for gathering Software reliability information?

      <--- Score

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

      <--- Score

      6. Has a team charter been developed and communicated?

      <--- Score

      7. Has the direction changed at all during the course of Software reliability? If so, when did it change and why?

      <--- Score

      8. What intelligence can you gather?

      <--- Score

      9. What is out-of-scope initially?

      <--- Score

      10. How often are the team meetings?

      <--- Score

      11. Is the team equipped with available and reliable resources?

      <---