1. Why quality over delivery is bad
2. Continues Integration pitfalls for distributed teams
3. Why test automation pyramid is good and must be followed

Happy Project Manager who is really passionate about management, quality and Agile. In the IT industry for more than 6 years. Started my career as a Quality Assurance Engineer and then became a Project Manager in 2015. I often give talks on Lean and Agile practices, run different activities for team building and team motivation. Mostly specialise in e-commerce area.

This talk is paired with Focus on Testing value first before correctness as part of a conversation track on Quality
 

 

I want to share a story of my very quality-focused customer. And the issues we faced when quality was over everything else. This resulted in huge delivery delays having CI, BDD, TDD, Scrum, Kanban properly setup though with an achievement of nearly 100% test coverage. Then I would like to have an open discussion on how to achieve a quality-velocity balance for big projects with distributed teams on it. I want to share the pitfalls of quality-oriented environments so that audience could take away an idea of how to prevent them on their projects