Agile implemented wisely is simple, effective, powerful
A written statement that describes the policies, goals, and opinions of a person or group
The Agile Manifesto was created on February 11-13, 2001, in Utah. Seventeen wise people met over two days to discuss software, along with skiing. This was a very important event in the history of mankind because it changed the way software development would be done forever.
One of the outcomes of this event was the Agile Manifesto. This Manifesto consists of Four Values and Twelve Principles.
Our work should ideally be driven by the Agile Values and guided by the Agile Principles. What are these values and principles?
As we continue to work from moment to moment and throughout the day, it’s a good idea to keep the four values on our fingertips and the twelve principles at the back of our mind. When we strike a conversation, collaborate with a colleague or team member, meet stakeholders, facilitate or participate in the Agile ceremonies, our choices should reflect the Agile Values. Our behaviors, intentions, body language, tone of voice should reflect the principles.
As an example, you had an important question related to complex software development for a colleague. You had a choice of instant messaging (Slack), emailing, or walking over to their cube for a quick chat. Your choice of going over and meeting them face to face, despite exerting a bit more physical effort than the first two options, reflects a deeper understanding of the Agile Values, a passion for manifesting them in your actions and creating warmth by bonding with another team member at the same time while resolving work.
Another example: While facilitating the Daily Standup with the new team that is rebellious towards scrum ceremonies, reach out with compassion to listen to them, coach them and meet them where they are while slowly bringing them to participate actively in the Daily Standup.
Let’s take a closer look below to the actual Values and Principles as documented in the Agile Manifesto:
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done
Continuous attention to technical excellence and good design enhances agility
Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation
Simplicity – the art of maximizing the amount of work not done — is essential
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale
Working software is the primary measure of progress
he best architectures, requirements, and designs emerge from self-organizing teams
The business and developers must work together daily throughout the project
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly
Subscribe to the Agilonomics Newsletter and Claim Your Free Power Team Consultation Today!
We promise to keep your email address safe. You can check our Privacy Policy.
You’re almost there! Please check your email and click the confirmation link to complete your subscription. If you don’t see the email, be sure to check your spam folder.
