Wiktor Żołnowski, Agile Coach and Trainer. Co-Founder at Pragmatic Coders. Entrepreneur, Sailor and Dots-Connector. Agile Transformation leader and Change Agent. Author of two books: “Myths and Problems in Agile” and “Agile transitions”. Blogger: http://blog.testowka.pl. Initiator of “Bring Your Own Problem” community (http://byop.pl).
Wiktor does not believe in work-life balance. He says that if you love what you do then your life automatically became awesome and you do not need to look for any balance.
During last few years he has been leading couple Agile transitions in various IT organisations. Beside Agile Coaching and training currently he is mostly focused on Pragmatic Coders (http://pragmaticcoders.com) – his own Software Development Company.
Queuing Theory. How to find a time for quality and improvements in software development?
Have you ever thought about how to find time for quality and process improvements when there is always to much things to do in your software product development? Have you ever think about why some Scrum and Kanban implementation works and other not?
This story started when I have been trying to find an efficient way to optimize performance of one of our Clients’ system. When looking for an efficient way for load and performance testing
I remind myself about Queuing Theory and Little’s Law.
When I was doing some research around it besides figuring out how to measure our system maximum possible load without performance tests I did realize (not just from experience or intuition but from real math) why Agile works. I have also learned why some implementations of Scrum or Kanban just have to fail from time to time (sooner or later).
During this presentation you will learn:
- How to apply Queuing Theory when looking for bottlenecks in your system Little’s Law in practice?
- Why Scrum and Kanban work and when it work based on Math not fluffy theories and intuition?
- How to use Work In Progress limits and why (both in your system and your development process) again no fluffy stuff, just Math?
- What is the Slack Time and how to convince anyone that it does make sense?
- How to find time for quality?
- How to find time for improvements?
Do you want to increase your team velocity and effectiveness? Have you ever struggled with implementing real teamwork? Do you want to improve the Cycle Time for implementing your features? Or maybe you just want to predict when your system or application will need more resources and where are the bottlenecks?
I will also uncover the secret of convincing anyone to use Scrum/Kanban or any other Agile/Lean process. It is simple they can argue with you but they can not argue Math. So if you have ever struggled with managers who push too much tasks on you and your team this presentation is definitely dedicated to you!
Queuing Theory is your answer…
This talk is not in English. It is in Math.