Scrum 911! Using Scrum to Overhaul a Support Organization

Bhaven Sheth
{"title":"Scrum 911! Using Scrum to Overhaul a Support Organization","authors":"Bhaven Sheth","doi":"10.1109/AGILE.2009.23","DOIUrl":null,"url":null,"abstract":"The Support 2.0 Team at our IT organization has recently completed Phase 1 of the Support 2.0 project. Phase 1 was a four month endeavor with a primary focus of collecting data to understand why support was so costly and identify the root cause for each support request. The team strongly believed that this initial phase would be critical to making significant impacts to the quality and supportability of applications. This experience report describes the challenge for the Support 2.0 Team and shares the successful adoption of agile practices in redefining the support organization. In the spirit of the agile transition to software development one year prior, our IT organization decided to rethink the approach to application support. By embracing agile principles and utilizing agile concepts, such as a cross-functional team, a team collaboration approach with frequent reviews to inspect and adapt as needed, etc, the business was able to reap immediate benefits. It was a challenging journey for the team, where the mix of onshore/offshore support engineers and an integrated client / vendor relationship within an agile team and focused framework helped to transform the support organization from an operational cost center to a value added thought partner. This resulted in a significantly improved culture and effectiveness of the support organization. This unique organization of an agile, cross-functional and team-based approach to handle support requests improved the customer experience, reduced support costs, and ultimately provided greater opportunity for the business to fund new development efforts.","PeriodicalId":280848,"journal":{"name":"2009 Agile Conference","volume":"2 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2009-08-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"13","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2009 Agile Conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/AGILE.2009.23","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 13

Abstract

The Support 2.0 Team at our IT organization has recently completed Phase 1 of the Support 2.0 project. Phase 1 was a four month endeavor with a primary focus of collecting data to understand why support was so costly and identify the root cause for each support request. The team strongly believed that this initial phase would be critical to making significant impacts to the quality and supportability of applications. This experience report describes the challenge for the Support 2.0 Team and shares the successful adoption of agile practices in redefining the support organization. In the spirit of the agile transition to software development one year prior, our IT organization decided to rethink the approach to application support. By embracing agile principles and utilizing agile concepts, such as a cross-functional team, a team collaboration approach with frequent reviews to inspect and adapt as needed, etc, the business was able to reap immediate benefits. It was a challenging journey for the team, where the mix of onshore/offshore support engineers and an integrated client / vendor relationship within an agile team and focused framework helped to transform the support organization from an operational cost center to a value added thought partner. This resulted in a significantly improved culture and effectiveness of the support organization. This unique organization of an agile, cross-functional and team-based approach to handle support requests improved the customer experience, reduced support costs, and ultimately provided greater opportunity for the business to fund new development efforts.
查看原文
分享 分享
微信好友 朋友圈 QQ好友 复制链接
本刊更多论文
Scrum 911 !使用Scrum彻底改革一个支持组织
我们IT组织的支持2.0团队最近完成了支持2.0项目的第一阶段。第1阶段是一个为期4个月的努力,主要集中于收集数据,以了解为什么支持如此昂贵,并确定每个支持请求的根本原因。该团队坚信,这个初始阶段对于对应用程序的质量和可支持性产生重大影响至关重要。这份经验报告描述了支持2.0团队面临的挑战,并分享了在重新定义支持组织时成功采用敏捷实践的经验。本着一年前向软件开发的敏捷过渡的精神,我们的IT组织决定重新考虑应用程序支持的方法。通过采用敏捷原则和利用敏捷概念,例如跨职能团队、团队协作方法,以及根据需要进行频繁检查和调整等,业务能够立即获得收益。对于团队来说,这是一次充满挑战的旅程,在敏捷团队和专注框架内,陆上/海上支持工程师的组合以及集成的客户/供应商关系帮助支持组织从运营成本中心转变为增值思想伙伴。这大大改善了支助组织的文化和效率。这种独特的组织采用敏捷、跨职能和基于团队的方法来处理支持请求,改善了客户体验,降低了支持成本,并最终为企业提供了更多的机会来资助新的开发工作。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 去求助
来源期刊
自引率
0.00%
发文量
0
期刊最新文献
Transitioning from Agile Development to Enterprise Product Management Agility Take No Prisoners: How a Venture Capital Group Does Scrum Applying the Dreyfus Model of Skill Acquisition to the Adoption of Kanban Systems at Software Engineering Professionals (SEP) Collaborative Agile Contracts Creating Habitable Code: Lessons in Longevity from CruiseControl
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
现在去查看 取消
×
提示
确定
0
微信
客服QQ
Book学术公众号 扫码关注我们
反馈
×
意见反馈
请填写您的意见或建议
请填写您的手机或邮箱
已复制链接
已复制链接
快去分享给好友吧!
我知道了
×
扫码分享
扫码分享
Book学术官方微信
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术
文献互助 智能选刊 最新文献 互助须知 联系我们:info@booksci.cn
Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。
Copyright © 2023 Book学术 All rights reserved.
ghs 京公网安备 11010802042870号 京ICP备2023020795号-1