2013
DOI: 10.1007/978-3-642-44930-7_2
|View full text |Cite
|
Sign up to set email alerts
|

Lean Software Development – What Exactly Are We Talking About?

Abstract: Abstract. As the Software Engineering landscape continues to evolve and new paradigms are introduced, there can be a tendency for both industry and academia to enthusiastically embrace new approaches and march forward under whatever banner conventional wisdom has decided to adopt. One such banner is Lean Software Development, a paradigm that continues to see a growth in interest driven by the need for cost reductions within industry. The term lean attracts the attention of business, but precisely how it applie… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

0
4
0

Year Published

2014
2014
2023
2023

Publication Types

Select...
4
2
2

Relationship

1
7

Authors

Journals

citations
Cited by 13 publications
(4 citation statements)
references
References 24 publications
0
4
0
Order By: Relevance
“…Flow differs from traditional software project management because it focuses on managing queues rather than project timelines and phases (Anderson, 2013; Poppendieck, 2011; Power & Conboy, 2015; Reinertsen, 2009). Flow differentiates itself from agile management approaches by (1) adopting an end-to-end perspective of the whole process (Anderson, 2013; Anderson et al, 2011; Petersen, 2011; Reinertsen, 2009), (2) moving from time boxed sprints to continuous deployment of software, and (3) limiting work in progress (WIP) (Cawley, Wang, & Richardson, 2013; Petersen, 2011; Sjøberg, Johnsen, & Solberg, 2012). Flow aims to maximize a continuous flow of value by (1) implementing WIP limits; (2) permitting new work items to immediately enter the development process, and, when required, prioritize it within the WIP limits; and (3) removing impediments to flow (i.e., time boxed sprints, context switching).…”
Section: Introductionmentioning
confidence: 99%
“…Flow differs from traditional software project management because it focuses on managing queues rather than project timelines and phases (Anderson, 2013; Poppendieck, 2011; Power & Conboy, 2015; Reinertsen, 2009). Flow differentiates itself from agile management approaches by (1) adopting an end-to-end perspective of the whole process (Anderson, 2013; Anderson et al, 2011; Petersen, 2011; Reinertsen, 2009), (2) moving from time boxed sprints to continuous deployment of software, and (3) limiting work in progress (WIP) (Cawley, Wang, & Richardson, 2013; Petersen, 2011; Sjøberg, Johnsen, & Solberg, 2012). Flow aims to maximize a continuous flow of value by (1) implementing WIP limits; (2) permitting new work items to immediately enter the development process, and, when required, prioritize it within the WIP limits; and (3) removing impediments to flow (i.e., time boxed sprints, context switching).…”
Section: Introductionmentioning
confidence: 99%
“…It is less costly and even the time taken by this approach is one third in comparison to the other approaches. However, in spite of its merits, this method entails a security risk [30]. Figure. 1 shows the list of factors affecting the design of web application security at first level.…”
Section: Lean Development Methodologymentioning
confidence: 99%
“…The objective of this paper therefore is to add to the existing conversation on value in requirements and software research projects brought about by lean [3,5] and agile [18,19] methods. We aim to inspire a discussion on the application of a lean mindset and lean development approaches in the planning and execution of DSR projects towards this regard.…”
Section: Introductionmentioning
confidence: 98%