Rimantas Benetis: Agile – Can you run without jogging first
•Download as PPTX, PDF•
0 likes•64 views
Agile is an iterative approach to software delivery that builds software incrementally from the start instead of delivering it all at once near the end. There are some prerequisites for effective agile adoption, including prioritizing individuals and interactions over processes and tools, ensuring it is a team effort across departments, and understanding that the goal is more aligned and less wasted work rather than just faster delivery. Adopting agile properly requires self-organizing teams rather than forced organization from management, but many organizations struggle with this transformation. The most important aspects of agile are self-organizing teams and a focus on results rather than processes.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Rimantas Benetis: Agile – Can you run without jogging first
Similar to Rimantas Benetis: Agile – Can you run without jogging first (20)
More from Agile Lietuva
More from Agile Lietuva (20)
Recently uploaded
Recently uploaded (20)
Rimantas Benetis: Agile – Can you run without jogging first
- 1. Scrum/Agile + Teamwork Rimantas Benetis, Technology director @ Devbridge
- 3. Agile
- 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?
- 5. Agile in a nutshell
- 6. How does it compare vs waterfall
- 7. Why agile?
- 10. Flavors – scrum
- 11. Forced organization ≠ Self organization
- 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*
- 13. Trap
- 14. Organize vs Self organize
- 15. Prick and Bill (Lumbergh) story
- 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
- 19. Water scrum fall
- 21. • Top 2 Self organizing teams Results
- 22. Team
- 23. Team: Don’t drop a baton
- 26. Results
- 27. Outcome: Done is done
- 29. Trust your people to find the way
- 30. Thank you Rimantas Benetis Rimantas.Benetis@devbridge.com Technology Director @ Devbridge
Editor's Notes
- 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