Читать книгу Software Test Engineering 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. How do you assess your Software test engineering workforce capability and capacity needs, including skills, competencies, and staffing levels?
<--- Score
2. Who needs to know about Software test engineering?
<--- Score
3. Are employees recognized or rewarded for performance that demonstrates the highest levels of integrity?
<--- Score
4. Are there recognized Software test engineering problems?
<--- Score
5. What needs to stay?
<--- Score
6. Are problem definition and motivation clearly presented?
<--- Score
7. How much are sponsors, customers, partners, stakeholders involved in Software test engineering? In other words, what are the risks, if Software test engineering does not deliver successfully?
<--- Score
8. What information do users need?
<--- Score
9. What are the expected benefits of Software test engineering to the stakeholder?
<--- Score
10. What is the problem or issue?
<--- Score
11. What is the smallest subset of the problem you can usefully solve?
<--- Score
12. Who needs to know?
<--- Score
13. Are there any specific expectations or concerns about the Software test engineering team, Software test engineering itself?
<--- Score
14. What needs to be done?
<--- Score
15. Does the problem have ethical dimensions?
<--- Score
16. How does it fit into your organizational needs and tasks?
<--- Score
17. What does Software test engineering success mean to the stakeholders?
<--- Score
18. What extra resources will you need?
<--- Score
19. Are there regulatory / compliance issues?
<--- Score
20. Which information does the Software test engineering business case need to include?
<--- Score
21. To what extent would your organization benefit from being recognized as a award recipient?
<--- Score
22. What prevents you from making the changes you know will make you a more effective Software test engineering leader?
<--- Score
23. Looking at each person individually – does every one have the qualities which are needed to work in this group?
<--- Score
24. What are the timeframes required to resolve each of the issues/problems?
<--- Score
25. How do you recognize an Software test engineering objection?
<--- Score
26. Will new equipment/products be required to facilitate Software test engineering delivery, for example is new software needed?
<--- Score
27. Who else hopes to benefit from it?
<--- Score
28. Will a response program recognize when a crisis occurs and provide some level of response?
<--- Score
29. Whom do you really need or want to serve?
<--- Score
30. What should be considered when identifying available resources, constraints, and deadlines?
<--- Score
31. Does your organization need more Software test engineering education?
<--- Score
32. What are the clients issues and concerns?
<--- Score
33. Can management personnel recognize the monetary benefit of Software test engineering?
<--- Score
34. Who needs budgets?
<--- Score
35. Have you identified your Software test engineering key performance indicators?
<--- Score
36. Are there Software test engineering problems defined?
<--- Score
37. What tools and technologies are needed for a custom Software test engineering project?
<--- Score
38. As a sponsor, customer or management, how important is it to meet goals, objectives?
<--- Score
39. How do you identify the kinds of information that you will need?
<--- Score
40. What is the problem and/or vulnerability?
<--- Score
41. When a Software test engineering manager recognizes a problem, what options are available?
<--- Score
42. How many trainings, in total, are needed?
<--- Score
43. What situation(s) led to this Software test engineering Self Assessment?
<--- Score
44. What are the minority interests and what amount of minority interests can be recognized?
<--- Score
45. What resources or support might you need?
<--- Score
46. Is it needed?
<--- Score
47. Why the need?
<--- Score
48. Are there any revenue recognition issues?
<--- Score
49. Where is training needed?
<--- Score
50. Does Software test engineering create potential expectations in other areas that need to be recognized and considered?
<--- Score
51. Is the quality assurance team identified?
<--- Score
52. Do you need different information or graphics?
<--- Score
53. What do you need to start doing?
<--- Score
54. Where do you need to exercise leadership?
<--- Score
55. Why is this needed?
<--- Score
56. How are you going to measure success?
<--- Score
57. Is it clear when you think of the day ahead of you what activities and tasks you need to complete?
<--- Score
58. Are you dealing with any of the same issues today as yesterday? What can you do about this?
<--- Score
59. For your Software test engineering project, identify and describe the business environment, is there more than one layer to the business environment?
<--- Score
60. Who needs what information?
<--- Score
61. Will Software test engineering deliverables need to be tested and, if so, by whom?
<--- Score
62. How can auditing be a preventative security measure?
<--- Score
63. What Software test engineering problem should be solved?
<--- Score
64. What problems are you facing and how do you consider Software test engineering will circumvent those obstacles?
<--- Score
65. Is the need for organizational change recognized?
<--- Score
66. What training and capacity building actions are needed to implement proposed reforms?
<--- Score
67. Who defines the rules in relation to any given issue?
<--- Score
68. What are the Software test engineering resources needed?
<--- Score
69. To what extent does each concerned units management team recognize Software test engineering as an effective investment?
<--- Score
70. 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
71. Did you miss any major Software test engineering issues?
<--- Score
72. Would you recognize a threat from the inside?
<--- Score
73. What is the extent or complexity of the Software test engineering problem?
<--- Score
74. Will it solve real problems?
<--- Score
75. Consider your own Software test engineering project, what types of organizational problems do you think might be causing or affecting your problem, based on the work done so far?
<--- Score
76. What is the recognized need?
<--- Score
77. Are losses recognized in a timely manner?
<--- Score
78. What are the stakeholder objectives to be achieved with Software test engineering?
<--- Score
79. Who are your key stakeholders who need to sign off?
<--- Score
80. What else needs to be measured?
<--- Score
81. How are the Software test engineering’s objectives aligned to the group’s overall stakeholder strategy?
<--- Score
82. Think about the people you identified for your Software test engineering 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
83. How do you take a forward-looking perspective in identifying Software test engineering research related to market response and models?
<--- Score
84. How do you recognize an objection?
<--- Score
85. What are your needs in relation to Software test engineering skills, labor, equipment, and markets?
<--- Score
86. Do you recognize Software test engineering achievements?
<--- Score
87. Who should resolve the Software test engineering issues?
<--- Score
88. What Software test engineering events should you attend?
<--- Score
89. Do you know what you need to know about Software test engineering?
<--- Score
90. What vendors make products that address the Software test engineering needs?
<--- Score
91. Are employees recognized for desired behaviors?
<--- Score
92. Which issues are too important to ignore?
<--- Score
93. What would happen if Software test engineering weren’t done?
<--- Score
94. Which needs are not included or involved?
<--- Score
95. What is the Software test engineering problem definition? What do you need to resolve?
<--- Score
96. Do you have/need 24-hour access to key personnel?
<--- Score
97. Do you need to avoid or amend any Software test engineering activities?
<--- Score
98. How do you identify subcontractor relationships?
<--- Score
99. What activities does the governance board need to consider?
<--- 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.
