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

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

СКАЧАТЬ Status Report: DRIVE Technology216

      3.2 Change Request: DRIVE Technology218

      3.3 Change Log: DRIVE Technology220

      3.4 Decision Log: DRIVE Technology222

      3.5 Quality Audit: DRIVE Technology224

      3.6 Team Directory: DRIVE Technology226

      3.7 Team Operating Agreement: DRIVE Technology228

      3.8 Team Performance Assessment: DRIVE Technology230

      3.9 Team Member Performance Assessment: DRIVE Technology232

      3.10 Issue Log: DRIVE Technology234

      4.0 Monitoring and Controlling Process Group: DRIVE Technology236

      4.1 Project Performance Report: DRIVE Technology238

      4.2 Variance Analysis: DRIVE Technology240

      4.3 Earned Value Status: DRIVE Technology242

      4.4 Risk Audit: DRIVE Technology244

      4.5 Contractor Status Report: DRIVE Technology246

      4.6 Formal Acceptance: DRIVE Technology248

      5.0 Closing Process Group: DRIVE Technology250

      5.1 Procurement Audit: DRIVE Technology252

      5.2 Contract Close-Out: DRIVE Technology254

      5.3 Project or Phase Close-Out: DRIVE Technology256

      5.4 Lessons Learned: DRIVE Technology258

      Index260

      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 take a forward-looking perspective in identifying DRIVE Technology research related to market response and models?

      <--- Score

      2. What situation(s) led to this DRIVE Technology Self Assessment?

      <--- Score

      3. What is the extent or complexity of the DRIVE Technology problem?

      <--- Score

      4. Are there DRIVE Technology problems defined?

      <--- Score

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

      <--- Score

      6. What are the clients issues and concerns?

      <--- Score

      7. What needs to stay?

      <--- Score

      8. Is the need for organizational change recognized?

      <--- Score

      9. 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

      10. Whom do you really need or want to serve?

      <--- Score

      11. How are training requirements identified?

      <--- Score

      12. Will it solve real problems?

      <--- Score

      13. Who needs budgets?

      <--- Score

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

      <--- Score

      15. Did you miss any major DRIVE Technology issues?

      <--- Score

      16. Which needs are not included or involved?

      <--- Score

      17. When a DRIVE Technology manager recognizes a problem, what options are available?

      <--- Score

      18. Think about the people you identified for your DRIVE Technology 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

      19. Where is training needed?

      <--- Score

      20. What creative shifts do you need to take?

      <--- Score

      21. What vendors make products that address the DRIVE Technology needs?

      <--- Score

      22. What are your needs in relation to DRIVE Technology skills, labor, equipment, and markets?

      <--- Score

      23. Where do you need to exercise leadership?

      <--- Score

      24. How do you recognize an objection?

      <--- Score

      25. Are there any specific expectations or concerns about the DRIVE Technology team, DRIVE Technology itself?

      <--- Score

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

      <--- Score

      27. Will DRIVE Technology deliverables need to be tested and, if so, by whom?

      <--- Score

      28. How do you recognize an DRIVE Technology objection?

      <--- Score

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

      <--- Score

      30. СКАЧАТЬ