Agile Software A Complete Guide - 2020 Edition. Gerardus Blokdyk
Чтение книги онлайн.
Читать онлайн книгу Agile Software A Complete Guide - 2020 Edition - Gerardus Blokdyk страница 8
58. Is there a Performance Baseline?
<--- 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 #4: ANALYZE:
INTENT: Analyze causes, assumptions and hypotheses.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
1. How can UX-related work practices and processes be integrated with agile software processes?
<--- Score
2. Does your organization have a distinct quality program that support continuous process improvement?
<--- Score
3. What types of data do your Agile software indicators require?
<--- Score
4. How do agile software development processes, open-source programming or embedded systems affect the possibilities and alternatives for interaction design management?
<--- Score
5. Do you evaluate quality assurance in Agile processes?
<--- Score
6. How to transform requirements management process to better enable agile software development?
<--- Score
7. What is so special about Test Driven Development?
<--- Score
8. What is the Agile software Driver?
<--- Score
9. How was the detailed process map generated, verified, and validated?
<--- Score
10. Is there a strict change management process?
<--- Score
11. When should a process be art not science?
<--- Score
12. Who will facilitate the team and process?
<--- Score
13. Does test-driven development improve the program code?
<--- Score
14. How much bottom-up data management?
<--- Score
15. Is the amount of data the system should operate with reasonable?
<--- Score
16. Does programming involve processes that are similar to engineering?
<--- Score
17. Were there any improvement opportunities identified from the process analysis?
<--- Score
18. What tools were used to generate the list of possible causes?
<--- Score
19. How does customer feedback change the test or the development process?
<--- Score
20. Do you value individuals and interactions over processes and tools?
<--- Score
21. Were Pareto charts (or similar) used to portray the ‘heavy hitters’ (or key sources of variation)?
<--- Score
22. Does it insist on mixing data representation and control?
<--- Score
23. How does the Agile software development process work?
<--- Score
24. What are the measurement goals in an agile software development process?
<--- Score
25. Is the Agile software process severely broken such that a re-design is necessary?
<--- Score
26. What Agile software data will be collected?
<--- Score
27. Is there any way to speed up the process?
<--- Score
28. What are the most commonly used architecture documenting practices in agile development processes?
<--- Score
29. What are the personnel training and qualifications required?
<--- Score
30. Is agile software development process more successful?
<--- Score
31. What are the most important problems with the Agile software development process of the B2C department?
<--- Score
32. How are UX-related work practices and processes integrated with agile software processes in practice in a web-related environment?
<--- Score
33. Which agile software engineering processes and practices consider artifacts to which extent?
<--- Score
34. What is the cost of poor quality as supported by the team’s analysis?
<--- Score
35. What is the complexity of the output produced?
<--- Score
36. What does the data say about the performance of the stakeholder process?
<--- Score
37. What systems/processes must you excel at?
<--- Score
38.