Software Performance Engineering A Complete Guide - 2020 Edition. Gerardus Blokdyk
Чтение книги онлайн.

Читать онлайн книгу Software Performance Engineering A Complete Guide - 2020 Edition - Gerardus Blokdyk страница 3

Название: Software Performance Engineering A Complete Guide - 2020 Edition

Автор: Gerardus Blokdyk

Издательство: Ingram

Жанр: Зарубежная деловая литература

Серия:

isbn: 9781867461203

isbn:

СКАЧАТЬ Probability and Impact Matrix: Software Performance Engineering209

      2.35 Risk Data Sheet: Software Performance Engineering211

      2.36 Procurement Management Plan: Software Performance Engineering213

      2.37 Source Selection Criteria: Software Performance Engineering215

      2.38 Stakeholder Management Plan: Software Performance Engineering217

      2.39 Change Management Plan: Software Performance Engineering219

      3.0 Executing Process Group: Software Performance Engineering221

      3.1 Team Member Status Report: Software Performance Engineering223

      3.2 Change Request: Software Performance Engineering225

      3.3 Change Log: Software Performance Engineering227

      3.4 Decision Log: Software Performance Engineering229

      3.5 Quality Audit: Software Performance Engineering231

      3.6 Team Directory: Software Performance Engineering234

      3.7 Team Operating Agreement: Software Performance Engineering236

      3.8 Team Performance Assessment: Software Performance Engineering238

      3.9 Team Member Performance Assessment: Software Performance Engineering240

      3.10 Issue Log: Software Performance Engineering242

      4.0 Monitoring and Controlling Process Group: Software Performance Engineering244

      4.1 Project Performance Report: Software Performance Engineering246

      4.2 Variance Analysis: Software Performance Engineering248

      4.3 Earned Value Status: Software Performance Engineering250

      4.4 Risk Audit: Software Performance Engineering252

      4.5 Contractor Status Report: Software Performance Engineering254

      4.6 Formal Acceptance: Software Performance Engineering256

      5.0 Closing Process Group: Software Performance Engineering258

      5.1 Procurement Audit: Software Performance Engineering260

      5.2 Contract Close-Out: Software Performance Engineering263

      5.3 Project or Phase 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

СКАЧАТЬ