DocumentCode
1803290
Title
Enterprise Scrum: Scaling Scrum to the Executive Level
Author
Greening, Daniel R.
fYear
2010
fDate
5-8 Jan. 2010
Firstpage
1
Lastpage
10
Abstract
Our company manages 25 software engineering teams across 6 products using a single top-down Enterprise Scrum. We know of no other company doing this, yet it provides extreme visibility and control at the CXO level. It promotes agile thinking enterprise-wide, driving non-engineering departments to adopt Scrum. We believe it is making us more profitable.We estimate effort in team months, run quarterly Sprints, assign whole teams to projects, meet in weekly stand-ups. We start, postpone or cancel whole projects. Within individual projects, we still use 1-4 week Sprints and all the trappings of the classic Scrum process, including, in some cases, Scrum-of-Scrums. New challenges arise: Shared resource constraints suggest Kanban methods. Net Present Value can justify prioritization, but creates controversy. Moving teams between projects requires rapid programming environment setup. The process forces executives to justify decisions. We want simple improvement metrics, but they seem elusive.
Keywords
software development management; Kanban methods; classic Scrum process; enterprise scrum; executive level; single top down enterprise scrum; software engineering teams; Companies; Conference management; Decision making; Engineering management; Impedance; Large-scale systems; Portfolios; Productivity; Programming environments; Software engineering;
fLanguage
English
Publisher
ieee
Conference_Titel
System Sciences (HICSS), 2010 43rd Hawaii International Conference on
Conference_Location
Honolulu, HI
ISSN
1530-1605
Print_ISBN
978-1-4244-5509-6
Electronic_ISBN
1530-1605
Type
conf
DOI
10.1109/HICSS.2010.186
Filename
5428541
Link To Document