Quality problems related to agile methods / scalability.
Download as PPTX, PDF1 like1,211 views
The document discusses the implementation of agile practices and their impact on software quality, emphasizing the need for proper execution to improve quality characteristics. It highlights the challenges with non-functional requirements (NFRs) being ill-defined and often neglected due to stakeholders focusing mainly on functionality. A new approach is suggested for managing both functional and non-functional requirements effectively, involving customer engagement for better understanding of quality attributes.
Quality problems related to agile methods / scalability.
- 1. 1 of 20
- 2. Agile values Agile practices can improve quality if they are implemented correctly (Sfetsos, P., & Stamelos, I. (2010). Empirical Studies on Quality in Agile Practices: A Systematic Literature Review.) 2 of 20
- 3. Lack of evidence to prove its effectiveness and successful implementation (Timperi, O. (2004). An Overview of Quality Assurance Practices in Agile Methodologies.) 3 of 20
- 4. ISO 9126 TDD Pair Programming Collective Ownership ? Simple Design User Stories Refactoring Inspections Coding Standard What quality characteristics are improved with each practice? (Mnkandla, E., & Dwolatzky, B. (2006). Defining Agile Software Quality Assurance.) 4 of 20
- 5. Focus on building the right product for the customer (instead of only build it properly) (Timperi, O. (2004). An Overview of Quality Assurance Practices in Agile Methodologies.) 5 of 20
- 6. Por último… Testing is left mandatory but vague because its level and coverage are not instructed. (Timperi, O. (2004). An Overview of Quality Assurance Practices in Agile Methodologies.) 6 of 20
- 7. New role of QA Is help in business definition, risk measurement, know user needs and underlying architecture. Next… nFR ill-defined (Mnkandla, E., & Dwolatzky, B. (2006). Defining Agile Software Quality Assurance.) 7 of 20
- 8. Non-Functional Requirements (nFR) example As a Universidad ORT Uruguay student I want to come from my house to this Pechakucha. 8 of 20
- 9. Non-Functional Requirements (nFR) example As a Universidad ORT Uruguay student I want to come quickly from my house to this Pechakucha. 9 of 20
- 10. Non-Functional Requirements (nFR) example As a Universidad ORT Uruguay student I want to come quickly and economically from my house to this Pechakucha. 10 of 20
- 11. Non-Functional Requirements (nFR) example As a Universidad ORT Uruguay student I want to come quickly, economically and safely from my house to this My own car Pechakucha. 11 of 20
- 12. The problem is… Stakeholders concentrate on software functionality (FR). Critical nFR are likely to be ill-defined and neglected. (Um, T., Kim, N., Lee, D., & In, H. P. (2011). A Quality Attributes Evaluation Method for an Agile Approach.) 12 of 20
- 13. Plus… Developers accustomed to cascade assume that nFR are solved by architects and designers. (Rachel Davies, Agile Experience Ltd, UK, Non-Functional Requirements: Do User Stories Really Help?) 13 of 20
- 14. Then… New approach is needed to improve non-functional aspects through quality attributes. (Um, T., Kim, N., Lee, D., & In, H. P. (2011). A Quality Attributes Evaluation Method for an Agile Approach.) 14 of 20
- 15. Useful to manage FR and nFR at the same time (but some nFR traverse the entire project) (Um, T., Kim, N., Lee, D., & In, H. P. (2011). A Quality Attributes Evaluation Method for an Agile Approach.) 15 of 20
- 16. Example: Test that … As a blogger, I want to post - A blog post should be posted in less than 3 clicks. an entry quickly and efficiently to easily update - A blog post should be posted in less the blog than 5 seconds. The problem is that: - The stories are designed to be completed - Tunnel vision: when the team focuses on a story is easy to forget the RnF. 16 of 20
- 17. How to deal with those nFR As a blogger, I want to post spanning all the an entry quickly and stories? efficiently to easily update the blog 17 of 20
- 18. Involving the customer is essential, explaining the importance of quality attributes. (Leffingwell D. (2009). Scaling Software Agility. Agile Requirements Information Model. Online.) 18 of 20
- 19. nFR filters Reminders As ablogger, I want to post an entry to update the blog User friendly Assign responsibles for each quality attr. Efficient As a blogger, I want to post an entry quickly and efficiently to easily update the blog 19 of 20
- 20. General Issues Non-functional Proposed requirements solutions Stories quality New role, Involving the filters. responsible for customer is QA to essential, Reminders understand and explaining the measure risk importance of Assign and assist in QA quality responsibles for activities. attributes. each quality attr. nFR ill-defined 20 of 20
Editor's Notes
- #2: Quality problems related to agile methods / scalability.In this presentation we will see some problems with agile practices of quality assurance. Then we will focus on the particular problem of non-functional req. Finally we will refer to the quality problems that arise when using agile methods in large projects.Is assumed that these practices improve the quality of a software product. We will see that in any case there are problems in implementation, especially when scaling agile projects and take them to big projects distributed environments.
- #3: Agile practices improve the quality if implemented correctly.Here is some of the agile practices which, according to some authors, if implemented correctly improves product quality.These can be deployed from the inside out and the goal is to adopt as many practices as necessary to obtain outside agile values.(Sfetsos, P., & Stamelos, I. (2010). Empirical Studies on Quality in Agile Practices: A Systematic Literature Review.)
- #4: Problemas generales - No existen evidencias sobre la aplicación en forma exitosa de muchas de las prácticas de aseguramiento de calidad sugeridas en diversas metodologías ágiles. Tampoco se tiene evidencia de la eficacia de tales prácticas en conjunto o de forma individual.Un problema importante respecto a las prácticas de aseguramiento de calidad es que no existen evidencias sobre su aplicación en forma éxitosa o no. Tampoco se tiene evidencia de la eficacia de ellas en forma individual o en conjunto.(Timperi, O. (2004). An Overview of Quality Assurance Practices in Agile Methodologies.)
- #5: Problemas generales - En la literatura sobre metodologías ágiles no existe una definición que describa completamente que características de calidad son mejoradas por qué prácticas ágiles.(Mnkandla, E., & Dwolatzky, B. (2006). Defining Agile Software Quality Assurance.)
- #6: General Issues - Most agile methodologies have focused on validation and making sure that benefits exist in the software at the expense of verification. The exceptions are XP and FDD that emphasize verification over validation.(Timperi, O. (2004). An Overview of Quality Assurance Practices in Agile Methodologies.)
- #7: General issues - The problems are mainly associated with testing in many methodologies because concrete guidance and instructions are not given. (Timperi, O. (2004). An Overview of Quality Assurance Practices in Agile Methodologies.)
- #8: Suggests the figure of a QA manager (Role) to understand and measure the risks, which works in every activity undertaken by the agile team.?(Opelt, K., & Beeson, T. (2008). Agile Teams Require Agile QA: How to Make it Work, An Experience Report.)
- #15: The ISO 9126 series provides guidelines for assessing quality, but it applies to traditional projects (especially from the point of view of the documentation).(Um, T., Kim, N., Lee, D., & In, H. P. (2011). A Quality Attributes Evaluation Method for an Agile Approach.)
- #16: Raising use of stories to introduce aspects of quality attributes. Involving the customer in this area is essential because these methodologies revolve around them.(Um, T., Kim, N., Lee, D., & In, H. P. (2011). A Quality Attributes Evaluation Method for an Agile Approach.)