.

 -


Скачать книгу
team aware of the different versions of a process: what they think it is vs. what it actually is vs. what it should be vs. what it could be?

      <--- Score

      8. Is there any additional Domain Awareness System definition of success?

      <--- Score

      9. Who is gathering Domain Awareness System information?

      <--- Score

      10. What are the record-keeping requirements of Domain Awareness System activities?

      <--- Score

      11. How would you define Domain Awareness System leadership?

      <--- Score

      12. What system do you use for gathering Domain Awareness System information?

      <--- Score

      13. What Domain Awareness System requirements should be gathered?

      <--- Score

      14. Is the current ‘as is’ process being followed? If not, what are the discrepancies?

      <--- Score

      15. Who are the Domain Awareness System improvement team members, including Management Leads and Coaches?

      <--- Score

      16. How have you defined all Domain Awareness System requirements first?

      <--- Score

      17. What are the tasks and definitions?

      <--- Score

      18. How do you gather requirements?

      <--- Score

      19. Will team members regularly document their Domain Awareness System work?

      <--- Score

      20. When is the estimated completion date?

      <--- Score

      21. What are the core elements of the Domain Awareness System business case?

      <--- Score

      22. What is the scope?

      <--- Score

      23. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?

      <--- Score

      24. Is scope creep really all bad news?

      <--- Score

      25. What are the boundaries of the scope? What is in bounds and what is not? What is the start point? What is the stop point?

      <--- Score

      26. Why are you doing Domain Awareness System and what is the scope?

      <--- Score

      27. Are audit criteria, scope, frequency and methods defined?

      <--- Score

      28. Who defines (or who defined) the rules and roles?

      <--- Score

      29. How would you define the culture at your organization, how susceptible is it to Domain Awareness System changes?

      <--- Score

      30. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?

      <--- Score

      31. Is the team equipped with available and reliable resources?

      <--- Score

      32. How do you catch Domain Awareness System definition inconsistencies?

      <--- Score

      33. Does the team have regular meetings?

      <--- Score

      34. Has a team charter been developed and communicated?

      <--- Score

      35. What are (control) requirements for Domain Awareness System Information?

      <--- Score

      36. Do you have organizational privacy requirements?

      <--- Score

      37. Is Domain Awareness System required?

      <--- Score

      38. Have all of the relationships been defined properly?

      <--- Score

      39. Are the Domain Awareness System requirements testable?

      <--- Score

      40. What are the compelling stakeholder reasons for embarking on Domain Awareness System?

      <--- Score

      41. Will a Domain Awareness System production readiness review be required?

      <--- Score

      42. When is/was the Domain Awareness System start date?

      <--- Score

      43. How do you hand over Domain Awareness System context?

      <--- Score

      44. What is the definition of success?

      <--- Score

      45. Are there any constraints known that bear on the ability to perform Domain Awareness System work? How is the team addressing them?

      <--- Score

      46. Is Domain Awareness System linked to key stakeholder goals and objectives?

      <--- Score

      47. What are the requirements for audit information?

      <--- Score

      48. Has the direction changed at all during the course of Domain Awareness System? If so, when did it change and why?

      <--- Score

      49. How and when will the baselines be defined?

      <--- Score

      50. Who is gathering information?

      <--- Score

      51. What intelligence can you gather?

      <--- Score

      52. What was the context?

      <--- Score

      53. How will variation in the actual durations of each activity be dealt with to ensure that the expected Domain Awareness System results are met?

      <--- Score

      54. Are task requirements clearly defined?

      <--- Score

      55. What is out of scope?

      <--- Score

      56. The political context: who holds power?

      <--- Score

      57. What would be the goal or target for a Domain Awareness System’s improvement team?

      <--- Score

      58. What is the definition of Domain Awareness System excellence?

      <--- Score

      59. Has a high-level ‘as is’ process map been completed, verified and validated?

      <--- Score

      60. Who approved the Domain Awareness System scope?

      <--- Score

      61. Are approval levels defined for contracts and supplements to contracts?

      <--- Score

      62. When are meeting minutes sent out? Who is on the distribution list?

      <--- Score

      63. What sources do you use


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