Put your hand up if you work in product development Keep your hand up if you work in a team Keep your hand up if your manager would say you work in an Agile team Keep your hand up if, hand on your heart, the first defining adjective of your workflow agile The agile manifesto was written in 2001 by a diverse cadre of 14 middle aged white men in a Utah ski lodge. There's 4 points in the main statement and then there's 12 Principles that are kind of an add on. but the 4 main points are Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan The 3rd ones a bit odd to me, I guess it's more of a business to business thing, and I imagine the lawyers wouldn't approve of de-prioritising contracts too much. But the others I can get on board with. so take those 4 points, add 25 years and now Atlassian own an F1 team. But when most people get introduced to agile it is in the form of scrum, I've heard lots of people when they get started in this world they get the 2 ideas confused. But scrum has alot more than 4 philosophical points. They define a team a scrum master and a product owner and 2 layers of backlog and rituals with daily standups and biweekly reviews and retros and planning in sprints. Side note, I hate the term sprint. we want to work at an indefinitely sustainable pace, what's a good analogy for that, I know, Sprinting. But the scrum alliance claims to have accredited over 1.8 million people, scrum.org, claims another 1.2 million so that's alot of presence, but to me it kind of feels like it's flaunting that first agile point. They say that whatever individuals you have in your team this process is what you need. I think there are a couple of sides to the appeal of processes like that, that you can buy in. The positive side is that you're learning from other peoples lessons, this is industry standard, tried and tested, it must be good, the cynical side side is that if you buy in the process you can disclaim responsibility if it goes wrong. To embrace self-organisation is to take on the responsibility that brings with it and that is what I think spooks people. It becomes the test of the entire company and the individuals that make up that company and the way they interact. "Working software over comprehensive documentation." point, It's mirrored in the 7th of the 12 principles which is "Working software is the primary measure of progress." If your team progress is measured by story points or the number of tickets some other metric of Jira tickets, you're missing the point of an agile process. If you come across a small bug and your first thought is to create a ticket instead of just fixing it then you've ended up in a mindset where the process documentation is more important than the working software. This could spin me off on a whole tangent about how I hate the idea of being "data driven" but I try to stick to one rant at a time. Ultimately, if you are doing sprints and tickets and standups because someone has come into your team and told you this is the best way to work, you are not doing agile, you are recreating the original sin that birthed agile by putting conforming to the prescribed process before the people and the product. Agile is not the be all and end all of development, it's a philosophy, If you're not buying into those 4 points, at an organisational level, then figure out what it is you do value, and figure out what a process that supports that looks like, and if you find some way that works for your requirements, your products and your team mates, you may just find that the true agile was inside us all along.