際際滷

際際滷Share a Scribd company logo
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)
The Power of Feedback (lightning talk)

More Related Content

Editor's Notes

  • #2: Hi, my name is Henning Wolf, I am a CST candidate and I am CEO and consultant for it-agile in Germany. I would like to take a deeper look into Scrum and agile method‘s ability in gaining and coping with feedback, which is a powerful tool, if you really use it.
  • #3: Why is feedback so important? Most projects do have a lot of risks. And that is OK, because risky projects are more valuable in most cases.
  • #4: One risk is unstable requirements. So some try to figure out all the requirements in detail upfront. But you can‘t do that successfully. No, you can‘t.
  • #5: And even when you are quite clear about your vision for the product, you can not always choose the right feature set upfront. And while we all are busy in changing the world with our projects, the world is changing itself. So we must respond to these changes, too.
  • #6: If we look at the core of Scrum, then it is Plan - Do - Adapt. We do this in short cycles we call Sprints. We can only successfully adapt on the basis of feedback. That is why feedback is so essential for us.
  • #7: So when do we get feedback? We might look at Scrum as getting feedback all the time. While developing, the team learns a lot based on feedback. At the DailyScrum we get feedback on team status and impediments.
  • #8: More feedback we gain in Sprint review meetings where we show the sprint results to the product owner and stakeholders. It‘s a good idea when the PO comes with customers and users: It‘s a chance for more feedback.
  • #9: While this feedback might also provide insights on our team‘s velocity and estimation skills, especially the sprint retrospectives gain feedback on process issues, hopefully resulting in ideas how to improve.
  • #10: But I‘m quite sure that the best feedback is gained from using the product. Are there any users at all? Which features do they use? What do users say? What do they like? Do they understand the intended philosophy of the product or service?
  • #11: Who wants what kind of feedback? The Scrum-Team wants feedback on their scheduling and planning, their velocity, their process, their improvements, impediments, their product‘s quality and customer satisfaction.
  • #12: The Product Owner wants different feedback: Do I need features like a country road or do I need highways? Am I planning the right features? Does anyone know about our product or service? Do they use it? Why don‘t they? Why do they?
  • #13: So, what do we do with all this feedback? We adapt, we change policies, team rules, processes, etc. And we change the Product Backlog by re-prioritizing, changing items and writing new ones.
  • #14: I think ideas from the Lean Startup community can help utilizing the power of feedback even more. They focus on learning something from feedback based on facts. You gather facts by measuring. To measure you need to build something.
  • #15: So while their cycle is Build-Measure-Learn it is a good idea to think it the opposite order: What do I want to learn? What could I measure to learn that? What do I need to build to measure that?
  • #16: And sometimes I even don‘t have to build new software and can learn from setting up a Google AdWord and a plain HTML-page to learn whether somone is interested in the service offered.
  • #17: Money is a cool feedback tool: How many people sign up for the service? Which price are they willing to pay? (and again: I can get this feedback before the whole service runs or even before my payment service is installed by having a „buy“-button and measure clicks)
  • #18: a/b-Testing is also a valuable feedback mechanism: What do users prefer? When do I get more followers, using the left or the right profile picture on twitter?
  • #19: Sometimes early feedback indicates project failure. And failing fast is a good thing. It‘s worse than succeeding, but better than failing late - after you spent a lot of money. So if there is a risk of failing, than we should get feedback on that as soon as possible.
  • #21: Thank your for your attention. I would like to get feedback from you, so feel free to follow me on twitter, send me a mail or just talk to me. Thank you very much.