Why you should learn about scrum/agile methodology?
Agile is a word that gets used very frequently in the IT software development world. However, more often than not, it is misunderstood by the most senior people in the industry and misused to put timeline pressures on the teams working on it.
The core use of the methodology is to focus on "non-negotiable" product value addition. Unfortunately, most of the industry leaders, team leaders and even thought leaders use it in the most destructive way. In this article, I want to explain the underlying meaning, the correct interpretation of agile, where to apply it and in which instances it does not work.
Before I explain my views on agile and how to "not abuse" agile, I am sharing the official scrum guide here which you MUST read for your knowledge. Because, agile is a mindset more than a methodology. One can only apply it in life or professional work environments if the underlying narrative and purpose is understood.
Let us try and deep dive into this topic further.
It is important to understand that agile is not a software industry concept. It is a concept that has its applications in the industry. Agile can be used in any industry, any project, any company provided it has the organisation support and intent to implement it.
The Meaning
Scrum/Agile simply means 2 things viz. product/commodity value addition at periodic intervals with high level flexibility and pivoting. It allows a team or a group of people to shift their focus on only 1 thing i.e VALUE. Remember, value is what your customer/user/stakeholder perceives. What is valuable today may change tomorrow or a month later. If something does not align to the value perceived, it loses value and users switch to better alternatives. Thats the core concept on which scrum is built. Value and adaptability to changing value perceptions.
How to determine if something can be implemented using agile?
First and the most important thing to determine is if the organisation you work in supports and respects scrum. You can easily find this out by speaking to a few other teams and their work style. Don't think of it as gossip. It is my way of getting to know the norm and align to the organisation culture. I have seen and worked in some organisation who embrace the chaotic culture 24x7 because thats their vision probably. If I would try to apply scrum at such places, I would fail and be frustrated. This is very similar to what jokes should you crack in other peoples houses. You check the culture and openess before you crack a joke right? This is a exactly that in a professional sense.
Secondly, remember that any creation can be in 4 stages i.e. Clear (known problems), Complication (known problems but solution discovery is required), Complex (unknown problems, experience on problems and likely solutions known) and Chaotic (unknown problems and unknown solutions).
Except in complex stage, no other stage is fit to use agile/scrum. If used, I would term it as ABUSE of scrum. I have seen a lot of teams trying to use scrum in chaotic stages where there are timeline pressures, constant changes in scope, new priorities arising almost on a daily basis and lack of governance. There have been times I have recommended leadership to use a more kanban style approach over scrum for a few months until the project moves back into the complex stage. However, some organisations have a rigid approach to prove that they AGILE but in reality they are not.
Instead of adding value in the deliveries, such projects end up being one of the slowest implementations. Remember, you need organisational culture to be agile and the creation of your product/commodity to be in a complex stage. Questions? Feel free to drop me a message.
When does Scrum NOT work?
There are multiple scenarios but I am listing down a few situations where scrum will not work.
Remember, in any industry your work, your ability to challenge status quo and asking "why" will take you to leadership levels faster. Of course, this has to be implemented with your individual work contributions. I have experience in my career so far that when I have asked questions, I have been able to change status quo and a bring a better version of the existing culture. Go ahead and learn more about scrum/agile mindset. If you can assess and apply it well, you can solve the most complex problems of your personal and professional life.
To remind, scrum/agile is about mindset first. Always!
I hope you found this read insightful.