Practices to Bring Agile Principles to Life

This is work in progress! in it’s first increment this page aims to provide guidance, you’ll have to do your own research! the aim is in the coming increments I will add links to resources that you can access directly from here.

1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

1. Incremental Development

2. Frequent Releases

3. Customer Reviews and Feedback

2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

1. A Prioritised Backlog

2. Prototyping

3. Short Iterations

3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

1. Definition of "Done"

2. Work-in-Progress (WIP) Limits

3. Automated Testing

4. Business people and developers must work together daily throughout the project.

1. Co-located Teams

2. 1-2-4-All

3. Cross-functional Teams

5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

1. Team Charter

2. Empowerment

3. Safe Environment for Feedback

6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

1. Co-located Teams

2. White boarding Sessions

3. Pairing

7. Working software is the primary measure of progress.

1. Definition of "Done"

2. Acceptance Criteria

3. Technical Debt Management

8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

1. Regular Retrospectives

2. Sustainable Pace of Work

3. Burn-down/Burn-up Charts

9. Continuous attention to technical excellence and good design enhances agility.

1. Code Reviews

2. Refactoring

3. Regular Tech Talks

10. Simplicity, the art of maximising the amount of work not done is essential.

1. Product Experimentation

2. Prioritisation Techniques

3. Visual Management Tools

11. The best architectures, requirements, and designs emerge from self-organising teams.

1. Team Autonomy

2. Cross-functional Teams

3. Encourage Ownership (Pull Vs Push)

12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.

1. Regular Retrospectives

2. Data Driven Continuous Improvement

3. Physical Improvement Board