Skip to main content

Challenge the person that tells you “We don’t really do agile here”

How many times did you hear somebody say “We don’t really do agile here”.
What does that even mean? First, the word “agile” is not a noun and you can’t do “agile”. We all forget this and we all get caught using the word “agile” as a noun.
The Agile Manifesto is very good, and how some of the organizations that promote scrum approach interpreted that manifesto is just one way of looking at it. I understand why these organizations worked on converting the word “agile” from adjective to a noun. It is because you can sell nouns and you can’t sell adjectives. Think about the overall industry that is built around training people on agile methodologies and all the certifications. I have nothing against these organizations writing books and providing courses on this matter. That is all good. I encourage everybody to learn and get exposed to different types of opinions and interpretations. You can treat all that available material on agile methodology as case studies. We all know that case studies are taken, absorbed and then you decide for yourself and for your organization what works for you.
You and your organization really need to go back to basics and roots. Go back to that Agile Manifesto, print it in huge print and post it on your walls. Then take all that knowledge from scrum master certification courses, SAFe courses and define for yourself what that manifesto really means to you. It may mean that you start with a very simple approach; for example, you could start by doing the following:
  • * Analyze at the end of your sprint: Just find one thing that you would want to improve.
  • * Improve it during the next sprint and acknowledge that small win.
  • * Repeat the process and get that much closer to higher level of agility.
Your organization has a lot of smart people who are passionate about increasing agility because the word “agile” lost its meaning. You can create a committee of these smart individuals and have them exposed to all the training material on the agile methodology and then bring them back into the room and work on how you can translate the Agile Manifesto into a very achievable and short list of guidelines (not rules) for your company that you can evolve from iteration to iteration.
Let me just leave you with one simple advice. Please make sure that the items on the RIGHT side of the manifesto do not weigh more and tip over the scale to the right side.
Thank you for reading this article. You can follow me here and you can also find my articles on SoftwareEngineeringBlogger.com and my personal site almirsCorner.com
Almir Mustafic



Comments

Popular posts from this blog

Daylight saving time and A Software Engineering state of mind ?

You may be wondering what the Daylight saving time has to do with a software engineering state of mind. When thinking about writing this article, at first I thought to start with the following joke and I am: “ Did you know that the Daylight saving time was started because a software developer coded a function that does smart timezone and configurable calculations and then this developer created a problem to solve to use the algorithm; hence, the Daylight saving time was born. ” This is a joke, but  on a more serious note , this brings me to a state of mind in software engineering that make this joke a reality to some degree. How many times did we find ourselves in situations where we learned something new in programming and we looked for ways to apply it at any cost? How many times did we see a cool new feature from a creator of a framework and we decided to use it even though that was not the right solution for the problem or maybe there was no problem to solve in the ...

Leaders/Mentors in my life

I have been blessed in my software engineering career with great leaders. Some of them challenged me in technical skills. Some of them challenged me in my organization and leadership skills. Some of them challenged me in both. And all of them made me a better software engineer, a better senior engineer, a better solutions architect, a better teammate, and a better leader. If you are a student, find yourself a mentor. If you are a junior software engineer, find yourself a mentor. If you are an experienced software engineer, find yourself a mentor. Remember, you write your own definition of success and you are your own critic. That may mean that you TRY to perfect every stage of your career, or that may mean that you skip some stages in your career. Remember, you are in control. That’s all I wanted to say today :) Keep geeking out. Almir

OWNING your sandbox

OWNING your sandbox. As software engineers we all like to work on latest technology and coding new applications. People generally don’t like spending a lot of time maintaining the code. However, in the world of microservices the owners of each microservice are very well known and defined unlike in the world of monolithic applications. That means that you own it in the true sense. You own the code. You own the QA environment. You own the Stage environment. You own the production environment and all the errors that come along with it :) On positive note, you have a lot to be proud of and you can turn it into opportunities :) You own something that is contributing your company’s customers and what you do responsibly affects the lives of many people in a positive way. Almir Mustafic