Читать книгу Software Reliability A Complete Guide - 2020 Edition - Gerardus Blokdyk - Страница 7

CRITERION #1: RECOGNIZE

INTENT: Be aware of the need for change. Recognize that there is an unfavorable variation, problem or symptom.

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

5 Strongly Agree

4 Agree

3 Neutral

2 Disagree

1 Strongly Disagree

1. Where do you need to exercise leadership?

<--- Score

2. What do employees need in the short term?

<--- Score

3. Will new equipment/products be required to facilitate Software reliability delivery, for example is new software needed?

<--- Score

4. How do you assess your Software reliability workforce capability and capacity needs, including skills, competencies, and staffing levels?

<--- Score

5. What needs to be done?

<--- Score

6. Do you need to avoid or amend any Software reliability activities?

<--- Score

7. Are there regulatory / compliance issues?

<--- Score

8. How does it fit into your organizational needs and tasks?

<--- Score

9. What are the stakeholder objectives to be achieved with Software reliability?

<--- Score

10. How many trainings, in total, are needed?

<--- Score

11. What vendors make products that address the Software reliability needs?

<--- Score

12. Think about the people you identified for your Software reliability project and the project responsibilities you would assign to them, what kind of training do you think they would need to perform these responsibilities effectively?

<--- Score

13. What is the extent or complexity of the Software reliability problem?

<--- Score

14. Are there Software reliability problems defined?

<--- Score

15. How are you going to measure success?

<--- Score

16. Would you recognize a threat from the inside?

<--- Score

17. Who are your key stakeholders who need to sign off?

<--- Score

18. Are there recognized Software reliability problems?

<--- Score

19. Do you have/need 24-hour access to key personnel?

<--- Score

20. Looking at each person individually – does every one have the qualities which are needed to work in this group?

<--- Score

21. How can auditing be a preventative security measure?

<--- Score

22. What should be considered when identifying available resources, constraints, and deadlines?

<--- Score

23. Will Software reliability deliverables need to be tested and, if so, by whom?

<--- Score

24. What Software reliability capabilities do you need?

<--- Score

25. What is the Software reliability problem definition? What do you need to resolve?

<--- Score

26. Will a response program recognize when a crisis occurs and provide some level of response?

<--- Score

27. What are the minority interests and what amount of minority interests can be recognized?

<--- Score

28. What Software reliability coordination do you need?

<--- Score

29. Have you identified your Software reliability key performance indicators?

<--- Score

30. What are the expected benefits of Software reliability to the stakeholder?

<--- Score

31. What training and capacity building actions are needed to implement proposed reforms?

<--- Score

32. Where is training needed?

<--- Score

33. As a sponsor, customer or management, how important is it to meet goals, objectives?

<--- Score

34. Can management personnel recognize the monetary benefit of Software reliability?

<--- Score

35. What activities does the governance board need to consider?

<--- Score

36. How do you recognize an Software reliability objection?

<--- Score

37. How are the Software reliability’s objectives aligned to the group’s overall stakeholder strategy?

<--- Score

38. What Software reliability events should you attend?

<--- Score

39. What situation(s) led to this Software reliability Self Assessment?

<--- Score

40. What information do users need?

<--- Score

41. Which issues are too important to ignore?

<--- Score

42. What problems are you facing and how do you consider Software reliability will circumvent those obstacles?

<--- Score

43. Are your goals realistic? Do you need to redefine your problem? Perhaps the problem has changed or maybe you have reached your goal and need to set a new one?

<--- Score

44. Are controls defined to recognize and contain problems?

<--- Score

45. What does Software reliability success mean to the stakeholders?

<--- Score

46. Who else hopes to benefit from it?

<--- Score

47. Are there any specific expectations or concerns about the Software reliability team, Software reliability itself?

<--- Score

48. Did you miss any major Software reliability issues?

<--- Score

49. How are training requirements identified?

<--- Score

50. Are losses recognized in a timely manner?

<--- Score

51. To what extent does each concerned units management team recognize Software reliability as an effective investment?

<--- Score

52. How much are sponsors, customers, partners, stakeholders involved in Software reliability? In other words, what are the risks, if Software reliability does not deliver successfully?

<--- Score

53. When a Software reliability manager recognizes a problem, what options are available?

<--- Score

54. How do you identify subcontractor relationships?

<--- Score

55. Is it needed?

<--- Score

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.