Demos exist primarily to get feedback from your stakeholders when you can’t get feedback from them during the course of a sprint. In this post, I explore a set of questions I frequently get regarding demos and answer them from a product ownership perspective.
Product ownership is all about determining the right things to build and utilizes activities from product management, business analysis, and user experience. This post provides my guesses at the collections of activities from each of those fields to identify product ownership activities and asks you if I’m even close.
Acceptance criteria are the conditions that a solution must satisfy to be accepted by a user, a customer, or, in the case of system-level functionality, the consuming system. They are also a set of statements, each with a clear pass/fail result, that specify both functional and nonfunctional requirements and are applicable at a variety of levels (feature and user stories).
Feedback is an important ingredient to successful projects. One reason teams use iterative approaches, either time boxed sprints or single piece flow, is that they have the opportunity to get frequent and rapid feedback. A few recent experiences have inspired me to think a bit about how helpful feedback can be and some subtle aspects of feedback that are important to keep in mind.