The Agile Manifesto started it all for me!

welcome to the podcast that challenges you

After a couple days of snow, we had here, we were snowed in a little bit, just a little bit of ice, and it's just after Thanksgiving in 2020 during the pandemic, I got to spend some time with my family, but not too big of a family cause we social distance and not too close to people just being after Thanksgiving. And I do have a lot to be thankful for. I'm thankful for my family. I'm thankful that I'm healthy and thankful that I live in the United States and a free country.

And I am thankful that I get to do this podcast and have some wonderful listeners such as you. So today's episode is just simply going to be me, me reading something called the agile manifesto or the S the manifesto for software development. Many of you out there may be familiar with this many may not, but I want to do this episode because I think it's very important that everyone understand what agile is built upon the foundation and the foundation for this podcast.

As you know, it's the behaviors, the mindset behind agile. If you're not doing changing the mindset and just changing the processes by doing scrum, XP, Kanban, whatever process, methodology of agile you're following, you're not truly doing scrum. You're, I'm sorry . You're not truly doing agile. You're doing agile. And this podcast is all about being agile. You got to combine the two, so I'm just going to simply be reading this.

If you're interested in a further dive into it, I will be doing a second podcast where with commentary, where I will be dissecting it, breaking it down, talking about each value and principles. There's two sections is the values and principles section. I'll be reading both here today. And actually a few years ago, when I used to do a class at a company, I would do a basic and an advanced agile class. And I always started off with this reading, the manifesto, the values and the principles.

And we did an exercise with the class. We spent a good 30, 45 minutes, depends on how big the class was talking through this. And each , uh , they would partner up , uh , the attendees. They would partner up and they would pick a principle and we would dissect it. We would talk about, are they applying it in their current role? If not, how can they, and what value does it add? That's the main part. That's the main part. Does it add value? So

They published the software for agile, the manifesto for agile software development. So now the first I'm going to read is the values. And the second I'm going to read their principles and then I'll close the podcast. And again, if you're interested, I'll do one with commentary,

Through this work, we have come to value individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration, over contract negotiation, responding to change over following a plan that is while there is value in the items on the right, we value the items on the left more Principles behind the agile manifesto. We follow these principles.

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

Even late in development, agile processes, harness change for the customer's competitive advantage, deliver working software frequently from a couple of weeks to a couple of months, with a preference to the shorter timescale Business, people and developers must work together daily throughout the project, Build projects around motivated individuals, give them the environment and support they need and trust them to get the job done.

The most efficient and effective method of conveying information to and within development team is face to face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors developers and users should be able to maintain a constant pace indefinitely, Continuous attention to technical excellence and good design enhances agility, simplicity. The art of maximizing the amount of work not done is essential.

The best architectures requirements and designs emerge from self-organizing teams at regular intervals. The team reflects on how to become more effective than tunes and adjusts its behavior. Accordingly. That has been this episode of the agile within I've read the agile manifesto values and principles. Hope you've enjoyed it again. I will be doing another one on commentary. If you're interested in that, that should be coming up shortly here, hopefully following this episode.

So thanks for joining again. Thanks for listening as always. If you want to review me on iTunes, all the other podcasts that I'm on out there, please review me. I'm on Google, Amazon, Stitcher, Spotify, all the big ones. Review me there. Reach out to me through social media, Twitter at the agile, within my website, the agile within.com Facebook, the agile within and email me gregMiller@theagilewithin.com with comments, suggestions, questions I'll read through them.

If you have any suggestions for the show as always, please let me know. I'm always looking for suggestions. If you'd like to be on the shell on Vita, on the show too , to talk about that. I'm looking for guests as well. So thanks for joining hope. You've enjoyed it. This has been the agile within where we help you be more