Guilherme Campos

“For every story you write, you need to put three into your backlog of stories.” I asked him why, and he said, “You just do.” I asked, “What should I write on the other two?” “It doesn’t matter what you write.” “What do you mean?” I asked, “I have to write something on them!” Alistair replied, “Well, if you have to write something on them, then write what you want on the first card, and on the second card write ‘Fix the first card.’ Then on the third card, write ‘Fix the second one.’ If you aren’t going around this cycle three times for each story, you’re not learning.”
― Jeff Patton, User Story Mapping: Discover the Whole Story, Build the Right Product

“And, of course, as savvy readers can appreciate, when software developers say it’s going to take a year to get something done, they really mean two years. It’s not because they’re incompetent, or that they are calendar-challenged, it’s just that estimating the time to do something we’ve never done before is something we suck at. And, by nature, we’re often optimistic animals.”
― Jeff Patton, User Story Mapping: Discover the Whole Story, Build the Right Product

“Your job isn’t to build more software faster: it’s to maximize the outcome and impact you get from what you choose to build.”
― Jeff Patton, User Story Mapping: Discover the Whole Story, Build the Right Product

“Approach what you find repulsive, help the ones you think you cannot help, and go places that scare you. ”
― Machik Labdron