Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
This is a list of actions that Scrum Masters at bbv Software Services AG have applied successfully in their teams to improve performance (= how much gets done in an amount of time). Please note that these actions were created to respond to specific problems found in real world projects. They may not be applicable in general in any situation. 
No comment yet.
Sign up to comment
Scoop.it!
Summary
|
Scoop.it!
One of the best things you can do to avoid story-splitting mistakes is to become more adept at splitting stories. Fortunately, there are only five techniques you need to know that will enable you to split any story. I mentioned three of the techniques in this post. They were splitting stories by
Mickael Ruau's insight:
Instead, spikes should be reserved for when a user story contains so much uncertainty that starting the story in earnest would be a mistake without the knowledge to be gained from the spike. Teams that split spikes out of stories too frequently often do so out out of fear of getting an estimate wrong. The team feels like they’ll be punished, or at least criticized, if a story takes longer to develop than they estimate. These teams are often found in cultures that confuse estimating with committing. To overcome this problem, either de-emphasize estimates or work to create safety around them so that teams don’t fear each estimate will used against them.
|
Use spikes and user stories deliberately. Spikes have a fix time-box and an estimated result. User stories have a fixed result (acceptance criteria) and estimated needed time.
Use user stories when you know what you want. Use Spikes when you want to plan the unknown.