Open Access Open Access  Restricted Access Subscription or Fee Access

Effective Implementation of Agile Practices – A Collaborative and Innovative Framework

V. Esther Jyothi, K. Nageswara Rao


This paper introduces a collaborative and innovative framework of agile software development that leads to a software product that proves in practice to be of much higher quality than what traditional software teams usually deliver. Agile methods place more emphasis on people, interaction, working software, customer collaboration, and change rather than on tools, processes contracts and plans. A number of new methodologies claiming these agile principles have been introduced. Each method has its own active research and user communities


Communication, Continuous Integration, Framework, Metrics.

Full Text:



Weisert, C., (2002), The #1 Serious Flaw in Extreme Programming (XP), Information Disciplines, Inc., Chicago. [Online]. Available from:

M. Poppendieck and T. Poppendieck, Lean Software Development: An Implementation Guide: Addison- Wesley, 2006.

B. Boehm and R. Turner, "Using Risk to Balance Agile and Plan-Driven Methods," IEEE Computer, vol. 36, no. 6, pp. 57-66, June 2003.

K.El Emam,"Finding Success in Small Software Projects"Agile Project Management, vol. 4, no.11, 2003.

Coram, M., and Bohner, S., “The Impact of Agile Methods on Software Project Management”, In Proceedings of the 12th IEEE International Conference and Workshops on the Engineering of Computer-Based Systems (ECBS), April 2005, pp. 363-370.

Nerur, S., Mahapatra, R., and Mangalaraj, G., “Challenges of migrating to Agile methodologies”, Communications of the ACM, Vol. 48, No. 5, May 2005, pp. 72-78.

Maurer, F. and Martel, S. (2002a). Extreme programming: Rapid development for Web-based applications. IEEE Internet Computing 6(1): 86-90.

Jeffries, R., Anderson, A. and Hendrickson, C. (2001). Extreme Programming Installed. Upper Saddle River, NJ, Addison-Wesley.

Highsmith, J. and Cockburn, A. (2001). Agile Software Development: The Business of Innovation. Computer 34(9): 120-122.

Schwaber, K. and Beedle, M. (2002). Agile Software Development with Scrum. Upper Saddle River, NJ, Prentice-Hall.

E. Arisholm, Gallis, H.E., Dybå, T., Sjøberg, D., Evaluating Pair Programming with Respect to System Complexity and Programmer Expertise", IEEE Transactions in Software Engineering, pp. 65-86, 2007.

Robert C. Martin, Agile Software Development, Principles, Patterns, and Practices, Prentice Hall, 2002

Agrawal and K. Chari, “Software Effort, Quality, and Cycle Time: A Study of CMM Level 5 Projects,” IEEE Trans. Software Eng., vol. 33, no. 3, pp. 145-156, Mar. 2007.

Baker, Steven W. Formalizing Agility: An Agile Organization’s Journey toward CMMI Accreditation. Agile 2005 Proceedings, IEEE Press, 2005.

Alleman, Glen. Agile Program Management: Moving from Principles to Practice. Agile Product & Project Management, Vol. 6 No. 9, Cutter Consortium, September, 2005.

Leffingwell, Dean, Scaling Software Agility: Best Practices for Large Enterprises, Addison-Wesley Professional, 2007.

Palmer, S. R., and J. M. Felsing. 2002. A practical guide to feature-driven deelopment. Upper Saddle River, N.J.: Prentice Hall PTR.

Anderson, David J., and Eli Schragenheim, Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results, Prentice Hall, 2003.

Poppendieck, Mary and Tom Poppendieck, Lean Software Development: An Agile Toolkit. Addison Wesley Professional, 2003.

Ming Huo, June Verner, Liming Zhu, Mohammad Ali Babar, “Software Quality and Agile Methods”, COMPSAC ’04, IEEE 2004.

Craig Larman, Victor R. Basili. Iterative and Incremental Development: A Brief History, 0018-9162/03/ © 2003 IEEE


  • There are currently no refbacks.

Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 License.