Kanban Implementation in a Telecom Product Maintenance

Marko Seikola, Hanna-Mari Loisa, Andr's Jagos
{"title":"Kanban Implementation in a Telecom Product Maintenance","authors":"Marko Seikola, Hanna-Mari Loisa, Andr's Jagos","doi":"10.1109/SEAA.2011.56","DOIUrl":null,"url":null,"abstract":"Telecom Product Maintenance at two Ericsson R&D Centers implemented Kanban. The third level maintenance is performed by the Customer Support Request (CSR) teams and by the design maintenance teams, which are located in two sites. There are separate backlogs for the customer support and for the design maintenance in the primary site and a third backlog for the design maintenance in the secondary site. Pull mindset, team working, team empowerment, and continuous improvement have become part of the everyday activities. Best practices from Scrum have been selected to complement the Kanban implementation. Also, the metrics have been reviewed. The major challenges have been related to the boundary rules, for instance, multi-site working, the platform dependency and the service level agreements but also to the roles and responsibilities. The Kanban boards and the chosen practices have been adjusted as the understanding of Lean has increased. This industry paper presents the journey to Lean product maintenance including the identification of the key success factors that are to some extent generalizable. First, the overall implementation is discussed followed by a deeper description of the implementation both in the CSR handling and in the Fault Handling (design maintenance) including also the experiences from the secondary R&D site. The paper continues by discussing the identified challenges and positive effects. At the end of the paper, the implementation concepts and key success factors are stated.","PeriodicalId":107972,"journal":{"name":"2011 37th EUROMICRO Conference on Software Engineering and Advanced Applications","volume":"8 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2011-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"15","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2011 37th EUROMICRO Conference on Software Engineering and Advanced Applications","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SEAA.2011.56","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 15

Abstract

Telecom Product Maintenance at two Ericsson R&D Centers implemented Kanban. The third level maintenance is performed by the Customer Support Request (CSR) teams and by the design maintenance teams, which are located in two sites. There are separate backlogs for the customer support and for the design maintenance in the primary site and a third backlog for the design maintenance in the secondary site. Pull mindset, team working, team empowerment, and continuous improvement have become part of the everyday activities. Best practices from Scrum have been selected to complement the Kanban implementation. Also, the metrics have been reviewed. The major challenges have been related to the boundary rules, for instance, multi-site working, the platform dependency and the service level agreements but also to the roles and responsibilities. The Kanban boards and the chosen practices have been adjusted as the understanding of Lean has increased. This industry paper presents the journey to Lean product maintenance including the identification of the key success factors that are to some extent generalizable. First, the overall implementation is discussed followed by a deeper description of the implementation both in the CSR handling and in the Fault Handling (design maintenance) including also the experiences from the secondary R&D site. The paper continues by discussing the identified challenges and positive effects. At the end of the paper, the implementation concepts and key success factors are stated.
看板在电信产品维护中的实现
爱立信两个研发中心的电信产品维护部门实施了看板。第三级维护由位于两个站点的客户支持请求(CSR)团队和设计维护团队执行。主站点的客户支持和设计维护有单独的backlog,次要站点的设计维护有第三个backlog。拉动式思维、团队合作、团队授权和持续改进已经成为日常活动的一部分。我们选择了Scrum中的最佳实践来补充看板的实现。此外,度量标准也经过了审查。主要的挑战与边界规则有关,例如,多站点工作、平台依赖和服务水平协议,但也与角色和责任有关。随着对精益理解的增加,看板和选择的实践也进行了调整。这篇行业论文介绍了精益产品维护的历程,包括在某种程度上可推广的关键成功因素的识别。首先,讨论总体实现,然后对CSR处理和故障处理(设计维护)中的实现进行更深入的描述,包括来自二级研发站点的经验。本文继续讨论了已确定的挑战和积极影响。文章最后阐述了实施理念和成功的关键因素。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信