Score
75. What are the timeframes required to resolve each of the issues/problems?
<--- Score
76. Who else hopes to benefit from it?
<--- Score
77. For your Software contract project, identify and describe the business environment, is there more than one layer to the business environment?
<--- Score
78. Have you identified your Software contract key performance indicators?
<--- Score
79. Are there any revenue recognition issues?
<--- Score
80. Is the need for organizational change recognized?
<--- Score
81. Who are your key stakeholders who need to sign off?
<--- Score
82. Consider your own Software contract project, what types of organizational problems do you think might be causing or affecting your problem, based on the work done so far?
<--- Score
83. Why the need?
<--- Score
84. What are the minority interests and what amount of minority interests can be recognized?
<--- Score
85. What do you need to start doing?
<--- Score
86. What is the smallest subset of the problem you can usefully solve?
<--- Score
87. Will it solve real problems?
<--- Score
88. What Software contract events should you attend?
<--- Score
89. Are your goals realistic? Do you need to redefine your problem? Perhaps the problem has changed or maybe you have reached your goal and need to set a new one?
<--- Score
90. Which information does the Software contract business case need to include?
<--- Score
91. Does Software contract create potential expectations in other areas that need to be recognized and considered?
<--- Score
92. How do you identify the kinds of information that you will need?
<--- Score
Add up total points for this section: _____ = Total points for this section
Divided by: ______ (number of statements answered) = ______ Average score for this section
Transfer your score to the Software contract Index at the beginning of the Self-Assessment.
CRITERION #2: DEFINE:
INTENT: Formulate the stakeholder problem. Define the problem, needs and objectives.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
1. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
2. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
3. What information do you gather?
<--- Score
4. Is there a critical path to deliver Software contract results?
<--- Score
5. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
6. What system do you use for gathering Software contract information?
<--- Score
7. Do you have a Software contract success story or case study ready to tell and share?
<--- Score
8. Do you all define Software contract in the same way?
<--- Score
9. What is the context?
<--- Score
10. Is the scope of Software contract defined?
<--- Score
11. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
12. When is/was the Software contract start date?
<--- Score
13. Have specific policy objectives been defined?
<--- Score
14. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
15. What are the Software contract tasks and definitions?
<--- Score
16. What are (control) requirements for Software contract Information?
<--- Score
17. Are required metrics defined, what are they?
<--- Score
18. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
19. Will a Software contract production readiness review be required?
<--- Score
20. Do you have organizational privacy requirements?
