The Right Way to do IT

The Right Way to do IT
复制标题

做 IT 的正确方法

DOI:
--
复制
发表时间:
2017
期刊:
影响因子:
--
通讯作者:
Adam Johansson
Adam Johansson
中科院分区:
--
文献类型:
--
作者:
Jonathan Ryen;Adam Johansson

文献摘要

被引文献

相似文献

在交付软件即服务(SaaS)时,对软件提供商带来了更多关于响应能力和灵活性的挑战。为了应对这些挑战并获得客户满意,可以应用精益软件开发原则消除浪费。已经认识到在开发软件时应用消除浪费原则的潜力的一个组织是企业资源规划系统提供商Infor M3的集成和商务单位。然而,消除浪费原则在整合和商务部门的五个团队中的实施仍处于早期阶段。因此,这篇论文的目的是在案例组织Infor M3集成和商业智能中识别废物并提出减少废物的方法。为了收集所需的深入知识,论文采用了定性的案例研究方法,即文献综述、访谈和观察。文献审查建立了关于软件开发中浪费的知识基础,随后将其作为分析和建议的基础。可以得出的结论是,软件开发中识别和减少浪费的主题还处于早期阶段,主要是由实践者推动的,很少有验证性研究支持该主题的适用性。然而,通过使用废物分类模型,在访谈中可以在所有的集成和商务团队中发现各种浪费,因此,部分完成工作、延迟、任务转换和重新学习被认为是最突出的浪费。此外,可以确定的是,一个团队开发了成功的方法,消除了团队的大部分浪费,而其他团队的方法通常是有缺陷的。为了更成功地减少废物,建议综合与商业智能单位在单位内培养对废物概念的认识。这些团队需要一个共同的定义和对废物的更多了解,以达到这一认识。此外,建议该股使用更全面的指标,如累计流程图,以便于识别和分析废物的根本原因。最后,建议该股通过以PDSA周期为结构的活动的持续改进来减少浪费。
When delivering Software as a Service (SaaS), increased challenges regarding responsiveness and flexibility are introduced to software providers. In order to address these challenges and attain customer satisfaction, the Lean Software Development principle Eliminate waste can be applied. One organization that has recognized the potential of applying the Eliminate waste principle when developing software is the Integration & BI unit of the Enterprise Resource Planning system provider Infor M3. However, the implementation of the Eliminate waste principle at the Integration & BI unit’s five teams is still in an early stage. Consequently, the intended purpose of the thesis was to identify waste and suggest approaches to reduce waste at the case organization, Infor M3 Integration & BI. In order to collect the in-depth knowledge required, the thesis utilized a qualitative case study methodology, whereby a literature review, interviews and observations were conducted. The literature review created a foundation of knowledge regarding waste in software development, that subsequent culminated as a basis for the analysis and recommendations. It could be concluded that the subject of waste identification and reduction in software development is in an early stage, largely driven by practitioners, with few verifying studies that support the subject’s applicability. However, by utilizing a waste categorization model various wastes could be identified at all of Integration & BI’s teams during the interviews, whereupon Partially done work, Delays, Task switching and Relearning was considered as the most prominent wastes. Moreover, it could be established that one team had developed successful approaches that eliminates much of the team’s waste whilst the other teams’ approaches were generally deficient. In order to more successfully reduce waste, the Integration & BI unit is suggested to create awareness of the concept of waste within the unit. The teams need a common definition and an increased understanding of waste in order to reach this awareness. Additionally, the unit is suggested to use more comprehensive indicators, like cumulative flow diagram, in order to facilitate identification and root-cause analysis of waste. Lastly, the unit is recommended to reduce waste by continuous improvements with activities structured as a PDSA-cycle.