<--- Score
18. Are the TIBCO Software requirements complete?
<--- Score
19. What are the core elements of the TIBCO Software business case?
<--- Score
20. Will team members regularly document their TIBCO Software work?
<--- Score
21. Is the scope of TIBCO Software defined?
<--- Score
22. What are the record-keeping requirements of TIBCO Software activities?
<--- Score
23. Is there any additional TIBCO Software definition of success?
<--- Score
24. What intelligence can you gather?
<--- Score
25. What is a worst-case scenario for losses?
<--- Score
26. How do you build the right business case?
<--- Score
27. Is the team equipped with available and reliable resources?
<--- Score
28. Who approved the TIBCO Software scope?
<--- Score
29. What information should you gather?
<--- Score
30. Is the team sponsored by a champion or stakeholder leader?
<--- Score
31. Do you have a TIBCO Software success story or case study ready to tell and share?
<--- Score
32. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
33. What baselines are required to be defined and managed?
<--- Score
34. What is the scope of the TIBCO Software effort?
<--- Score
35. Is there a TIBCO Software management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
36. How would you define the culture at your organization, how susceptible is it to TIBCO Software changes?
<--- Score
37. How will variation in the actual durations of each activity be dealt with to ensure that the expected TIBCO Software results are met?
<--- Score
38. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
39. 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
40. 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
41. Are improvement team members fully trained on TIBCO Software?
<--- Score
42. What is the definition of success?
<--- Score
43. If substitutes have been appointed, have they been briefed on the TIBCO Software goals and received regular communications as to the progress to date?
<--- Score
44. Is it clearly defined in and to your organization what you do?
<--- Score
45. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
46. Are approval levels defined for contracts and supplements to contracts?
<--- Score
47. How do you think the partners involved in TIBCO Software would have defined success?
<--- Score
48. Have all basic functions of TIBCO Software been defined?
<--- Score
49. Where can you gather more information?
<--- Score
50. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
51. How does the TIBCO Software manager ensure against scope creep?
<--- Score
52. How have you defined all TIBCO Software requirements first?
<--- Score
53. Are there any constraints known that bear on the ability to perform TIBCO Software work? How is the team addressing them?
<--- Score
54. How do you manage unclear TIBCO Software requirements?
<--- Score
55. Has/have the customer(s) been identified?
<--- Score
56. Have specific policy objectives been defined?
<--- Score
57. Has your scope been defined?
<--- Score
58. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
59. How do you hand over TIBCO Software context?
<--- Score
60. What is the scope of TIBCO Software?
<--- Score
