Uncovering the Truth About Fake Agile: Why It’s Harmful and How to Address It

Umar Nasir
Agile Insider
Published in
3 min readFeb 1, 2023

Examining the reasons for Agile’s ineffectiveness in some companies and the implications of staying silent, and offering solutions for genuine Agile implementation

https://marketoonist.com/2018/05/being-agile.html

Everyone is thinking that the Agile methodology, which is supposed to make software development more efficient and effective, is not always being implemented in a genuine way. Instead, some companies are going through the motions of Agile without truly embracing its principles. This is often referred to as “fake Agile.”

One supporting point for this claim is that Agile requires a high degree of collaboration and communication among team members, but in many cases, teams are still siloed and decisions are still made by a small group of managers. This undermines the basic principles of Agile and make the process ineffective.

No one is saying anything about this because speaking out against a company’s approach to Agile can be seen as criticizing management and could lead to negative consequences for the employee. Additionally, many employees may not have a clear understanding of what genuine Agile looks like and may not realize that their company’s approach is fake.

Another supporting point is that Agile is often seen as a panacea for all software development problems and there is a lot of pressure on companies to adopt it. So, even if a company’s Agile implementation is not genuine, they may still be able to produce results that are good enough to keep stakeholders happy.

If people continue to stay silent about fake Agile, the future implications are that software development will continue to be less efficient and effective than it could be. Companies will continue to waste time and resources on meetings and ceremonies that don’t lead to real progress.

On the other hand, if we bring attention to this issue and encourage companies to truly embrace Agile principles, the world would be different in a positive way. Software development teams would be more productive, and companies would be able to deliver better products to their customers. Additionally, employees would be more engaged and satisfied with their work, leading to a more positive work environment.

Here are some clear steps that can be taken to resolve the issue of fake Agile:

  1. Start by educating yourself and your team about the principles of Agile and what genuine Agile implementation looks like. This will help you to identify if your company’s approach is fake.
  2. Communicate with your team and management about the issues you are facing with the current approach to Agile. Share your concerns and offer suggestions for improvement.
  3. Create a culture of transparency and open communication within your team. Encourage team members to speak up if they see something that is not in line with Agile principles.
  4. Encourage management to invest in training and coaching to help the team understand and adopt genuine Agile practices.
  5. Implement Agile practices incrementally, starting with the most important ones and then building on them over time. This will help the team to become comfortable with Agile and will make the transition smoother.
  6. Continuously monitor and measure the progress of your Agile implementation and make adjustments as needed.
  7. Finally, encourage the team to continuously reflect on their work and find ways to improve, this will help them to adopt a continuous improvement mindset that is essential for Agile methodology.

References

R. Prikladnicki, C. Lassenius and J. C. Carver, “Trends in Agile: From Operational to Strategic Agility [Practitioners’ Digest],” in IEEE Software, vol. 36, no. 1, pp. 95–97, Jan.-Feb. 2019.
doi: 10.1109/MS.2018.2875649
URL: http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=8611452&isnumber=8611443

T. Dingsøyr et al., “Key Lessons From Tailoring Agile Methods for Large-Scale Software Development,” in IT Professional, vol. 21, no. 1, pp. 34–41, Jan.-Feb. 2019.
doi: 10.1109/MITP.2018.2876984
keywords: {Planning;Software management development;Scrum (Software development);Organizations;Proj

--

--

Umar Nasir
Agile Insider

A seasoned project manager with a proven track record. Loves mentoring and sharing project management knowledge