Agile Software215
3.3 Change Log: Agile Software217
3.4 Decision Log: Agile Software219
3.5 Quality Audit: Agile Software221
3.6 Team Directory: Agile Software224
3.7 Team Operating Agreement: Agile Software226
3.8 Team Performance Assessment: Agile Software228
3.9 Team Member Performance Assessment: Agile Software230
3.10 Issue Log: Agile Software232
4.0 Monitoring and Controlling Process Group: Agile Software234
4.1 Project Performance Report: Agile Software236
4.2 Variance Analysis: Agile Software238
4.3 Earned Value Status: Agile Software240
4.4 Risk Audit: Agile Software242
4.5 Contractor Status Report: Agile Software244
4.6 Formal Acceptance: Agile Software246
5.0 Closing Process Group: Agile Software248
5.1 Procurement Audit: Agile Software250
5.2 Contract Close-Out: Agile Software253
5.3 Project or Phase Close-Out: Agile Software255
5.4 Lessons Learned: Agile Software257
Index259
CRITERION #1: RECOGNIZE
INTENT: Be aware of the need for change. Recognize that there is an unfavorable variation, problem or symptom.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
1. Do you need quantum computing to create human level AI?
<--- Score
2. How much flexibility does your software need?
<--- Score
3. How do scaling issues affect the manner in which you fulfill your goal of identifying your initial scope?
<--- Score
4. Do you need quantum computing for consciousness?
<--- Score
5. Why do you have problems keeping things simple?
<--- Score
6. Whom do you really need or want to serve?
<--- Score
7. What prevents you from performing your work as efficiently as possible?
<--- Score
8. What are the expected benefits of Agile software to the stakeholder?
<--- Score
9. Why do you need to write additional tests?
<--- Score
10. As a sponsor, customer or management, how important is it to meet goals, objectives?
<--- Score
11. How are the Agile software’s objectives aligned to the group’s overall stakeholder strategy?
<--- Score
12. Which information does the Agile software business case need to include?
<--- Score
13. How do alternate target architectures eliminate the problems of the current architecture?
<--- Score
14. How do you address challenges to deliver software that your business needs?
<--- Score
15. How many supply boxes will you need?
<--- Score
16. Who else hopes to benefit from it?
<--- Score
17. Are you looking for an internationally recognized certification in agile software testing?
<--- Score
18. What are the stakeholder objectives to be achieved with Agile software?
<--- Score
19. Are the identified requirements relatively stable and clear?
<--- Score
20. How do you prevent testing gaps across the full system integration?
<--- Score
21. What situation(s) led to this Agile software Self Assessment?
<--- Score
22. How much architectural activity will a project need?
<--- Score
23. What Agile software events should you attend?
<--- Score
24. How can readers be prevented from using versions?
<--- Score
25. How much are sponsors, customers, partners, stakeholders involved in Agile software? In other words, what are the risks, if Agile software does not deliver successfully?
<--- Score
26. What system qualities need to be delivered & when?
<--- Score
27. Are there any specific expectations or concerns about the Agile software team, Agile software itself?
<--- Score
28. Are there recognized Agile software problems?
<--- Score
29. How are you going to measure success?
<--- Score
30. What does Agile software success mean to the stakeholders?
<---
