Videos on Scrum and Agile Project Management
Technical debt is inevitable in Agile software development and rewriting your code every 6 months is not an option. Refactoring is a complex topic that doesn’t have a one-size-fits-all solution. Frontend applications are particularly sensitive because of frequent requirements and user flows changes.
There are many examples of fake Product Owners (PO) in the companies (PO as Business Analyst, PO as Project Manager, Proxy PO). Companies cause this by using many organisational design antipatterns (assign one PO per team, “Product” being in fact a component, using committee for product decisions instead of one person).
Based on a true story of the lessons learned coaching two Scrum teams on one product. Why is it that the same coaching techniques, in the same environment, can lead to drastically different outcomes? Learn how to identify the culture cycle and break bad habits to unlock the power of Agile team self-management.
This presentation discusses what technical debt looks like, and how easy it is to get into debt in the first place. Then the presenter proposes to put a plan into action to get out of it, understanding that you should consider technical debt as a business problem, not as a tech problem.
This video is an interactive exploration of retrospectives top tips, strategies and agile hacks for enabling continuous improvement of Scrum teams.
Ignoring impediments is one of the fastest ways to sabotage your Agile transformation. Agile is not a cure, it will on the contrary uncover issues. So Agile transformation efforts must overcome a myriad of challenges to achieve success.
So how to become a self-aware jack-of-all-trades in agility? Is there such a thing as Full Stack Agile Coach? If yes, how to become one?
Scrum Expert Copyright © 2009-2024 Martinig & Associates