Showing posts with label Agile. Show all posts
Showing posts with label Agile. Show all posts

Oct 19, 2022

Operation Hates Agile

Operation hates Agile. Why?

Simply because Agile is supposed to be moving fast and keep breaking things (for improvement).  With the fast pace of changing (in DevOps), it is impossible to get a stable and predictable metrics for operation teams.

Audit is another entity that similar to operation which hates Agile. 😜 Because by the time audit team finish the report, DevOps is already making 38 changes. 😅 

Conclusion, Agile is supposed to replace traditional operation, change management, and even audit.  

Question is, does the top management has the courage to replace the traditional operations (change management, audit) with Agile?

So if you want a successful Agile in your company:

Apr 4, 2021

"Why you'll probably never see Agile development in the real world"

This video explains very well about the difference between Agile and Scrum. 


Notes:

  • 6:33 - .... what we want is flexibility, the whole point of Agile is to get agility. I n another words, what we want is we want to quickly adapt to changing requirements, be those changes coming from inside or outside.
  • 6:53 - .... so I suppose the one thing that I will agree with the Agile skeptics about is that, I think the vast majority of large companies cannot ever be Agile because it is the very nature of those large companies to not be flexible about things in flexibility. 

Feb 14, 2021

Is Agile a FAILED Approach?

Is Agile software development a failed approach or is it an important advance?

Discussions of agile methodology and agile philosophy often get bogged down in discussions of practices: 

  • “Is Scrum better than Kanban”, 
  • is “SAFe or Less the way to scale-up”, 
  • “Is agile certification a good route to success or a money-making scheme for the trainers?”. 

In this episode, Dave Farley attempts to demystify agile thinking. What is the idea at the heart of agile thinking that made it definitively win the “waterfall vs agile” contest? Why is the idea of “post-agile” a misunderstanding of the step forward that the move to agile software engineering means for software development?


 My take is:

  • Agile should be used for unpredictable result, such as learning and discovery.
  • Waterfall approach is for more predictable result, such as scale up.

If Agile is used just because of predictability, then it is being used irrational, and have no difference than waterfall approach.