Last week, I posted a summary of the responses to my poll on scrum sprint success and story size. I also proposed a simple definition of success: a successful Scrum team delivers what it promises.
A good Scrum team does not systematically over-commit. It doesn’t under-commit either – not one single response indicated that the team usually delivered more that 110% of its commitment. By this definition, 32% of the respondents are “successful” while 68% are “improvable”.
Let’s take a closer look at Team Size, Story Size and Sprint Duration and how the relate to relate to successfully completing the a Scrum Sprint.
Team Size and Sprint Duration
Two week sprints are by far the most popular with 50 respondents, and the distribution of on the number of stories committed to each sprint looks pretty much like a bell curve centered around 6 stories/sprints. Three week sprints a relatively popular – 17 responses – but the volume of data is probably too small for a curve to form. With a total of 13 responses, it’s unlikely that the data for 1-week and 4-week sprints is at all representative.
Summary
Having analyzed the data, I think the survey would be much useful if there were a factor of 10 more data points – 800 to 1000 would be really good. Still, looking at this data, some trends are taking shape:
P.S. Does anybody with substantial readership think this study was cool and useful? I would love to repeat it with the goal of substantially higher feedback and see the trends become more apparent. Please contact me!
The story size poll is still active – I’ll keep an I eye on it and when I get 200 responses, I’ll evaluate the data again. Presently I have 85.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
mailchimp_landing_site | 1 month | The cookie is set by MailChimp to record which page the user first visited. |
Cookie | Duration | Description |
---|---|---|
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gat_gtag_UA_42152348_1 | 1 minute | Set by Google to distinguish users. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
Cookie | Duration | Description |
---|---|---|
NID | 6 months | NID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
Cookie | Duration | Description |
---|---|---|
COMPASS | 1 hour | No description |
cookies.js | session | No description available. |
S | 1 hour | No description available. |
3 Comments
Very insightful, thanks a lot!
Very interesting statistics here.. I have to agree that there is no one way to develop with scrum. Companies and Project manager's sometimes seem to get caught up in all of the rules/fads of scrum instead of creating a system that works with their culture and team. Excellent post and I look forward to reading more.
I think this was very interesting as well. It would be nice to try it again and push for more input to see if the trends become a little bit more clear and then maybe ask some clarifying questions to try and draw unique differences and similarities.