Basic Agile Quality Practices
The aim of Agile quality practices is to ensure that cross functional teams produce outputs that meet the appropriate quality standards while creating customer value. According to Scaled Agile these practices encompass several elements:
⬅👈Shifting Learning Left: During the development process, teams encounter many unknowns that surface as they progress and learn new facts. Delayed learning can have a significant impact on the solution, resulting in rework and delays. Shifting learning left means that teams learn new information earlier in the process, identifying problems sooner and taking corrective action with minimum impact.
👨💻👩💻Pairing and Peer Review: Pair work involves two knowledge workers collaborating in real-time on the same asset. Peer review helps to identify quality issues as one team member examines the work of the other.
🙋♂️🙋♀️Collective Ownership and T-shaped skills: Collective ownership is a quality practice that enables any team member to access and update an asset. Quality standards ensure consistency, making it easier for everyone to maintain the quality of each component. T-shaped skills describe individuals who have deep expertise in one area and broad skills in others.
✅⚙Artifact standards and definition of done: To ensure that assets created and maintained by the organization add value to the business, they must adhere to standards. These standards may relate to how the artifacts are built or the properties they must manifest. Implementing productive artifact standards involves using a definition of done (DoD), which ensures that a work product is complete and correct.
🤖💰Workflow automation: Workflows often involve many manual steps, such as handoffs from one worker to another, searching for assets, and manual inspection of assets to a standard. Automation reduces execution costs and ensures adherence to standards.
#agilesoftwaredevelopment #innovation #quality