Agile Product Management with Scrum Quotes

“product owners felt more confident, more able to influence, more visible, better organized, and better motivated in the new role”
― Roman Pichler, Agile Product Management with Scrum: Creating Products that Customers Love (Addison-Wesley Signature Series

“The Product Owner is the one and only person responsible for managing the Product Backlog”
― Roman Pichler, Agile Product Management with Scrum: Creating Products that Customers Love (Addison-Wesley Signature Series

“the product vision was lost amid the many handoffs.”
― Roman Pichler, Agile Product Management with Scrum: Creating Products that Customers Love (Addison-Wesley Signature Series

“Most sprint planning meetings I have attended were fun. The ones that weren’t involved a poorly groomed product backlog. When the backlog isn’t groomed prior to the meeting, the product owner and team often try to carry out impromptu grooming activities, which consume valuable planning time and result in poor requirements and weak commitments. Plus, everyone is exhausted by the end of the meeting.”
― Roman Pichler, Agile Product Management with Scrum: Creating Products that Customers Love (Addison-Wesley Signature Series

“Working with a product backlog does not mean that the Scrum team cannot create other helpful artifacts, including a summary of the various user roles, user story sequences to model workflows, diagrams to illustrate business rules, spreadsheets to capture complex calculations, user interface sketches, storyboards, user interface navigation diagrams, and user interface prototypes. These artifacts do not replace the product backlog but instead should elaborate and explain its content. And keep things simple. Only use artifacts that help the Scrum team move closer to a shippable product.”
― Roman Pichler, Agile Product Management with Scrum: Creating Products that Customers Love (Addison-Wesley Signature Series

“product road map should state for each version the projected launch date, the target customers and their needs, and the top three to five features.”
― Roman Pichler, Agile Product Management with Scrum: Creating Products that Customers Love (Addison-Wesley Signature Series

“The wisdom of many is preferable to the brilliance of one.”
― Roman Pichler, Agile Product Management with Scrum: Creating Products that Customers Love (Addison-Wesley Signature Series

“There is only one move that really counts: the next one” (Gilb 1988, 97).”
― Roman Pichler, Agile Product Management with Scrum: Creating Products that Customers Love (Addison-Wesley Signature Series

“The first thing we have to do is to look ahead two to three sprints to understand which product backlog items are likely to be worked on (Cohn 2005, 206; Pichler 2008, 146). This requires decomposing and refining product backlog items earlier; more detailed items can now be found at the top of the product backlog. The next step is to identify any dependencies between the teams by asking the following questions: Do they have to work on the same feature or component? Does any team act as the supplier of another team? If so, is it feasible to supply the feature or component and use it in the same sprint? To eliminate problematic dependencies, we may have to change the product backlog prioritization.”
― Roman Pichler, Agile Product Management with Scrum: Creating Products that Customers Love (Addison-Wesley Signature Series