In its recent guide to the Product Backlog, Plaky breaks down the what and why of one of Agile’s core artifacts. But as Gehtsoft CEO Ivan Gekht often reminds teams—it’s not the format that matters. It’s the thinking behind it. “A backlog is a living hypothesis
Helping agile teams to improve, I often saw one problem, especially with the teams recently migrated from old-school methods, such as RUP. In these teams, product owners are the only team members proactively involved in backlog management. Such situation contradicts to the Scrum ideology and dramatically decreases the team performance.
FURPS is an acronym for requirements management, elaborated by Grady and Caswell decades ago. It stands for Functionality, Usability, Reliability, Performance, and Supportability. It helps to collect the complete set of requirements without overlooking essential non-functional needs and expectations of a customer and end-users. Many product owners and even whole
Benefits of Problem Analysis The big question for PSPO is how to discover user stories and gather information about them. SCRUM itself does not offer a good toolkit for requirements analysis, but we can choose an appropriate tool as long as the tool and its application support SCRUM pillars and
