62. How often are the team meetings?
<--- Score
63. What is the scope of Tracking systems?
<--- Score
64. What are the record-keeping requirements of Tracking systems activities?
<--- Score
65. What is in the scope and what is not in scope?
<--- Score
66. How do you manage changes in Tracking systems requirements?
<--- Score
67. What intelligence can you gather?
<--- Score
68. Will a Tracking systems production readiness review be required?
<--- Score
69. 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
70. How have you defined all Tracking systems requirements first?
<--- Score
71. How do you manage scope?
<--- Score
72. Does the team have regular meetings?
<--- Score
73. What are the tasks and definitions?
<--- Score
74. Are approval levels defined for contracts and supplements to contracts?
<--- Score
75. Has the Tracking 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
76. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
77. What happens if Tracking systems’s scope changes?
<--- Score
78. Has your scope been defined?
<--- Score
79. Is the scope of Tracking systems defined?
<--- Score
80. Are task requirements clearly defined?
<--- Score
81. What is the scope?
<--- Score
82. 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
83. Is there a clear Tracking systems case definition?
<--- Score
84. Are roles and responsibilities formally defined?
<--- Score
85. When is the estimated completion date?
<--- Score
86. What are the requirements for audit information?
<--- Score
87. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
88. Have all of the relationships been defined properly?
<--- Score
89. What gets examined?
<--- Score
90. How do you keep key subject matter experts in the loop?
<--- Score
91. What is the definition of Tracking systems excellence?
<--- Score
92. Are all requirements met?
<--- Score
93. What constraints exist that might impact the team?
<--- Score
94. Is it clearly defined in and to your organization what you do?
<--- Score
95. Do you have organizational privacy requirements?
<--- Score
96. What critical content must be communicated – who, what, when, where, and how?
<--- Score
97. What was the context?
<--- Score
98. Who is gathering Tracking systems information?
<--- Score
99. What baselines are required to be defined and managed?
<--- Score
100. How did the Tracking systems manager receive input to the development of a Tracking systems improvement plan and the estimated completion dates/times of each activity?
<--- Score
101. What system do you use for gathering Tracking systems information?
<--- Score
102. How would you define the culture at your organization, how susceptible is it to Tracking systems changes?
<--- Score
103. How do you hand over Tracking systems context?
<--- Score
104. Is there a critical path to deliver Tracking systems results?
<--- Score
105. What knowledge or experience is required?
<--- Score
106. What are (control) requirements for Tracking systems Information?
<--- Score
107.
