style="font-size:15px;"> <--- Score
67. Is scope creep really all bad news?
<--- Score
68. What key stakeholder process output measure(s) does Trusted system leverage and how?
<--- Score
69. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
70. When is the estimated completion date?
<--- Score
71. What is in scope?
<--- Score
72. What intelligence can you gather?
<--- Score
73. Why are you doing Trusted system and what is the scope?
<--- Score
74. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
75. Do you all define Trusted system in the same way?
<--- Score
76. 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
77. How will variation in the actual durations of each activity be dealt with to ensure that the expected Trusted system results are met?
<--- Score
78. What sources do you use to gather information for a Trusted system study?
<--- Score
79. How can the value of Trusted system be defined?
<--- Score
80. Scope of sensitive information?
<--- Score
81. Are the Trusted system requirements complete?
<--- Score
82. What baselines are required to be defined and managed?
<--- Score
83. 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
84. Who defines (or who defined) the rules and roles?
<--- Score
85. Are audit criteria, scope, frequency and methods defined?
<--- Score
86. Do you have a Trusted system success story or case study ready to tell and share?
<--- Score
87. How do you keep key subject matter experts in the loop?
<--- Score
88. What Trusted system requirements should be gathered?
<--- Score
89. Is there any additional Trusted system definition of success?
<--- Score
90. What is the context?
<--- Score
91. Have all basic functions of Trusted system been defined?
<--- Score
92. The political context: who holds power?
<--- Score
93. Are task requirements clearly defined?
<--- Score
94. What is the definition of success?
<--- Score
95. Has a team charter been developed and communicated?
<--- Score
96. What is a worst-case scenario for losses?
<--- Score
97. Are approval levels defined for contracts and supplements to contracts?
<--- Score
98. What constraints exist that might impact the team?
<--- Score
99. Do you have organizational privacy requirements?
<--- Score
100. What is the definition of Trusted system excellence?
<--- Score
101. What are the compelling stakeholder reasons for embarking on Trusted system?
<--- Score
102. What is the worst case scenario?
<--- Score
103. How would you define the culture at your organization, how susceptible is it to Trusted system changes?
<--- Score
104. Has the direction changed at all during the course of Trusted system? If so, when did it change and why?
<--- Score
105. What are the requirements for audit information?
<--- Score
106. How are consistent Trusted system definitions important?
<--- Score
107. What is the scope of Trusted system?
<--- Score
108. What scope do you want your strategy to cover?
<--- Score
109. How does the Trusted system manager ensure against scope creep?
<--- Score
110. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
111. Have all of the relationships been defined properly?
