How and when will the baselines be defined?
<--- Score
62. What are the dynamics of the communication plan?
<--- Score
63. How do you manage changes in TIBCO Software requirements?
<--- Score
64. Is the TIBCO Software scope complete and appropriately sized?
<--- Score
65. Will a TIBCO Software production readiness review be required?
<--- Score
66. Will team members perform TIBCO Software work when assigned and in a timely fashion?
<--- Score
67. How do you catch TIBCO Software definition inconsistencies?
<--- Score
68. Are the TIBCO Software requirements testable?
<--- Score
69. What is the scope?
<--- Score
70. What are (control) requirements for TIBCO Software Information?
<--- Score
71. What is the definition of TIBCO Software excellence?
<--- Score
72. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
73. How did the TIBCO Software manager receive input to the development of a TIBCO Software improvement plan and the estimated completion dates/times of each activity?
<--- Score
74. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
75. Does the team have regular meetings?
<--- Score
76. What are the rough order estimates on cost savings/opportunities that TIBCO Software brings?
<--- Score
77. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
78. What are the requirements for audit information?
<--- Score
79. Has a team charter been developed and communicated?
<--- Score
80. Is the TIBCO Software scope manageable?
<--- Score
81. Is TIBCO Software linked to key stakeholder goals and objectives?
<--- Score
82. How is the team tracking and documenting its work?
<--- Score
83. When is the estimated completion date?
<--- Score
84. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
85. What is the worst case scenario?
<--- Score
86. How do you gather TIBCO Software requirements?
<--- Score
87. Scope of sensitive information?
<--- Score
88. Who is gathering TIBCO Software information?
<--- Score
89. Is there a critical path to deliver TIBCO Software results?
<--- Score
90. Are task requirements clearly defined?
<--- Score
91. Are roles and responsibilities formally defined?
<--- Score
92. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
93. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
94. What key stakeholder process output measure(s) does TIBCO Software leverage and how?
<--- Score
95. What sources do you use to gather information for a TIBCO Software study?
<--- Score
96. Are all requirements met?
<--- Score
97. What customer feedback methods were used to solicit their input?
<--- Score
98. What is in the scope and what is not in scope?
<--- Score
99. What are the TIBCO Software tasks and definitions?
<--- Score
100. Who are the TIBCO Software improvement team members, including Management Leads and Coaches?
<--- Score
101. What are the compelling stakeholder reasons for embarking on TIBCO Software?
<--- Score
102. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
103. Are accountability and ownership for TIBCO Software clearly defined?
<--- Score
104. Who defines (or who defined) the rules and roles?
<--- Score
105. What is in scope?
