Building Software: The Right Way
1 like342 views
This document discusses building software the right way by ensuring quality. It explains that different stakeholders have different views of what "right" means, from making money for clients to being easy to use for end users. The document emphasizes that everyone involved in building the product is responsible for quality. Quality analysts promote best practices and ensure they are followed throughout the software development lifecycle. They identify threats and challenges to help continuously ensure quality. The document provides examples of activities in a quality analyst's day and best practices like communication, continuous integration, and usability testing that people can start with to improve quality.
Building Software: The Right Way
- 1. C l a y t o n N y a k a n a BUILDING SOFTWARE THE RIGHT WAY Clayton Nyakana
- 2. WHAT IS “RIGHT”? ▫︎Client: A product that will make money for them or simplify their lives. ▫︎PM: A product delivered within the planned budget and meets all the requirements. ▫︎Developer: A product whose code is extensible and maintainable. ▫︎Designer: A product that looks good. ▫︎End User: A simple/easy to use product that is compatible with their devices. ▫︎Blind User: A product that can be used with a braille terminal. ▫︎Competitor: A product with less features 2
- 4. So, who is responsible for Quality? 4
- 6. WHO IS RESPONSIBLE? You and Everyone involved in building the product 6
- 7. WHO IS RESPONSIBLE? So, why do we have Quality Analysts? 7
- 8. WHO ARE Q.A’S? A software quality analyst is responsible for applying the principles and practices of software quality assurance throughout the software development life cycle. Though often referred to as "quality assurance", software testing is considered to be only one part of the larger process of reducing errors. Testing is used to detect errors in a product; software quality assurance also fixes the processes that resulted in those errors. -Wikipedia 8
- 9. WHAT DO THEY DO? ▫︎They promote Quality to all stakeholders at all times ▫︎Promote best practices and ensure that they are followed ▫︎Share knowledge ▫︎Challenge the different activities on a project ▫︎Identify threats on the project 9
- 10. WHY DO WE NEED THEM? ▫︎Time/Team size constraints ▫︎Lack of Q.A knowledge/information ▫︎Lack of experience ▫︎Oversight/ neglect ▫︎Bad habits 10
- 11. HOW TO CONTINUOUSLY ENSURE QUALITY? 11
- 12. A DAY IN THE LIFE OF A Q.A 12
- 13. CARD WALL 13
- 14. STORY REVIEW AND ACCEPTANCE CRITERIA 14
- 21. SHOWCASE 21
- 22. 22
- 24. WHERE YOU CAN START FROM? ▫︎Communication (Asking the important Questions and facilitating information sharing) 24
- 25. WHERE YOU CAN START FROM? ▫︎Fast feedback infrastructure (Build a C.I server) ▫︎Continuous integration (CI) is the practice, in software engineering, of merging all developer working copies with a shared mainline several times a day. ▫︎Examples Include: Jenkins, Travis, SnapCI 25
- 26. WHERE YOU CAN START FROM? ▫︎Non Functional Requirements ▫︎A non-functional requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviours ▫︎Examples; Performance, Security, Reliability, Accessibility 26
- 27. WHERE YOU CAN START FROM? ▫︎Usability ▫︎Usability is the ease of use and learnability of a human-made object. 27
- 28. For questions or suggestions: Clayton Nyakana cnyakana@thoughtworks.com THANK YOU