Score
31. How much storage and MIPS do you need?
<--- Score
32. What if your business needs are still emerging and certain aspects of the system are rapidly changing or cannot be defined yet?
<--- Score
33. Are there other common software architecture problems?
<--- Score
34. What problems are you facing and how do you consider Agile software will circumvent those obstacles?
<--- Score
35. What would happen if Agile software weren’t done?
<--- Score
36. What problems arise from the current architectural practices?
<--- Score
37. What extra resources will you need?
<--- Score
38. How to prevent the architecture from gradually degrading over time?
<--- Score
39. How much of an explicit description of the architecture does the project 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 Agile software 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. What constraints on components are imposed by non-functional requirements?
<--- Score
2. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
3. Does the team have regular meetings?
<--- Score
4. Who are the Agile software improvement team members, including Management Leads and Coaches?
<--- Score
5. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
6. If substitutes have been appointed, have they been briefed on the Agile software goals and received regular communications as to the progress to date?
<--- Score
7. What are the rough order estimates on cost savings/opportunities that Agile software brings?
<--- Score
8. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
9. How do you keep key subject matter experts in the loop?
<--- Score
10. Is Agile software linked to key stakeholder goals and objectives?
<--- Score
11. What would be the goal or target for a Agile software’s improvement team?
<--- Score
12. What critical content must be communicated – who, what, when, where, and how?
<--- Score
13. How will the Agile software team and the group measure complete success of Agile software?
<--- Score
14. How do you achieve a balance between the fixed and evolving quality requirements?
<--- Score
15. Is the team equipped with available and reliable resources?
<--- Score
16. What are the compelling stakeholder reasons for embarking on Agile software?
<--- Score
17. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
18. Do you have a Agile software success story or case study ready to tell and share?
<--- Score
19. Are accountability and ownership for Agile software clearly defined?
<--- Score
20. Are improvement team members fully trained on Agile software?
<--- Score
21. What is the definition of Agile software excellence?
<--- Score
22. How will that use case habit know which accounts to use?
<--- Score
23. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
24. What are the record-keeping requirements of Agile software activities?
<--- Score
25. Has a team charter been developed and communicated?
<--- Score
26. Has/have the customer(s) been identified?
<--- Score
27. Do you have organizational privacy requirements?
<--- Score
28. How did the Agile software manager receive input to the development of a Agile software improvement plan and the estimated
