<--- Score
21. Is there any additional Software contract definition of success?
<--- Score
22. Is there a clear Software contract case definition?
<--- Score
23. What knowledge or experience is required?
<--- Score
24. What happens if Software contract’s scope changes?
<--- Score
25. Are resources adequate for the scope?
<--- Score
26. How often are the team meetings?
<--- Score
27. Are audit criteria, scope, frequency and methods defined?
<--- Score
28. Who is gathering Software contract information?
<--- Score
29. How are consistent Software contract definitions important?
<--- Score
30. Is it clearly defined in and to your organization what you do?
<--- Score
31. What is the scope?
<--- Score
32. How do you hand over Software contract context?
<--- Score
33. Where can you gather more information?
<--- Score
34. What intelligence can you gather?
<--- Score
35. Is the Software contract scope manageable?
<--- Score
36. What is the scope of the Software contract work?
<--- Score
37. What scope to assess?
<--- Score
38. How do you catch Software contract definition inconsistencies?
<--- Score
39. What sort of initial information to gather?
<--- Score
40. How would you define the culture at your organization, how susceptible is it to Software contract changes?
<--- Score
41. What are the record-keeping requirements of Software contract activities?
<--- Score
42. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
43. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
44. What Software contract services do you require?
<--- Score
45. 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
46. 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
47. How do you build the right business case?
<--- Score
48. What are the core elements of the Software contract business case?
<--- Score
49. Who is gathering information?
<--- Score
50. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
51. Are task requirements clearly defined?
<--- Score
52. Has your scope been defined?
<--- Score
53. How does the Software contract manager ensure against scope creep?
<--- Score
54. What defines best in class?
<--- Score
55. Why are you doing Software contract and what is the scope?
<--- Score
56. Is Software contract required?
<--- Score
57. Have all basic functions of Software contract been defined?
<--- Score
58. When is the estimated completion date?
<--- Score
59. What are the dynamics of the communication plan?
<--- Score
60. How and when will the baselines be defined?
<--- Score
61. Has/have the customer(s) been identified?
<--- Score
62. Does the team have regular meetings?
<--- Score
63. What baselines are required to be defined and managed?
<--- Score
64. Has a team charter been developed and communicated?
<--- Score
65. How have you defined all Software contract requirements first?
<--- Score
66. Is special Software contract user knowledge required?
<---
