mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 02:54:26 +00:00
Environment TestandClaude Sonnet 4.6
6d1f7781c1
Move Agile Manifesto principles out of design/principles.md into a dedicated organisation/principles.md so code and process concerns live in separate files. Move communication.md into the same directory for consistency. Add SRP to design/principles.md. Add cross-references between the two principles files. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2.9 KiB
2.9 KiB
Organisational Principles 📐
These principles govern how teams collaborate, plan, and deliver work. For code design principles, see principles.md.
Principles 📋
Follow these principles. Keep the rule column short, imperative, and as SMART as practical; use the reason column for the rationale, the principle column for the linked source name, and put the expanded wording in the details column.
| Rule | Reason | Principle | Details |
|---|---|---|---|
| Ship the first valuable increment early. | Early value shortens feedback loops. | Agile Manifesto | Deliver working software as soon as it is useful and keep delivering value continuously. |
| Accept useful requirement changes. | Better ideas can arrive late. | Agile Manifesto | Treat late requirement changes as normal when they improve customer value. |
| Release working software frequently. | Frequent delivery surfaces issues sooner. | Agile Manifesto | Keep iterations short enough that users see working software at regular intervals. |
| Work with business daily. | Daily contact keeps intent aligned. | Agile Manifesto | Keep business and development in daily contact for decisions and feedback. |
| Trust motivated people. | Engaged people take better ownership. | Agile Manifesto | Build around engaged people and give them ownership of the work. |
| Use direct conversation for blocking topics. | Direct talk resolves blockers faster. | Agile Manifesto | Prefer face-to-face or synchronous discussion when the decision is urgent or complex. |
| Measure progress with working software. | Working software shows real progress. | Agile Manifesto | Use running software, not documents alone, as the main progress signal. |
| Keep a sustainable pace. | Sustainable pace avoids burnout. | Agile Manifesto | Set a pace the team can maintain for the long term. |
| Improve technical quality continuously. | Quality debt compounds if ignored. | Agile Manifesto | Invest in design and code quality on every change. |
| Remove unnecessary work. | Removing work leaves room for value. | Agile Manifesto | Choose the smallest solution that achieves the goal. |
| Let teams shape their own design. | Local teams know the best design. | Agile Manifesto | Let self-organizing teams own architecture, requirements, and implementation. |
| Inspect and adapt regularly. | Regular review catches process drift. | Agile Manifesto | Review the process at regular intervals and change it when it is not working. |