Case study: factors for early prediction of software development success

Recurring opinions or productive improvements—what agile teams actually discuss in retrospectives

“…The existing literature has presented a wide array of factors affecting the software development outcomes (McLeod and MacDonell 2011). Prior studies show that the factors are related to the entire software development lifecycle; for example, the factors of better understanding the sales, user and customers (Keil et al 1998;Moløkken-Østvold and Jørgensen 2005;Drew Procaccino et al 2002;Cerpa et al 2010), of determining the requirements (McLeod and MacDonell 2011), and of focusing on quality control and software testing (Jones 2008;Kaur and Sengupta 2011;Egorova et al 2010). Based on our results, however, it seems that teamlevel retrospectives are weak at recognising issues and successes related to the process areas that are external to the concerns of the teams (eg sales & requirements, general management and the product owner).…”

Eliciting user requirements using Appreciative inquiry

“…Stability is the extent that requirements change over the course of the project; it is usually defined as instability since changing requirements introduce risk to project success; diversity is the extent to which requirements differ and are not consistent; and analyzability is the extent that a user's need can be translated to a requirement (Moynihan, 2000). Requirements uncertainty and instability are measured by the degree that a requirement changes during the development process (Barney, Aurum, & Wohlin, 2008;Hsu, Chan, Liu, & Chen, 2008); and participant prediction for future project success (Procaccino, Verner, Overmyer, & Darter, 2002). Diversity was measured by the uniqueness of the requirement if it was not previously identified.…”

“…These are reported as expected outcomes from Appreciative Inquiry sessions (Cooperrider, 2008;Hammond, 1998). Additionally, the following measures were added: Commitment, buy-in and motivation (Kauppinen, Vartiainen, Kontio, Kujala, & Sulonen, 2004), and perception of project success or failure as measured by confidence in results (Procaccino, et al, 2002). A survey was provided to participants to measure these items.…”

Risk management automation of software projects based оn fuzzy inference

“…Терехова, Т. ДеМарко, Т. Листера. В научных исследованиях выявлены проблемы управления рисками в проектах разработки программного обеспечения [2], разработаны инструменты и методы управления рисками [3], описаны факторы рисков [4] и методики профилактического управления рисками на ранних стадиях программных проектов [5].…”