Home

Agile Manifesto

www.agilemanifesto.org

  • Individuals and interactions over processes and tools

  • Working software over comprehensive documentation

  • Customer collaboration over contract negotiation

  • Responding to change over following a plan

we follow these principles:

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

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

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

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

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

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

  7. Working software is the primary measure of progress.

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

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

  10. Simplicity—​the art of maximizing the amount of work not done—​is essential.

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

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

Manifesto for Software Craftsmanship

http://manifesto.softwarecraftsmanship.org/

  • Not only working software, but also well-crafted software

  • Not only responding to change, but also steadily adding value

  • Not only individuals and interactions, but also a community of professionals

  • Not only customer collaboration, but also productive partnerships

  • That is, in pursuit of the items on the left we have found the items on the right to be indispensable.

Google Philosophy

https://www.google.com/intl/en/about/philosophy.html

  • Focus on the user and all else will follow.

  • It’s best to do one thing really, really well.

  • Fast is better than slow.

  • Democracy on the web works.

  • You don’t need to be at your desk to need an answer.

  • You can make money without doing evil.

  • There’s always more information out there.

  • The need for information crosses all borders.

  • You can be serious without a suit.

  • Great just isn’t good enough.

Zen of GitHub

http://ben.balter.com/2015/08/12/the-zen-of-github/

  • Responsive is better than fast

  • It’s not fully shipped until it’s fast

  • Anything added dilutes everything else

  • Practicality beats purity

  • Approachable is better than simple

  • Mind your words, they are important

  • Speak like a human

  • Half measures are as bad as nothing at all

  • Encourage flow

  • Non-blocking is better than blocking

  • Favor focus over features

  • Avoid administrative distraction

  • Design for failure

  • Keep it logically awesome

Gov UK

https://www.gov.uk/design-principles

  • Start with needs*

  • Do less

  • Design with data

  • Do the hard work to make it simple

  • Iterate. Then iterate again.

  • This is for everyone

  • Understand context

  • Build digital services, not websites

  • Be consistent, not uniform

  • Make things open: it makes things better