Understanding the Introduction of Design Thinking as a Change Process

Martha Fritsch

A chapter in Design Thinking for Software Engineering, 2022, pp 115-126 from Springer

Abstract: Abstract When Design Thinking is introduced into software development projects, it is often done in an unstructured way and with a tendency to formulate goals only vaguely. It mostly is unclear at which points within the software development process the desired changes should be implemented. Moreover, the implementation of changes is often not initiated by the management but by an employee and testing on a project is conducted in a non-systematic way. Usually, such test projects fail and consequently does the introduction of Design Thinking. This contribution is not about the technical aspects of integrating Design Thinking into a software development process. It is rather intended as a contribution toward understanding the implementation of Design Thinking into software development as a change process, enabling us to deal with challenges, that may arise during the implementation itself in a more targeted way.

Keywords: Design thinking; Requirements engineering; Change management; Process; Introduction; Resistance; Communication (search for similar items in EconPapers)
Date: 2022
References: Add references at CitEc
Citations:

There are no downloads for this item, see the EconPapers FAQ for hints about obtaining it.

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:spr:prochp:978-3-030-90594-1_7

Ordering information: This item can be ordered from
http://www.springer.com/9783030905941

DOI: 10.1007/978-3-030-90594-1_7

Access Statistics for this chapter

More chapters in Progress in IS from Springer
Bibliographic data for series maintained by Sonal Shukla () and Springer Nature Abstracting and Indexing ().