Notes from Jeff Patton's "User Story Mapping" book
“I like making things.
What motivates me is the joy I get from creating a piece of software and seeing people use it and benefit from it.
I’m a reluctant methodologist. I found I needed to learn how process and practice work to get better at them.
I’m only now learning after 20-plus years in software development how to teach what I’ve learned.
And I know that what I teach is a moving target.
What I understand changes every week.
How best to explain it changes almost as fast...”
Excerpt From: Jeff Patton. “User Story Mapping.”
User Stories traps and anti-patterns
"Because stories let you focus on building small things, it’s easy to lose sight of the big picture" => user stories should be small and have all the good SMART attributes, but having these small chunk of features done and integrated in the actual product sprint after sprint may bring you to build a "Franken-product".
"When you’re building a product of any significant size, building one small thing after another leaves people wondering when you’ll ever be done, or what exactly you’ll deliver"
“Because stories are about conversations, people use that idea to avoid writing anything down.”