What is Agile? Really ?
An agnostic and objective introduction
Agile is a set of 4 values and 12 principles that give people, teams and organizations a foundation that will help them to make decisions that result in better software development, products and services delivering a high-quality customer experience and satisfaction as well as providing a better world of work with satisfying stakeholders & employee experience. Agile is NO Methodology nor Framework. We hope these values and principles, however, will enable you to create what’s best for organizing your work for a better and smarter future!
Inspiration of this definition by Mike Beedle and Mark Shead.
7 basic things agilist and new adopters should know!
Extracted, inspired and enhanced from an inspirational article from Jason Little here:https://www.linkedin.com/pulse/6-things-everyone-needs-know-agile-jason-little
Adapted & Enhanced by Alexandre F Joly, the Agile Scrum Lounger. Let’s connect! Want more of these Blogs/ Vlogs? Subscribe here!
There are some basics you absolutely need to know about Agile. So, go ahead, on the beach, at a park or near your fireplace and go through those reading that would give you the objective agnostic definition and idea of what is Agile and should spark your mind to become a catalyst of agility at your work place.
The world of work isn’t changing, its transforming by adapting to new generation of people in the work force, to new mindset of user and customer experience and to new ways of doing business (#H2H) and creating product, services and solutions via product management #NOPROJECTS!
Let’s start your agile journey on the right foot. Shall we People? Ready to Dare Real Agile ?
Section One: The Sources
1) The Agile Manifesto: http://agilemanifesto.org Go read it, even read it in your own language, available in 80+ languages.
Read the history of why, and how, it came to be. Oh, and don’t skip the principles.
Then listen to Agile Uprising’s interviews of 13 of the 17 Manifesto signatories. Mike Beedle was my Mentor and Coach who died in a tragic event in Chicago last March 23rd.
2) The Scrum Guide: http://scrumguides.org Jeff Sutherland and Ken Schwaber created Scrum in 1993/1995 (depending on whom you want to believe, even though Jeff started to pick some ideas from Computer Programmers since 1986) and they don’t hate each other anymore so The Scrum Guide has been consolidated after they split their efforts between Scrum Alliance and Scrum.orgScrum easy to understand really hard and disruptive to put into action, however very feasible: See it here: https://www.scrumalliance.org/about-scrum/overview
3) Kanban: Read Kanban: Successful Evolutionary Change for Your Business by David Anderson. He was the first to write about using Kanban in software. While you’re at it, read Personal Kanban by Jim Benson, the arguable creator of Kanban.
4) DevOps : Read What is DevOps : Infrastructure as code from Mike Loukides provides an incisive look into this new world of operations, where IT specialists are becoming part of the development team as results of almost 20 years of Agile and Lean Software development. In an environment with thousands of servers, these specialists now write the code that maintains the infrastructure. Even applications that run in the cloud have to be resilient and fault tolerant, need to be monitored, and must adjust to huge swings in load.
Section Two : The Practices
5) Extreme Programming: Read Extreme Programming Explained by Kent Beck, then watch Kent Beck’s ’20 Years Later’ talk on XP. While you’re at it, read about the C3 project whom become famous as the ‘birth project’ of Extreme Programming.
6) “Agile Testing” – Read Brian Marick’s original post here, and Lisa Crispin’s awesome refresher here. I put ‘Agile Testing’ in quotes because testing is a team sport. Don’t use this as a way to make your testers agiler,that’s just dumb! Literally. Oh, and Grammarly said, yes to use ‘agiler’ instead of ‘more agile’.
Section Three: The Thinkers & Sparkers
7) Read everything by Jerry Weinberg. Who sadly, just passed away on August 7th 2018 RIP Well, that might take a lifetime, so start with these. Just about everyone who’s considered to be an ‘agile thinker’ (whatever that means) has been influenced by Jerry in one way or another. It does for me, on top of Mike Beedle and Steve Denning. Will talk more about them after you’d tried some sprints with a certain satisfaction!
Honorable Mention: Look up the Manifesto authors in your spare time. These guys compromise in 2001 to make us moving onward in togetherness!
Why Write This and share it to my trainee, coachee and clients?
More and more people are getting introduced to Agile in big corporate settings via big frameworks and have no idea what the history of Agile is and that what hit them is only based on «opinion» flavored by some conartist!
As your coach I want you to have the facts and more over the best experience for you and for you to provide the best to your clients and users.
To enhance the human experience!
Also, instead of talking about me in my experience as your newly coach, I just reassured you of my path that went through those 7 things on this list and they are foundational in nature, table-stakes if you will. If someone haven’t heard of them, you sure as hell shouldn’t be coaching a team or organization on Agile. I do and I can.
There’s certainly nothing wrong with the glut of methods/tools/processes/frameworks that have been invented since 2001, albeit those are not the places to look first.
Most of us old dogs moved on from Agile years ago, but now that the rest of the business world is catching up, we’ve had to make Agile modern, take Agile back, and Rise Up against the evil corporations who seek only to monetize Agile, or use Agile to beat their teams into submission. I am here, with you and with passion to prevent this to happen to you, if you wish to innovate!
So voilà! Hope you’ll enjoy this introduction. I won’t write any other LONG email I will go back to my Agile principles of meeting you face to face.