Six Card Solutions belongs to the earlier adopters among Swiss Financial Institutions deploying Scrum. They started rolling out Scrum among their 80 developers in Zurich last Summer (2009). So, how did it go?
Christoph Loher (Product Owner) and Stefan Kinigadner (ScrumMaster) were the leaders of the first team to transition to Scrum at Six’s Development Group Zurich. The organization presented to usual challenges one expects when trying to transition one team to a cross-functional Scrum in a company that is organized on function division. Despite this challenge, the team was able to achieve a pretty good Scrum (based on Henrik Kniberg’s Scrum Checklist).
One problem in particular stood out: As the project unfolded, the team grew. This was a relic of the classical project planning. At some point, the team became unwieldy – 12 people or so – and performance stagnated. The P-O wanted to split the team in two. Although they talked about it in several retrospectives, the team was never enthusiastic about splitting. Eventually, the P-O insisted (but avoided falling back into command and control). Although not all variables have been eliminated, after the first sprint after the split, it looks like the team(s) substantially improved their productivity and everyone agreed the split was a good thing.
You can download their presentation here: Scrum at Six Card Solutions
A lot of the discussion centered on why the team could not agree to split. My take: the members of a team are expected to form a unit, to commit to that unit and to solve problems together. Even the ScrumMaster is taught ‘When in doubt, ask the team!’ Asking a team to split itself up is asking the team members to reject their identity, something they are not all inclined to do!
Perhaps there are limits to what problems self-organizing teams can be expected to solve. And this hints at the role of management in a Scrum organization.
What’s your experience? What are the limits of a self organizing team?
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. |