A decade of agile methodologies: Towards explaining agile software development

Dingsøyr, Torgeir; Nerur, Sridhar; Balijepally, VenuGopal; Moe, Nils Brede

doi:10.1016/j.jss.2012.02.033

Cited by 826 publications

(601 citation statements)

References 49 publications

Supporting

Mentioning

521

Contrasting

Unclassified

Order By: Relevance

“…SDPs use different stakeholders who are people that are involved in getting them executed, completed and making a decision whether they are successful or not [15]. These stakeholders require two sets of skills namely soft skills and technical skills.…”

Section: A Skills For Software Project Stakeholdersmentioning

confidence: 99%

See 1 more Smart Citation

Soft Skills for Software Project Team Members

Mtsweni¹,

Hörne²,

Poll³

2016

IJCTE

View full text Add to dashboard Cite

Abstract-Software development usually occurs in the context of software project management (SPM). An often cited challenge in the area of software project management is the high failure rate of software development projects (SPDs). One of the factors contributing to the failure of SDPs is the lack of soft issues, also known as soft skills or human aspects. The main purpose of this research was to identify and categorise the soft skills that facilitate the delivery of successful SDPs. To this end a survey was conducted in the form of a questionnaire as the research instrument. The results of the survey underwent a quantitative analysis and it was found that a variety of soft skills are important in facilitating the delivery of successful SDPs. Although a wide range of soft skills were identified, not all soft skills can be considered to be of crucial or equal importance. Index Terms-Soft skills, software development projects, software project failure.

show abstract

Section: A Skills For Software Project Stakeholdersmentioning

confidence: 99%

“…The main purpose of conducting SDPs is to address the challenges the end users are facing [1]. The success of SDPs also depends on end users because they are the ones who are going to use the end product [15].…”

Section: Different Stakeholders For Software Development Projectsmentioning

confidence: 99%

Soft Skills for Software Project Team Members

Mtsweni¹,

Hörne²,

Poll³

2016

IJCTE

View full text Add to dashboard Cite

show abstract

“…The model building strategy was based on agile methods [39] including time-boxed iterations and pair working (modeler and clinician). The team included health economists, software engineers, data miners, business analysts and clinicians from the study areas.…”

Section: Iterative Approach To Model Developmentmentioning

confidence: 99%

NETIMIS: Dynamic Simulation of Health Economics Outcomes Using Big Data

2016

View full text Add to dashboard Cite

Many healthcare organizations are now making good use of e-health record (EHR) systems to record clinical information about their patients and the details of their healthcare. Electronic data in EHRs is generated by people engaged in complex processes within complex environments and their human input, albeit shaped by computer systems, is compromised by many human factors. This data is potentially valuable to health economists and outcomes researchers but is sufficiently large and complex enough to be considered part of the new frontier of "big data". This paper describes emerging methods that draw together data mining, process modeling, activity based costing and dynamic simulation models. Our research infrastructure includes safe links to Leeds hospital's EHR with 3 million secondary and tertiary care patients. We created a multi-disciplinary team of health economists, clinical specialists, data and computer scientists and developed a dynamic simulation tool called NETIMIS (www.netimis.com) suitable for visualization of both human-designed and data-mined processes which can then be used for "what-if" analysis by stakeholders interested in costing, designing and evaluating healthcare interventions. We present two examples of model development to illustrate how dynamic simulation can be informed by big data from an EHR. We found the tool provided a focal point for multi-disciplinary team work to help them iteratively and collaboratively "deep dive" into big data. Key Points for Decision Makers Big data can be defined as a data at a scale where research become uncomfortable -the point where existing methods are unable to unlock the value in the data.  Electronic health records (EHR) are a type of big data that will be valuable to future health economists and outcomes researchers but the data is messy, it is the human product of large numbers of individuals working in complex environments. Solutions have yet to emerge.  We found that the use of a dynamic simulation tool provided an effective focal point for multidisciplinary investigations into the messy world of EHR big data and the development of valuable insights.2

show abstract

“…Most companies introduce agile methods to increase the frequency in which they release new features and new products, and as a way to improve their software engineering efficiency. According to Dingsøyr et al [5], agility embraces lean processes with an emphasis on realizing effective outcomes, and common for agile methods is that they entail the ability to rapidly and flexibly create and respond to change in the business and technical domains [5].…”

Section: Related Workmentioning

confidence: 99%

Expectations and Challenges from Scaling Agile in Mechatronics-Driven Companies – A Comparative Case Study

Berger

Eklund

2015

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. Agile software development is increasingly adopted by companies evolving and maintaining software products to support better planning and tracking the realization of user stories and features. While convincing success stories help to further spread the adoption of Agile, mechatronics-driven companies need guidance to implement Agile for non-software teams. In this comparative case study of three companies from the Nordic region, we systematically investigate expectations and challenges from scaling Agile in organizations dealing with mechatronics development by conducting on-site workshops and surveys. Our findings show that all companies have already successfully implemented Agile in their software teams. The expected main benefit of successfully scaling agile development is a faster time-to-market product development; however, the two main challenges are: (a) An inflexible test environment that inhibits fast feedback to changed or added features, and (b) the existing organizational structure including the company's mind-set that needs to be opened-up for agile principles.

show abstract

A decade of agile methodologies: Towards explaining agile software development

Cited by 826 publications

References 49 publications

Soft Skills for Software Project Team Members

Soft Skills for Software Project Team Members

NETIMIS: Dynamic Simulation of Health Economics Outcomes Using Big Data

Expectations and Challenges from Scaling Agile in Mechatronics-Driven Companies – A Comparative Case Study

Contact Info

Product

Resources

About