Videos on Scrum and Agile Project Management
As Agile practitioners, whether you are a developer, tester, scrum master or product owner, we know that it is ALL about communication, right? But how much of what we say and what we hear are words? If, as much as 93% of our communication is non-verbal how can be sure we are ‘saying’ or ‘hearing’ the right thing? Non-Verbal Communication is sometimes referred to as Body Language, but it’s much more than that. This session is designed to give you a gentle introduction to this field. It will help you recognise some common behaviours, and show you how to start using this skill every day.
Organizations often start with Scrum after having heard about it, read about it, or after having read the Scrum Guides. While that is great, there are several unforeseen challenges they often face that prevent them from really benefiting from the advantages of Scrum. This presentation discusses seven unmentioned challenges of Scrum and uncovers possible solutions.
Shoddy software quality, disgruntled customers, missed deadlines… Such is daily life in many software companies. But there exists a better way. This presentation tells a story of turning around a demoralized and disengaged group of developers into a high performing team, while improving software quality, customer satisfaction and reducing technical debt.
As with everything else related to agile, the nature of the Product Owner role, and whether it is needed or all, depends a great deal on context. As teams discover this, it leads to some common questions: What do Product Owners really do? Do we even need Product Owners?
This is a talk about how shifting the focus from craft to product has affected my company. Our delivery teams are required everyday to make trade offs between what would the best technical solution and the one that is right for the product they are delivering. Ultimately, we get paid to solve business problems, not to be perfectionists.
Agile reminds us that the focus of any set of requirements needs to be on an outcome rather than a collection of whats and whos. Storytelling is a powerful tool to elevate even the most diehard requirements analyst from a discussion of individual requirements to a discussion of outcomes. Outcomes are the big picture that acts as an anchor for whole efforts and which is continuously broken down into more and more detailed product backlogs.
Running an experiment is trivial: Make a change and see what happens. Running experiments at scale, however, is a different story. It is not trivial to simultaneously run hundreds of experiments across 100 million users. It’s not trivial to cover dozens of platforms and markets while staying on top of the technical and methodological complexities.
