measurable requirements? How?
<--- Score
65. Have all of the relationships been defined properly?
<--- Score
66. How do you catch Protocol Systems definition inconsistencies?
<--- Score
67. Are required metrics defined, what are they?
<--- Score
68. What is the scope of the Protocol Systems work?
<--- Score
69. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
70. Will team members perform Protocol Systems work when assigned and in a timely fashion?
<--- Score
71. Does the scope remain the same?
<--- Score
72. Are there any constraints known that bear on the ability to perform Protocol Systems work? How is the team addressing them?
<--- Score
73. What are the core elements of the Protocol Systems business case?
<--- Score
74. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
75. How will variation in the actual durations of each activity be dealt with to ensure that the expected Protocol Systems results are met?
<--- Score
76. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
77. Is special Protocol Systems user knowledge required?
<--- Score
78. Who approved the Protocol Systems scope?
<--- Score
79. Is it clearly defined in and to your organization what you do?
<--- Score
80. How and when will the baselines be defined?
<--- Score
81. Has the Protocol Systems 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
82. What are the requirements for audit information?
<--- Score
83. Is the Protocol Systems scope manageable?
<--- Score
84. How do you gather the stories?
<--- Score
85. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
86. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
87. 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
88. What Protocol Systems services do you require?
<--- Score
89. Do you have organizational privacy requirements?
<--- Score
90. Scope of sensitive information?
<--- Score
91. Are audit criteria, scope, frequency and methods defined?
<--- Score
92. Are accountability and ownership for Protocol Systems clearly defined?
<--- Score
93. Will team members regularly document their Protocol Systems work?
<--- Score
94. What are the Protocol Systems use cases?
<--- Score
95. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
96. Is Protocol Systems required?
<--- Score
97. How do you gather requirements?
<--- Score
98. What constraints exist that might impact the team?
<--- Score
99. What is out of scope?
<--- Score
100. 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
101. What is in scope?
<--- Score
102. Who is gathering Protocol Systems information?
<--- Score
103. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
104. What are the Protocol Systems tasks and definitions?
<--- Score
105. Is there any additional Protocol Systems definition of success?
<--- Score
106. What are (control) requirements for Protocol Systems Information?
<--- Score
107. What knowledge or experience is required?
<---
