Your product roadmap can basically set your life course as a designer/researcher so why is it so often that user feedback can get lost in the discussion over “Feasibility” of implementation. Without a clear roadmap, research and design can often not have the lead time needed for activities. This leads to a state of forever catching up and being reactionary.
Videos on Scrum and Agile Project Management
The common wisdom is that Agile need Kanban teams to do the work that the Scrum Teams can’t do yet as well as the stuff that you don’t want your Scrum Teams to be distracted by. There is however much more to Kanban than meets the common agilist’s eye.
The change required by Agile and Scrum isn’t simple. This talk presents the tools provided for six teams and they were enabled to build the foundations for safe continuous learning themselves. Most people in agile and lean are involved in change somehow.
Inspired by NASA astronaut training for solving complex, evolving problems on the fly, the Chaos Lottery is one approach to testing the resilience of a Scrum team. This is a story about knowing what you should do, and finding you are still not quite doing it.
Genuine agility is enormously effective in helping us achieve our dreams. The trouble is, Agile has grown into a complex tangle of roles and rituals, frameworks and tools, processes and certifications. We need a return to simplicity. Modern Agile is here to help.
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.
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?