![](bg8.png)
executions: 8 out of 10 Scrum projects are
successful according to half of the participants. The
survey participants valued the main characteristics
of Agile processes that generally assist in achieving
increased productivity and producing software
systems of higher quality.
The adoption of Scrum seems indeed to be wide
and many books and articles are centred around its
use. Nevertheless, continuous studies are necessary
to follow its adoption progress and the emerging
variants, especially its combination with other
production methods, such as Kanban. Hybrid Agile
methods and their effectiveness under different
environments are an interesting field of study in
software processes.
REFERENCES
Atlas, A., 2009. Accidental Adoption: The Story of Scrum
at Amazon.com, In Agile Conference, pp. 135-140.
Benefield, G., 2008. Rolling Out Agile in a Large
Enterprise, In 41st Annual Hawaii International
Conference on System Sciences, pp. 461.
Gao, Y., Yong-hua Y., 2012. “Flexibility” of Software
Development Method. Advances in Multimedia,
Software Engineering and Computing, Springer Berlin
Heidelberg, vol. 128, pp. 383-387.
Hajjdiab, H., Taleb, A. S., Ali, J., 2012. An Industrial
Case Study for Scrum Adoption, Journal of Software,
vol. 7, no. 1, pp. 237-242.
Highsmith, J., Cockburn, A., 2001. Agile software
development: the business of innovation, IEEE
Computer, vol. 34, no. 9, pp.120-127.
Kurapati, N., Sarath, V., Manyam, C., Petersen, K., 2012.
Agile Software Development Practice Adoption
Survey, Agile Processes in Software Engineering and
Extreme Programming, vol. 111, no. 1, pp. 16-30.
. Leau, Y. B., Loo, W. K., Tham, W. Y., Tan, S. F., 2012.
Software Development Life Cycle AGILE vs
Traditional Approaches. In International Conference
on Information and Network Technology, pp. 162-167.
Moore, G. A., 2002. Crossing the Chasm: Marketing and
Selling Disruptive Products to Mainstream Customers,
Harper Business Essentials.
Paulk, M., 2011. On Empirical Research Into Scrum
Adoption, Carnegie Mellon University, viewed 5
February 2014, http://www.cs.cmu.edu/~mcp/agile/
oersa.pdf
Petersen, K., Wohlin, C., 2009. A comparison of issues
and advantages in Agile and incremental development
between state of the art and an industrial case, Journal
of Systems and Software, vol. 82, no. 9, pp. 1479-
1490.
Schatz, B., Abdelsha, I., 2005. Primavera gets Agile: a
successful transition to Agile development, IEEE
Software, vol. 22, no., 3, pp. 36-42.
Scrum Alliance, 2013. The State of Scrum: Benchmarks
and Guidelines, viewed 5 February 2014.
Scwaber, K., Beedle, M., 2002. Agile Software
Development with Scrum, Prentice Hall.
Shine technologies, 2003. Agile methodologies survey
results, viewed 5 February 2014, http://
www.shinetech.com/attachments/104_ShineTechAgile
Survey2003-01-17.pdf.
Statistics Canada, 2003. Survey Methodology, viewed 5
February 2014, http://www.statcan.gc.ca/pub/12-587-
x/12-587-x2003001-eng.pdf.
Sugimori, Y., et al., 1977. Toyota production system and
kanban system materialization of just-in-time and
respect-for-human system. The International Journal
of Production Research, vol. 15,.no. 6, pp. 553-564.
VersionOne survey, 2010. The state of Agile development,
viewed 5 February 2014, http://www.scribd.com/doc/
45835357/2010-State-of-Agile-Development-Survey-
Results.
Vijayasarathy, L. R., Turk, D., 2008. Agile software
development: a survey of early adopters, Journal of
Information Technology Management, vol. 14, no. 2,
pp. 1-8.
West, D., 2010. Agile Systems Integrators: Plausible Or
Paradoxical?, Application Development & Delivery
Professionals.
Williams, L., Brown, G., Meltzer, A., Nagappan, N., 2011.
Scrum + Engineering Practices: Experiences of Three
Microsoft Teams, In International Symposium on
Empirical Software Engineering and Measurement,
pp. 463-471.
Yin, R. K., 2008. Case study research: Design and
methods, Sage Publications, Incorporated.
ENASE2014-9thInternationalConferenceonEvaluationofNovelSoftwareApproachestoSoftwareEngineering
108