MAY 2019CIOAPPLICATIONS.COM8gile model changed the way we deliver software. It requires more than adopting new processes like Scrum and DevOps - it requires a complete mind shift. While delivering software in small increments and receiving continuous feedback from customers have provided significant improvements over the traditional waterfall (6 months to a year) delivery, like any groundbreaking, life-saving medicine, it came with few non-trivial side effects. The biggest potential victims of Agile are Quality and Technical Debt.Maintaining quality while delivering shippable software in a 2-4 week time period is an obvious challenge that most companies shifting towards Agile have to face. In a traditional waterfall model, software used to spend a large chunk of the overall delivery time in Quality Assurance. QA was a rather large centralized team that allocated resources to each project, which in turn went thru multiple iterations of testing, bug fixing, and re-testing. In the waterfall model, the software could not be released to production without an official QA signoff which means that all reported bugs have either been fixed, accepted by the business as working as designed or TANYA KRAVTSOV, DIRECTOR OF QA, AUDIBLEMHow to Go Fast and Not Get Buried in the DustIN MY View
< Page 7 | Page 9 >