The impetus for exploring and eventually adopting agile methodologies typically originates from within development. After all, agile was artfully branded as a development methodology created by developers for developers.
Yet, despite the benefits (and the sociology) of agile development practices, the “business” only cares about one thing: make my business requirement work. Of course, this goal actually involves three very crucial elements:
- Implement my business requirement.
- Make it work as the business expects it to work.
- Deliver it on time.
The point here is this: Without a robust strategy for agile quality that effectively meets the demand of the business, the most agile of agile teams will remain benched.
To get the ball rolling in the right direction, we've aggregated 10 tips for development and scrum managers to consider while evolving more iterative development methodologies, and we're going to present them in the next 10 blog posts. These tips are designed to help you extend well-known agile quality practices to ensure that your software satisfies business needs—effectively and efficiently:
- Extend Quality Beyond QA
- Embrace Policy as a Team
- Use Automation to Catch as Many Errors as Possible before QA
- Continuously Evolve Your Quality Policy in Response to Defects Detected
- Manage Code Complexity
- Extend TDD and Functional Tests with Automatically-Generated Regression Tests
- Reduce Developer Testing Complexity
- Reduce End-to-End Testing Complexity
- Re-Test Only as Needed
- Use Automation to Optimize Stand-Up Meetings
Want to learn more about Agile quality? Get our Agile Quality Starter Kit.
Photo credit: quapan