Do you find that user stories grow and multiply until you can’t fit them in your Scrum sprints? Are you struggling to see the big picture? Are you lost in user story hell? This presentation examines the OOPSI (Outcome, Output, Process, Scenarios, Inputs) technique and demonstrates how it accelerates delivery by ensuring that you are always working on the right thing and can see the bigger picture.
Videos on Scrum and Agile Project Management
So now that everyone and their dog is Agile, what has really changed? Are we really „delivering more value in less time“ as many agile approaches promise. What do we even mean by value? How do we know when we have delivered value? When we are “done” according to our “Definition of Done”, or when we can validate that a feature is being used by our customers?
Agile and Scrum team formation is a natural human response to certain conditions. Once they exist, the formation process begins. This session looks at those conditions, and then looks at what other conditions need to be reached to progress through the different stages defined by Bruce Tuckman: Forming, Storming, Norming, and Performing.
There’s some weird stuff going on in the name of “agile” nowadays.Too many pretty promises, eager exaggerations, and misguided misapplications of misunderstood premises make for troubling times. So what is the future of agile? We want to share with you how agile fails and how agile succeeds. The key to the future of agile is being thoughtful, realistic, and above all skeptical.
The Scrum Guide says that “The Scrum Master is a servant-leader for the Scrum Team.”, but what is servant leadership? We will talk about where servant leadership came from and what servant leadership is. We will talk about examples of servant leaders in our world and where to find more information about servant leadership. Finally, we will talk about how you can become a servant leader.
Nexus is a framework for scaled Scrum developed by Scrum co-creator Ken Schwaber and Scrum.org community. It addresses the most painful problems of scaled development – dealing with dependencies and building ‘Done’ integrated software every iteration.
In small Scrum teams, it’s common for people to share roles such as Scrum Master / Tester / Dev but in a lot of cases there are conflicting interests. How can a Tester adequately test when as a Scrum Master the highest priority is assisting the team to deliver?