Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Extending value stream mapping through waste definition beyond customer perspective
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.
2014 (English)In: Journal of Software: Evolution and Process, ISSN 2047-7481, Vol. 26, no 12, 1074-1105 p.Article in journal (Refereed) Published
Abstract [en]

Value Stream Mapping is one of the several Lean practices, which has recently attracted interest in the software engineering community. In other contexts (such as military, health, production), Value Stream Mapping has achieved considerable improvements in processes and products. The goal is to also leverage on these benefits in the software intensive product development context. The primary contribution is that we are extending the definition of waste to fit in the software intensive product development context. As traditionally in Value Stream Mapping everything that is not considered valuable is waste, we do this practically by looking at value beyond the customer perspective, and using the Software Value Map. A detailed illustration, via application in an industrial case at Ericsson AB, demonstrates usability and usefulness of the proposed extension. The case study results consist of two parts. First, the instantiation and motivations for selecting certain strategies have been provided. Second, the outcome of the value stream map is described in detail. Overall, the conclusion is that this case study indicates that Value Stream Mapping and the integration with the Software Value Map is useful in a software intensive product development context. In a retrospective the value stream approach was perceived positively by the practitioners with respect to process and outcome.

Place, publisher, year, edition, pages
Wiley , 2014. Vol. 26, no 12, 1074-1105 p.
Keyword [en]
value stream mapping, software engineering
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-6345DOI: 10.1002/smr.1647ISI: 000346649500002Local ID: oai:bth.se:forskinfoDCC88F333772F56CC1257D9D005257D5OAI: oai:DiVA.org:bth-6345DiVA: diva2:833842
Available from: 2015-05-26 Created: 2014-11-27 Last updated: 2015-06-30Bibliographically approved

Open Access in DiVA

fulltext(3789 kB)346 downloads
File information
File name FULLTEXT01.pdfFile size 3789 kBChecksum SHA-512
134c33de37e4d72722ad01e439700c3dca5be10027d8ffb9b6ef5d203a4dff64311b6d3d45fa94de0e40a0482fa406f363873e06106359942691f3282d0281de
Type fulltextMimetype application/pdf

Other links

Publisher's full text

Search in DiVA

By author/editor
Petersen, KaiGorschek, Tony
By organisation
Department of Software Engineering
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 346 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

doi
urn-nbn

Altmetric score

doi
urn-nbn
Total: 343 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf