Re:Agile at 20: The Failed Rebellion
by mirekrusin on Sunday July 25, 2021 @03:14AM
(#27947402)
I don't think agile was meant to take everything client says without critical thinking. Quite opposite actually, it encourages dialogue. Often developers know better how to solve certain problems.
Early in my career somebody said something like "make sure you distinguish between <<what they (customers) want>> and <<what they need>>.". This thought stuck with me for years and in my opinion has been reposible for success I witnessed.
It's important to unwrap "what they want" so you, as developer, can apply more first principle thinking to arrive at "what they need".
BAs have tendency to project their own solutions, however when unwrapped so you see the problem that needs solving, you may arrive at solution that is simpler (like orders of magnitue is not that rare in my experience), reflects reality better, takes advantage of somehow hidden from BAs PoV system internals etc.
Agile enouraged dialogue is the platform where those ideas can surface.
Early in my career somebody said something like "make sure you distinguish between <<what they (customers) want>> and <<what they need>>.". This thought stuck with me for years and in my opinion has been reposible for success I witnessed.
It's important to unwrap "what they want" so you, as developer, can apply more first principle thinking to arrive at "what they need".
BAs have tendency to project their own solutions, however when unwrapped so you see the problem that needs solving, you may arrive at solution that is simpler (like orders of magnitue is not that rare in my experience), reflects reality better, takes advantage of somehow hidden from BAs PoV system internals etc.
Agile enouraged dialogue is the platform where those ideas can surface.