Agile, testing and more frequent deliveries.

Yet another time I think I see people using word Agile wrong. Yet another guy claimed "we need to have more predictability and stability so I think we would go for Agile methodologies, Scrum in particular".

Nonesense.

I don't think that "predictability, stability, whatevershitability" has anything to do with Agile. If you start Agile transformation with such goal you've already failed.
Agile is about maximizing value delivery rate in a state of uncertainty, that's pretty much what it is.

If your business is uncertain as hell why do you think that "predictability" with engineering teams is going to fix things? It is not.
Worse, if you make engineering teams predictable while having unpredictable environment, you will miss the whole point and make things worse while still thinking you're doing fine.

Nonesense.

Agile team is about removing management layers between engineering and customer, not making management happier.

Having an ability to communicate with customer we can deliver features customers think they need faster.

Having an ability to communicate with customer we can validate if what we built really can solve customer problem.That also would mean we don't have to kill ourselves testing feature we are not yet sure 100% needed.

Understanding that testing something we are not yet validated with customer is a waste is a real reason why we can release more often. Why would you spent much time testing feature that may be removed next release?

Test automation plays much smaller role in Agile.
Jira dashboard plays much smaller role in Agile.
Predictablity plays much smaller role in Agile.

Adaptability and communication are the keys.

Comments

  1. That's great article and the ones who doesn't have clear idea about Agile.

    ReplyDelete

Post a Comment

Popular posts from this blog

Test automation framework architecture. Part 2.2 - Two-layered architecture

Test automation framework architecture. Part 2.1 - Layered architecture example

Test automation framework architecture. Part 2 - Layered architecture