The Use of Design Thinking in Agile Software Requirements Survey: A Case Study

Canedo, Edna Dias; Costa, Ruyther Parente da

doi:10.1007/978-3-319-91797-9_45

Cited by 13 publications

(5 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…2. In addition, a third paradigm in new product development has gained in popularity in the last decade; that is, design thinking [9], [10]. This design model emphasizes on close collaboration with the end users during the development phases of a new product, starting with the process of need investigation, continuing with a deep understanding of users from multiple perspectives (roles), and then following an incremental process of solution formulation by looping ideas and prototypes in close collaboration with beneficiaries of solution [10], [11].…”

Section: Fig 2 Lean Innovation Methodologymentioning

confidence: 99%

CALDET: A TRIZ-Driven Integrated Software Development Methodology

Brad

Homorodean³

2019

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

Companies specialized in software development services and software outsourcing have adopted agile methodologies such as SCRUM and Kanban to drive the software development process. Along time, experts have introduced new methodologies that enhance agile roadmaps with lean patterns and design thinking tools. Despite the value added brought by aggregation of agile with lean and design thinking, the integrated methodology is still fuzzy at operational level. There is no scientific demonstration on the most appropriate way to alternate the steps of agile with those promoted by lean innovation and design thinking. This niche of opportunity is investigated by this paper. Conflicts and barriers generated by aggregation are treated with TRIZ. Inventive solutions are proposed to optimize the agile-lean-design thinking (ALDET) software development process considering a life-cycle perspective. Gaps identified in ALDET are additionally tackled with TRIZ and new tools of competitive engineering, including TRIZ contradiction matrix for software, are embedded within the optimized ALDET to enhance its potentiality. The methodology is called Competitive ALDET or CALDET. Its effectiveness was tested in a real project. Preliminary results demonstrate that CALDET provides a clearer and smoother path for project management, reduces ambiguities relative to traditional ALDET methodology, and increases the impact of outcomes to the user. By tackling conflicts in an iterative manner, CALDET avoids re-analysis and re-coding in software development, too. The presence of value engineering tools within the framework of CALDET reveals additional spaces of innovation, both technical and project management related.

show abstract

Section: Fig 2 Lean Innovation Methodologymentioning

confidence: 99%

CALDET: A TRIZ-Driven Integrated Software Development Methodology

Brad

Homorodean³

2019

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

show abstract

“…Many agile techniques have been developed, including crystal methodologies, dynamic software development method (DSDM), extreme programming, scrum, lean software development, and feature-driven development [10]. Agile software development's main objective is to generate quality software products cost-effectively through a series of short iterative and incremental development cycles [12]. Having originated in software development [11], agile software development is used in many industries, including for developing digital banking platform [13].…”

Section: The Concept Of Design Thinkingmentioning

confidence: 99%

Adoption of Design Thinking, Agile Software Development and Co-creation: A Qualitative Study towards Digital Banking Innovation Success

Indriasari¹,

Prabowo²,

Gaol³

et al. 2022

IJETAE

View full text Add to dashboard Cite

Digitalization in the financial sector challenges banking institutions to develop new methods of innovation processes by incorporating current concepts such as design thinking (DT), agile software development (ASD), and cocreation. This qualitative study is based on empirical research conducted at three Indonesian banks. Semi-structured interviews with three IT executives and a questioner of 31 middle managers participating in digital banking efforts were used to gather data. A Systematic Literature Review based on Kitchenheim processes generates keywords in the VOS Viewer software. NVIVO 12 qualitative software is employed to aid data analysis for illustrating the process integration. The research's contribution is identified, including process integration, obstacles, potential solutions, and enhanced framework on adopting DT, ASD, and Co-creation. Keywords— design thinking, agile software development, co-creation, Innovation

show abstract

“…To do so, we observe participants in a simulation of a situation where a software team is given a set of TRS and then asked to design an appropriate application. Although RE and highlevel designing are increasingly merged (e.g., [93]- [95]), such situations arise often in outsourcing arrangements (where the outsourcer provides a questionable requirements specification and expects the team to develop mock-ups without much access to prospective users or client representatives). In our experience, many software teams that have stakeholder access still have specifications forced upon them by clients, management, marketing or other stakeholders.…”

Section: Purpose and Scenariomentioning

confidence: 99%

How Templated Requirements Specifications Inhibit Creativity in Software Engineering

Mohanani

Ralph

Turhan

et al. 2022

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Desiderata is a general term for stakeholder needs, desires or preferences. Recent experiments demonstrate that presenting desiderata as templated requirements specifications leads to less creative solutions. However, these experiments do not establish how the presentation of desiderata affects design creativity. This study, therefore, aims to explore the cognitive mechanisms by which presenting desiderata as templated requirements specifications reduces creativity during software design. Forty-two software designers, organized into 21 pairs, participated in a dialog-based protocol study. Their interactions were transcribed and the transcripts were analyzed in two ways: (1) using inductive process coding and (2) using an a-priori coding scheme focusing on fixation and critical thinking. Process coding shows that participants exhibited seven categories of behavior: making design moves, uncritically accepting, rejecting, grouping, questioning, assuming and considering quality criteria. Closed coding shows that participants tend to accept given requirements and priority levels while rejecting newer, more innovative design ideas. Overall, the results suggest that designers fixate on desiderata presented as templated requirements specifications, hindering critical thinking. More precisely, requirements fixation mediates the negative relationship between specification formality and creativity.

show abstract

The Use of Design Thinking in Agile Software Requirements Survey: A Case Study

Cited by 13 publications

References 15 publications

CALDET: A TRIZ-Driven Integrated Software Development Methodology

CALDET: A TRIZ-Driven Integrated Software Development Methodology

Adoption of Design Thinking, Agile Software Development and Co-creation: A Qualitative Study towards Digital Banking Innovation Success

How Templated Requirements Specifications Inhibit Creativity in Software Engineering

Contact Info

Product

Resources

About