The Twelve Agile Principles
A 59 Seconds Agile Training Video
Continue to Part 4 Below
The Twelve Agile Principles
A 59 Seconds Agile Article
This article provides an ‘Introduction to the The Twelve Agile Principles‘ and looks to discuss what each or the principles are and what each principle means.
The Twelve Principles
The writers of the Agile manifesto agreed on 12 principles.
The first principle is ‘our highest priority is to satisfy the customer through early and continuous delivery of valuable software.’
The second principle is ‘welcome changing requirements, even late in development.’
The third principle is ‘deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
The fourth principle is ’business people and developers must work together daily throughout the project.’
The fifth principle is ‘build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.’
The sixth principle is ‘the most efficient and effective method of conveying information to and within a development team is face-to-face conversation.’
The seventh principle is ‘working software is the primary measure of progress.’
The eight principle is ‘agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.’
The ninth principle is ‘continuous attention to technical excellence and good design enhances agility’.
The tenth principle is ‘simplicity – the art of maximising the amount of work not done is essential.’
The eleventh principle is ‘the best architectures, requirements, and design emerge from self-organising teams.’
The twelfth principle is ‘at regular intervals, the team reflect on how to become more effective, then tunes and adjusts its behaviour accordingly.’
Continue Reading —> Next
The Agile Principles
A 59 Seconds Agile Video Animation
Continue Reading —> Next
User Stories Applied
A 59 Seconds Agile Book Review
User Stories Applied by Mike Cohn is one of our favourite books on Agile User Stories. The book starts with an overview into user stories, and details what a user story is and the different aspects of them. He then discusses how to go about writing a user story, and provides details of the INVEST criteria that can be used to determine if the story is meeting all of its objectives. Next Mike gives an in depth discussion of who user stories are written for and where to begin when gathering the details for them. The book then discusses acceptance testing user stories, including how to go about specifying these criteria and the responsibilities of the development team and customers during this process.
Continue Reading —> Next
The Agile Principles
A 59 Seconds Agile Infographic
Continue Reading —> Next
Agile Scrum Master Training Course
Our Favourite Agile Books
We found these books great for finding out more information on Agile Scrum:
Continue Reading —> Next
