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

Close-Out: Software Performance Engineering265

      5.4 Lessons Learned: Software Performance Engineering267

      Index269

      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 are the Software Performance Engineering’s objectives aligned to the group’s overall stakeholder strategy?

      <--- Score

      2. Who needs budgets?

      <--- Score

      3. What Software Performance Engineering problem should be solved?

      <--- Score

      4. Where is training needed?

      <--- Score

      5. Do you recognize Software Performance Engineering achievements?

      <--- Score

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

      <--- Score

      7. What Software Performance Engineering events should you attend?

      <--- Score

      8. When a Software Performance Engineering manager recognizes a problem, what options are available?

      <--- Score

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

      <--- Score

      10. What situation(s) led to this Software Performance Engineering Self Assessment?

      <--- Score

      11. Will new equipment/products be required to facilitate Software Performance Engineering delivery, for example is new software needed?

      <--- Score

      12. What are the stakeholder objectives to be achieved with Software Performance Engineering?

      <--- Score

      13. Who else hopes to benefit from it?

      <--- Score

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

      <--- Score

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

      <--- Score

      16. Have you identified your Software Performance Engineering key performance indicators?

      <--- Score

      17. Do you know what you need to know about Software Performance Engineering?

      <--- Score

      18. Which needs are not included or involved?

      <--- Score

      19. Can management personnel recognize the monetary benefit of Software Performance Engineering?

      <--- Score

      20. How are training requirements identified?

      <--- Score

      21. What does Software Performance Engineering success mean to the stakeholders?

      <--- Score

      22. What vendors make products that address the Software Performance Engineering needs?

      <--- Score

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

      <--- Score

      24. How can auditing be a preventative security measure?

      <--- Score

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

      <--- Score

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

      <--- Score

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

      <--- Score

      28. What are the expected benefits of Software Performance Engineering to the stakeholder?

      <--- Score

      29. How do you recognize an objection?

      <--- Score

      30. What problems are you facing and how do you consider Software Performance Engineering will circumvent those obstacles?

      <--- Score

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

      <--- Score

      32. Why the need?

      <--- Score

      33. What do you need to start doing?

      <--- Score

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

      <--- Score

      35. What Software Performance Engineering coordination do you need?

      <--- Score

      36. What resources or support might you need?

      <--- Score

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

      <--- Score

      38. Is it needed?

      <--- Score

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

      <--- Score

      40. Are there regulatory / compliance issues?

      <--- Score

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

      <--- Score

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

      <--- Score

      43. What prevents you from making the changes you know will make you a more effective Software Performance Engineering leader?

      <--- Score

      44. Are there Software Performance Engineering problems defined?

      <--- Score

      45. Who should resolve the Software Performance Engineering issues?

      <--- Score

      46. Are there recognized Software Performance Engineering problems?

      <--- Score

      47. How do you recognize an Software Performance Engineering objection?

      <--- Score

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

      <--- Score

      49. How do you identify subcontractor relationships?

      <--- Score

      50.

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