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



Labels:

Comments

Post a Comment

Popular posts from this blog

Brand New programming language and one solution OR …

Brand New programming language and one solution OR Two existing programming languages, one solution for EACH? I understand that there is no right or wrong. It all depends on your software architecture, team structure, team skills and other factors, but I still want to explain the scenario as it may look familiar to some. Let me explain. Let’s assume that you have microservices and common libraries in two major programming languages. You have some teams who are experts in one and some teams experts in the other programming language. Now you need to come up with a solution for a scenario that all teams will need to leverage. Let’s assume that your cloud platform has an off-the-shelf approach for this but it is supported by a 3rd programming language that your teams do not have much experience in. What is the right thing for your organization and not just from the technical point of view? A) Do you embrace what your cloud platform gives you off the shelf and implement thi...
Post a Comment
Read more

10,000 foot level view in technology

10,000 foot level view in technology: How useful is it? What can be done at this level? If the 30,000 foot level is the CTO level, then consider the 10,000 foot level as the level that software engineering managers and directors operate at. To achieve the success at 10,000 foot level, you as a software engineering manager need to dive deep into technical details, help the team lay the foundation from BOTH organizational and technical side. It is the little moves that get the team to this level. Once the team’s applications and results at that level, then you as a manager have ability to perform the high level analysis and troubleshooting without necessarily being in code on daily or weekly basis. Therefore, your ability to troubleshoot technical issues at the 10,000 foot level is a testament to the great work of your team. Go TEAM !! Almir Mustafic
Post a Comment
Read more

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
Post a Comment
Read more