Standards
Common principles, practices, and delivery guidance for building and operating high-quality software.
Engineering Standards
Audacia's engineering standards defines the standards that all engineers, including software engineers and test engineers, must follow when delivering software.
Project Delivery Standards
Audacia's project delivery standards defines the standards that all delivery managers, engineers, including software engineers and test engineers, business analysts must follow when delivering software.
- Delivery PrinciplesAudacia’s Delivery Principles define what good delivery looks like across successful client engagements. They are intentionally engagement-agnostic, applying across consultancy, TechOps, fixed-price delivery, T&M, minimum commitment, out...
- Work Item Estimation GuidelinesThis document outlines:
- Raising Bug CardsThe aim of this document is to provide a set of standards for Audacia to define bug cards, such that issues can be communicated clearly and work can be tracked effectively. There may be other standards for specific clients or third-parti...
- Requirements Refinement ProcessThe process for defining and refining requirements will vary by project, but in terms of how a typical project might operate:
- Sprint Demos GuidelinesThis document provides a set of standards relating to sprint demos which apply to people of all job roles.
- Sprint Retrospective GuidelinesThis document outlines how to run effective sprint retrospectives.
- Sprint Reviews GuidelinesThis document outlines a basic structure and best practices for running sprint review meetings and applies to people of all job roles.
- Daily Standup Meeting GuidelinesThis document provides a set of standards relating to standups which apply to people of all job roles.
- Writing Acceptance Criteria (AC)Acceptance criteria define the conditions that must be met for the software to be accepted by a user or stakeholder.