4. Agile is a time boxed, iterative approach to software delivery that builds software incrementally from the
start of the project, instead of trying to deliver it all at once near the end
What is agile?
12. *There are some prerequisites required!
• “Individuals and interactions over processes and tools”
• It’s a team effort (Companies with large fragmentation like big enterprises have difficult time getting
this right)
• Nonobvious people/departments should be onboarded as well
• It is not about faster – its about more aligned and less wasted
Does Agile work?Yes if done right*
16. Business issue: Need to reorganize as competitors are moving faster and we are unable to keep up
Operations: Get the consultants and let’s adopt agile practice/framework
Department: Unable to ship on time and what is expected.This is development things so let's sort it out
first
Let’s transform the delivery
17. Prick and Bill
Prick
• “People skills” – Talk to business, set
expectations and deadlines
Bill
• “Efficiency” – Ensure team is
delivering to Pricks promises, make
sure team is doing effective
18. Prick and Bill cycle
Set
unrealistic
expectations
Micromanage
Get most
experience
person for
reporting
Fail
What happens when you force organization rather then allow to self organize
Why some companies are more successful in getting agile principle and some of them struggle even with the help of best coaches or consultants
It looks just development piece here -> make your software in pieces but faster and then we sell (deploy does not practice push into production)
Waterfall has clear responsibility boundaries, agile does not, where is accountability?
If done properly you can start getting some business value earlier than waiting till the product is complete – even without functionality you can start verifying deployment, resiliency and other items as the capability builds out
From general point of view you cannot “buy” agile – every company has its own processes that have their own nuances and people
Individuals and interactions over processes and tools – points to self organization as it rather relies on people than processes
Why do sometimes making change fails?
Bill Lumbergh
Both items are very closely related
If you look Test, deploy is done over and over, thins is where test automation and DevOps come in. It becomes a super important roles!
If you don’t trust your people or teams you got bigger issues than just Agile not working
Dev team is a blend of required engineers: Developers, Tes engineers, Devops, Security