UX Design in Agile: A DSDM Case Study

Plonka, Laura; Sharp, Helen; Gregory, Peggy; Taylor, Katie

doi:10.1007/978-3-319-06862-6_1

Cited by 19 publications

(10 citation statements)

References 15 publications

(19 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…We discuss our findings with the organisation, engage in a dialogue with them about mitigation strategies and undertake research into changes made. We then publish our findings as academic papers for the research community [2][3][4] and as white papers for the practitioner community [5,6]. In order to find out what topics are most challenging for organisations, we have developed a 'Challenge Wall' (see Figure 1), deployed at five Agile Conferences and events between October 2013 and October 2014.…”

Section: Introductionmentioning

confidence: 99%

Agile Challenges in Practice: A Thematic Analysis

Gregory

Barroca

Taylor

et al. 2015

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

Abstract. As agile is maturing and becoming more widely adopted, it is important that researchers are aware of the challenges faced by practitioners and organisations. We undertook a thematic analysis of 193 agile challenges collected at a series of agile conferences and events during 2013 and 2014. Participants were mainly practitioners and business representatives along with some academics. The challenges were thematically analysed by separate authors, synthesised, and a list of seven themes and 27 sub-themes was agreed. Themes were Organisation, Sustainability, Culture, Teams, Scale, Value and Claims and Limitations. We compare our findings against previous attempts to identify and categorise agile challenges. While most themes have persisted we found a shift of focus towards sustainability, business engagement and transformation, as well as claims and limitations. We identify areas for further research and a need for innovative methods of conveying academic research to industry and industrial problems to academia.

show abstract

Section: Introductionmentioning

confidence: 99%

Agile Challenges in Practice: A Thematic Analysis

Gregory

Barroca

Taylor

et al. 2015

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

show abstract

“…DSDM has been developed from the experience gained by a large consortium of vendor and user organizations [17]. The main focus of DSDM is to deliver immediate business needs on time.…”

Section: C) Dynamic Systems Development Methodsmentioning

confidence: 99%

“…FDD is an agile software development process which uses short iteration model [17]. In FDD, the feature is an important aspect.…”

Section: D) Feature Driven Developmentmentioning

confidence: 99%

ScrumFall: A Hybrid Software Process Model

Rahim¹,

Chowdhury²,

Nandi³

et al. 2018

IJITCS

View full text Add to dashboard Cite

Every software project is unique in its own way. As a consequence, a single software process model cannot be suitable for all types of projects. In the real world, practitioners face different difficulties with the existing process models during development. Still, they cope up with the challenges by tailoring the software development lifecycle according to their needs. Most of these custom-tailored practices are kept inside the walls of the organizations. However, sharing these proven and tested practices as well as acquired knowledge and experience would be highly beneficial for other practitioners as well as researchers. So in this paper, we have presented a software process model which contains the characteristics of both Scrum and Waterfall model and named it "ScrumFall". This model has been practicing in an Anonymous Software Development Company, Bangladesh to solve the shortcomings of Scrum and Waterfall models. Moreover, we have analyzed the performance and suitability for applying this process model. The result shows that this process model is highly effective for the certain projects.

show abstract

“…Customer value as well as technical attributes and consequences are important factors to raise customer satisfaction in UX. Recently many researchers have presented the integrated approach of agile software development and user-centered design [25], [26]. Brhel et al [22] presented principles of user-centered agile software development (UCASD).…”

Section: Related Workmentioning

confidence: 99%

Value-Driven V-Model: From Requirements Analysis to Acceptance Testing

Han¹,

Lee²,

Choi

et al. 2016

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

SUMMARYThe goal of software testing should go beyond simply finding defects. Ultimately, testing should be focused on increasing customer satisfaction. Defects that are detected in areas of the software that the customers are especially interested in can cause more customer dissatisfaction. If these defects accumulate, they can cause the software to be shunned in the marketplace. Therefore, it is important to focus on reducing defects in areas that customers consider valuable. This article proposes a valuedriven V-model (V 2 model) that deals with customer values and reflects them in the test design for increasing customer satisfaction and raising test efficiency. key words: V-model, test design, value-based software engineering, customer value, customer satisfaction

show abstract

UX Design in Agile: A DSDM Case Study

Cited by 19 publications

References 15 publications

Agile Challenges in Practice: A Thematic Analysis

Agile Challenges in Practice: A Thematic Analysis

ScrumFall: A Hybrid Software Process Model

Value-Driven V-Model: From Requirements Analysis to Acceptance Testing

Contact Info

Product

Resources

About