A cloud-hosted payment system, Stripe turned out to be robust and easy to use. I faced this the first time we built a product that used Stripe for payment processing. In some cases, a story is large because there are a lot of technical unknowns. In agile terminology, a spike is research conducted to make the development team smarter about what it will take to implement a user story. One alternative method for splitting user stories is called SPIDR. However, you may find that it doesn’t work for you, and you’d like an alternative. Many people follow Mike Cohn‘s five strategies for splitting user stories. Showing up to sprint review and having to explain again why they didn’t complete their stories can demoralize a development team.
Large stories make it difficult for the team to feel a sense of momentum, and they can cause an even worse problem: not quite getting them done by the end of the sprint. Although they do have a way to break down the work using subtasks, stories that take an entire sprint or more to complete cause problems for the team. Scrum teams face this same type of challenge when tackling user stories that are too large. More projects have suffered the tragic death of procrastination than having met their end through the far more noble failure of execution. You drag your feet and never quite get going simply because you don’t know where to start. Whether you’re considering entering a new market with unfamiliar compliance issues or hiring a team of employees for a division you’ve never had before, such projects seem overwhelming when considered as a single item on your to-do list. We’ve all been faced with a daunting challenge that seems almost too big to tackle.
0 kommentar(er)
