TIBCO Software A Complete Guide - 2020 Edition. Gerardus Blokdyk

      <--- 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?

      <--- Score

      106. Is full participation by members in regularly held team meetings guaranteed?

      <--- Score

      107. What is the context?

      <--- Score

      108. Have all of the relationships been defined properly?

      <--- Score

      109. What scope to assess?

      <--- Score

      110. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?

      <--- Score

      111. Has a high-level ‘as is’ process map been completed, verified and validated?

      <--- Score

      112. What constraints exist that might impact the team?

      <--- Score

      113. Has a TIBCO Software requirement not been met?

      <--- Score

      114. What information do you gather?

      <--- Score

      115. Is the work to date meeting requirements?

      <--- Score

      116. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?

      <--- Score

      117. 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

      118. What would be the goal or target for a TIBCO Software’s improvement team?

      <--- Score

      119. The political context: who holds power?

      <--- Score

      120. How was the ‘as is’ process map developed, reviewed, verified and validated?

      <--- Score

      121. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?

      <--- Score

      122. Is the current ‘as is’ process being followed? If not, what are the discrepancies?

      <--- Score

      123. When is/was the TIBCO Software start date?

      <--- Score

      124. Is there a clear TIBCO Software case definition?

      <--- Score

      125. What TIBCO Software requirements should be gathered?

      <--- Score

      126. What knowledge or experience is required?

      <---