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

Score

      2. If substitutes have been appointed, have they been briefed on the Open source appropriate technology goals and received regular communications as to the progress to date?

      <--- Score

      3. Is the Open source appropriate technology scope complete and appropriately sized?

      <--- Score

      4. What is in the scope and what is not in scope?

      <--- Score

      5. Has the Open source appropriate technology work been fairly and/or equitably divided and delegated among team members who are qualified and capable to perform the work? Has everyone contributed?

      <--- Score

      6. How is the team tracking and documenting its work?

      <--- Score

      7. What happens if Open source appropriate technology’s scope changes?

      <--- Score

      8. Has the direction changed at all during the course of Open source appropriate technology? If so, when did it change and why?

      <--- Score

      9. What is out-of-scope initially?

      <--- Score

      10. Are different versions of process maps needed to account for the different types of inputs?

      <--- Score

      11. What scope to assess?

      <--- Score

      12. What scope do you want your strategy to cover?

      <--- Score

      13. Is Open source appropriate technology currently on schedule according to the plan?

      <--- Score

      14. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?

      <--- Score

      15. What constraints exist that might impact the team?

      <--- Score

      16. Is special Open source appropriate technology user knowledge required?

      <--- Score

      17. How have you defined all Open source appropriate technology requirements first?

      <--- Score

      18. What intelligence can you gather?

      <--- Score

      19. What Open source appropriate technology requirements should be gathered?

      <--- Score

      20. What are the tasks and definitions?

      <--- Score

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

      <--- Score

      22. How often are the team meetings?

      <--- Score

      23. How do you think the partners involved in Open source appropriate technology would have defined success?

      <--- Score

      24. Are customer(s) identified and segmented according to their different needs and requirements?

      <--- Score

      25. Why are you doing Open source appropriate technology and what is the scope?

      <--- Score

      26. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?

      <--- Score

      27. What are the requirements for audit information?

      <--- Score

      28. Who are the Open source appropriate technology improvement team members, including Management Leads and Coaches?

      <--- Score

      29. Is the work to date meeting requirements?

      <--- Score

      30. How will variation in the actual durations of each activity be dealt with to ensure that the expected Open source appropriate technology results are met?

      <--- Score

      31. Will team members regularly document their Open source appropriate technology work?

      <--- Score

      32. Do you have organizational privacy requirements?

      <--- Score

      33. What sources do you use to gather information for a Open source appropriate technology study?

      <--- Score

      34. What key stakeholder process output measure(s) does Open source appropriate technology leverage and how?

      <--- Score

      35. Scope of sensitive information?

      <--- Score

      36. Has everyone on the team, including the team leaders, been properly trained?

      <--- Score

      37. Do you have a Open source appropriate technology success story or case study ready to tell and share?

      <--- Score

      38. When is/was the Open source appropriate technology start date?

      <--- Score

      39. Are required metrics defined, what are they?

      <--- Score

      40. How do you keep key subject matter experts in the loop?

      <--- Score

      41. How do you manage scope?

      <--- Score

      42. Is there a Open source appropriate technology management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?

      <--- Score

      43. How would you define Open source appropriate technology leadership?

      <--- Score

      44. Are all requirements met?

      <--- Score

      45. What are the record-keeping requirements of Open source appropriate technology activities?

      <--- Score

      46. What are the compelling stakeholder reasons for embarking on Open source appropriate technology?

      <--- Score

      47. The political context: who holds power?

      <--- Score

      48. Are there any constraints known that bear on the ability to perform Open source appropriate technology work? How is the team addressing them?

      <--- Score

      49. How would you define the culture at your organization, how susceptible is it to Open source appropriate technology changes?

      <--- Score

      50. Is there a clear Open source appropriate technology case definition?

      <--- Score

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

      <--- Score

      52. How do you gather the stories?

      <--- Score

      53. How do you build the right business case?

      <--- Score

      54.

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