"Creepy" User Stories

Written By Allison Pollard

Photo by Dan and Fern Treacy

Most of us are familiar with the idea of scope creep--when the understanding of work grows, and the effort involved is larger than originally expected.  A coworker was talking about the problem of scope creep and how it can be due to discovering technical debt in the codebase that needs to be addressed or it can be related to the complexity of business requirements.  When this happens, he said, the user stories can be called "creepy."  I love the term, and I wonder:

Does your product lead to a lot of creepy user stories?
Allison Pollard

Allison Pollard is a coach, consultant, and trainer who brings the power of relationship systems intelligence to go beyond tasks, roles, and frameworks to create energy for change. She engages with people and teams in a down-to-earth way to build trust and listen for signals to help them learn more and improve. Allison focuses on creating alignment and connection for people to solve business problems together. Her experience includes working with teams and leaders in energy, retail, financial, real estate, and transportation industries to help improve their project/product delivery and culture. Allison currently volunteers as program director for Women in Agile’s mentorship program. Her agile community focus is championing new voices and amplifying women as mentors and sponsors for the next generation of leaders. Allison earned her bachelor’s degrees in computer science, mathematics, and English from Southern Methodist University in Dallas, TX. She is a Certified Professional Co-Active Coach (CPCC), a foodie, and proud glasses wearer. Allison is a prolific speaker at professional groups and international conferences, including Scrum Gatherings and the Agile Alliance Agile20xx conferences. Allison is co-owner of Helping Improve LLC.

http://www.allisonpollard.com
Previous

Growing as a Person -- the Goo
Next

The F-word (Feedback)