Technical Efficiency A Complete Guide - 2020 Edition. Gerardus Blokdyk

Technical efficiency requirements should be gathered?

      <--- Score

      16. Who are the Technical efficiency improvement team members, including Management Leads and Coaches?

      <--- Score

      17. What was the context?

      <--- Score

      18. Do you all define Technical efficiency in the same way?

      <--- Score

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

      <--- Score

      20. How do you think the partners involved in Technical efficiency would have defined success?

      <--- Score

      21. What customer feedback methods were used to solicit their input?

      <--- Score

      22. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?

      <--- Score

      23. What knowledge or experience is required?

      <--- Score

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

      <--- Score

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

      <--- Score

      26. How do you manage changes in Technical efficiency requirements?

      <--- Score

      27. Is Technical efficiency linked to key stakeholder goals and objectives?

      <--- Score

      28. How will variation in the actual durations of each activity be dealt with to ensure that the expected Technical efficiency results are met?

      <--- Score

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

      <--- Score

      30. What critical content must be communicated – who, what, when, where, and how?

      <--- Score

      31. Are the Technical efficiency requirements complete?

      <--- Score

      32. How do you gather requirements?

      <--- Score

      33. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?

      <--- Score

      34. How was the ‘as is’ process map developed, reviewed, verified and validated?

      <--- Score

      35. Are roles and responsibilities formally defined?

      <--- Score

      36. What is out of scope?

      <--- Score

      37. When is the estimated completion date?

      <--- Score

      38. Have all of the relationships been defined properly?

      <--- Score

      39. Who approved the Technical efficiency scope?

      <--- Score

      40. What sources do you use to gather information for a Technical efficiency study?

      <--- Score

      41. How do you build the right business case?

      <--- Score

      42. How and when will the baselines be defined?

      <--- Score

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

      <--- Score

      44. Who is gathering information?

      <--- Score

      45. Are the Technical efficiency requirements testable?

      <--- Score

      46. Is the Technical efficiency scope complete and appropriately sized?

      <--- Score

      47. How often are the team meetings?

      <--- Score

      48. How does the Technical efficiency manager ensure against scope creep?

      <--- Score

      49. What specifically is the problem? Where does it occur? When does it occur? What is its extent?

      <--- Score

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

      <--- Score

      51. Do you have organizational privacy requirements?

      <--- Score

      52. What is the scope of the Technical efficiency effort?

      <--- Score

      53. Have the customer needs been translated into specific, measurable requirements? How?

      <--- Score

      54. What is the scope of the Technical efficiency work?

      <--- Score

      55. What are the requirements for audit information?

      <--- Score

      56. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?

      <--- Score

      57. Are accountability and ownership for Technical efficiency clearly defined?

      <--- Score

      58. When is/was the Technical efficiency start date?

      <--- Score

      59. Is the scope of Technical efficiency defined?

      <--- Score

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

      61. Does the scope remain the same?

      <--- Score

      62. Are there different segments of customers?

      <--- Score

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

      <--- Score

      64. Is scope creep really all bad news?

      <--- Score

      65. What are the rough order estimates on cost savings/opportunities that Technical efficiency brings?

      <--- Score

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

      <--- Score

      67. Is Technical efficiency currently on schedule according to the plan?

      <--- Score

      68. Have specific policy objectives been defined?

      <--- Score

      69. What are the core elements of the Technical efficiency business case?

      <--- Score

      70. Has a project plan, Gantt chart, or similar been developed/completed?

      <---