Skip to Content

Changes for page Agile Manifesto

Last modified by chrisby on 2024/05/20 08:49
From version 1.11
edited by chrisby
on 2023/11/11 15:04
Change comment: There is no comment for this version
To version 1.10
edited by chrisby
on 2023/10/20 19:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -36,4 +36,16 @@
36 36  
37 37  ### The 12 Principle
38 38  
39 -Additionally, there are [twelve principles](https://agilemanifesto.org/principles.html) for further guidance.
39 +Additionally, there are [twelve principles](https://agilemanifesto.org/principles.html) for further guidance:
40 +
41 +* Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
42 +* Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
43 +* Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
44 +* Business people and developers must work together daily throughout the project.
45 +* Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
46 +* The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
47 +* Working software is the primary measure of progress.
48 +* Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
49 +* Continuous attention to technical excellence and good design enhances agility. Simplicity, the art of maximizing the amount of work not done, is essential.
50 +* The best architectures, requirements, and designs emerge from self-organizing teams.
51 +* At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.