.

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

      <--- Score

      13. Where can you gather more information?

      <--- Score

      14. Who approved the System Protection scope?

      <--- Score

      15. Is data collected and displayed to better understand customer(s) critical needs and requirements.

      <--- Score

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

      <--- Score

      17. Is the work to date meeting requirements?

      <--- Score

      18. What is the scope of the System Protection effort?

      <--- Score

      19. How would you define System Protection leadership?

      <--- Score

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

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

      <--- Score

      22. What information do you gather?

      <--- Score

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

      <--- Score

      24. How have you defined all System Protection requirements first?

      <--- Score

      25. How would you define the culture at your organization, how susceptible is it to System Protection changes?

      <--- Score

      26. How do you hand over System Protection context?

      <--- Score

      27. Does the team have regular meetings?

      <--- Score

      28. What knowledge or experience is required?

      <--- Score

      29. What sources do you use to gather information for a System Protection study?

      <--- Score

      30. What sort of initial information to gather?

      <--- Score

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

      <--- Score

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

      <--- Score

      33. What intelligence can you gather?

      <--- Score

      34. What is the scope of the System Protection work?

      <--- Score

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

      <--- Score

      36. How often are the team meetings?

      <--- Score

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

      <--- Score

      38. What is out-of-scope initially?

      <--- Score

      39. What is the definition of System Protection excellence?

      <--- Score

      40. Have all basic functions of System Protection been defined?

      <--- Score

      41. What defines best in class?

      <--- Score

      42. Do you have organizational privacy requirements?

      <--- Score

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

      <--- Score

      44. Do you have a System Protection success story or case study ready to tell and share?

      <--- Score

      45. Are accountability and ownership for System Protection clearly defined?

      <--- Score

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

      <--- Score

      47. Is the System Protection scope complete and appropriately sized?

      <--- Score

      48. When is the estimated completion date?

      <--- Score

      49. Is scope creep really all bad news?

      <--- Score

      50. Is the scope of System Protection defined?

      <--- Score

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

      <--- Score

      52. What are the core elements of the System Protection business case?

      <--- Score

      53. Is System Protection linked to key stakeholder goals and objectives?

      <--- Score

      54. What System Protection requirements should be gathered?

      <--- Score

      55. What is the scope?

      <--- Score

      56. How and when will the baselines be defined?

      <--- Score

      57. Scope of sensitive information?

      <--- Score

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

      <--- Score

      59. Do you all define System Protection in the same way?

      <--- Score

      60. What key stakeholder process output measure(s) does System Protection leverage and how?

      <--- Score

      61. Is the improvement 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

      62. What are the rough order estimates on cost savings/opportunities that System Protection brings?

      <--- Score

      63. Are there different segments of customers?

      <--- Score

      64. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?

      <--- Score

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

      <--- Score

      66. Will team members regularly document their System Protection work?

      <--- Score

      67. Is the System Protection scope manageable?

      <---