Principles behind the Agile Manifesto
1.) Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software — CI/CD (Continuous Integration and Continuous Delivery) Pipelines helps us achieve this. One can use multiple
2.) Welcome changing requirements, even late in
development. Agile processes harness change for
the customer’s competitive advantage. — Team, Scrum Master, Product Owner and Client should closely work with each other so that client can intimate the changes as soon as possible and (Team, Scrum Master) can adopt the changes quickly.
3.) Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale — Integration and Deliver Pipelines should be effective enough so that customer can see the interactive and integrate version frequently.
4.) Business people and developers must work
together daily throughout the project — Team, Scrum Master, Product Owner and Client should closely work with each other so that Client can intimate the changes as soon as possible and (Team, Scrum Master) can adopt the changes quickly.
5.) Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done — Team should comprise of Enthusiastic person so that they pro actively develop the application and Scrum Master, Product Owner and Client should support the team to get necessary tools, frameworks which can increase the productivity and efficiency of the team.
6.) The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation — Workshops , Interviews, Daily Scrum Calls and Video Chats between Team, Scrum Master, Product Owner and Client helps us understand the product and it’s outcome better.
7.) Working software is the primary measure of progress — Measurement unit is considered to be delivered user stories to the client with acceptance criteria.
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 of the Team, Scrum Master, Product Owner and good design enhances agility.
10.) Simplicity — the art of maximizing the amount
of work not done — is essential.
11.) Self-organizing teams — 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.
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Principles behind the Agile Manifesto was originally published in DXSYS on Medium, where people are continuing the conversation by highlighting and responding to this story.
