Quality & Risk Flashcards
How to guarantee the quality of the final product in Agile?
Work on smaller steps and catch errors more easily
At each feedback, the team receives information about the quality and how the project is going
Frequent test of the software that has been development until now on a daily basis. Test immediately and fix immediately
Product Owner clarifies requirements and accept features done (acceptance criteria)
Scrum Master ensures the work environment allow the team to work to the best of their abilities
Quality Development techniques in Agile
Test-driven development (TDD)
-Create a test through which the functionality has to go through while developing until it passes
Pair programming
-2 person, one computer. You work together with other person to a single functionality. One is working and the other is checking and navigating (controller). Catch very early problems. Then switch.
Peer review
-Someone controls what you have done after you have finished, work together to solve issues.
Collective code ownership
-Code is public. All the development team can change what has been done by other members
Continuous integration
-Control that the part you developed is integrated with the other parts that have been already developed
Improving Quality in Agile
Inspect: Sprint Review
Adapt: Sprint Retrospective
Risk management in Agile
Definition of done
-Developed, tested, integrated and documented
Self-funding
-Small revenues for the client and you overtime
Failing fast
-Reduce risk because I arrive to the client earlier, delivering small amount of work
(bonus)
However, there is not a structured way to track risk/opportunity as TPM
If the project is not achieving in the beginning the definition of done, it could end earlier and save costs (project failed, but earlier than TPM)
