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.
