a Expert Software production readiness review be required?
<--- Score
63. What would be the goal or target for a Expert Software’s improvement team?
<--- Score
64. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
65. How can the value of Expert Software be defined?
<--- Score
66. Is Expert Software required?
<--- Score
67. How do you keep key subject matter experts in the loop?
<--- Score
68. Do you all define Expert Software in the same way?
<--- Score
69. Why are you doing Expert Software and what is the scope?
<--- Score
70. What Expert Software requirements should be gathered?
<--- Score
71. What information do you gather?
<--- Score
72. What is the scope of the Expert Software work?
<--- Score
73. When is/was the Expert Software start date?
<--- Score
74. What happens if Expert Software’s scope changes?
<--- Score
75. 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
76. What is the scope of the Expert Software effort?
<--- Score
77. Are resources adequate for the scope?
<--- Score
78. Are roles and responsibilities formally defined?
<--- Score
79. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
80. What is the scope of Expert Software?
<--- Score
81. What is a worst-case scenario for losses?
<--- Score
82. Scope of sensitive information?
<--- Score
83. What information should you gather?
<--- Score
84. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
85. How do you gather Expert Software requirements?
<--- Score
86. Have all of the relationships been defined properly?
<--- Score
87. What customer feedback methods were used to solicit their input?
<--- Score
88. What sort of initial information to gather?
<--- Score
89. Is the scope of Expert Software defined?
<--- Score
90. What are the Expert Software use cases?
<--- Score
91. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
92. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
93. Is scope creep really all bad news?
<--- Score
94. Are task requirements clearly defined?
<--- Score
95. Where can you gather more information?
<--- Score
96. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
97. How does the Expert Software manager ensure against scope creep?
<--- Score
98. How do you manage changes in Expert Software requirements?
<--- Score
99. How do you manage unclear Expert Software requirements?
<--- Score
100. Who approved the Expert Software scope?
<--- Score
101. What are the dynamics of the communication plan?
<--- Score
102. How do you gather the stories?
<--- Score
103. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
104. Do you have organizational privacy requirements?
<--- Score
105. Is Expert Software currently on schedule according to the plan?
<--- Score
106. What critical content must be communicated – who, what, when, where, and how?
<--- Score
107. Has your scope been defined?
<--- Score
108.
