CFP last date
22 April 2024
Reseach Article

Managing Versioning Activities to Support Tracking Progress of Distributed Agile Teams

by Sultan Alyahya, Wendy K. Ivins, W. A. Gray
International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 39 - Number 16
Year of Publication: 2012
Authors: Sultan Alyahya, Wendy K. Ivins, W. A. Gray
10.5120/4903-7405

Sultan Alyahya, Wendy K. Ivins, W. A. Gray . Managing Versioning Activities to Support Tracking Progress of Distributed Agile Teams. International Journal of Computer Applications. 39, 16 ( February 2012), 12-19. DOI=10.5120/4903-7405

@article{ 10.5120/4903-7405,
author = { Sultan Alyahya, Wendy K. Ivins, W. A. Gray },
title = { Managing Versioning Activities to Support Tracking Progress of Distributed Agile Teams },
journal = { International Journal of Computer Applications },
issue_date = { February 2012 },
volume = { 39 },
number = { 16 },
month = { February },
year = { 2012 },
issn = { 0975-8887 },
pages = { 12-19 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume39/number16/4903-7405/ },
doi = { 10.5120/4903-7405 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-06T20:26:46.863687+05:30
%A Sultan Alyahya
%A Wendy K. Ivins
%A W. A. Gray
%T Managing Versioning Activities to Support Tracking Progress of Distributed Agile Teams
%J International Journal of Computer Applications
%@ 0975-8887
%V 39
%N 16
%P 12-19
%D 2012
%I Foundation of Computer Science (FCS), NY, USA
Abstract

Development Progress in agile methods is based on the amount of “working software” completed by team members. Changes to the source code might be introduced that affect the working software. Team members face difficulties in understanding and sharing changes that affect development progress especially in distributed projects. They may not recognise that there is an effect, or may not know who is affected by a change. In addition, changes are not perceived by the current tracking systems and hence if these changes affect development progress, they will not be discovered. This may lead to weak awareness of development progress and extra defects and delays. In this paper, we attempt to support tracking distributed agile projects by identifying and co-ordinating the impact of versioning activities on development progress, thereby ensuring that progress information is more consistent with the current software state. This will provide distributed agile teams with improved transparency of the actual progress.

References
  1. Beck, K., Extreme Programming Explained: Embrace Change, Addison-Wesley, 2004.
  2. Agile Alliance, Manifesto for Agile Software Development, URL: http://www.agilemanifesto.org/principles.html, Cited 15 January 2012.
  3. Sauer, J., Agile Practices in Offshore Outsourcing - An Analysis of Published Experiences. Proceedings of the 29th Information Systems Research, 2006.
  4. Peng Xu - Coordination In Large Agile Projects Review of Business Information Systems (RBIS), 2011.
  5. Rally, URL: http://www.rallydev.com/, Cited 15 January 2012.
  6. Mingle, http://studios.thoughtworks.com/mingle-agile-project-management, Cited 15 January 2012..
  7. TargetProcess, URL: http://www.targetprocess.com/, 15 January 2012..
  8. VersionOne, URL: http://www.versionone.com/, 15 January 2012.
  9. Asklund, U., Bendix, L. & Ekman, T., 2004. Software Configuration Management Practices for eXtreme Programming Teams. Management, p.1-16. Cockburn, A., Highsmith, J. Agile Software Development: The Business of Innovation. Computer, 2001, Vol. 34, No. 9, pp. 120–122.
  10. Appleton, B., Cowham, R., and Berczuk, S., Lean Traceability: A smattering of strategies and solutions, CM Journal, 2007.
  11. Cockburn, A., Highsmith, J., Agile Software Development: The Business of Innovation, IEEE Computer, 2001, Vol. 34, No. 9, pp. 120–122.
  12. Cockburn, A. Agile Software Development. Boston: Addison-Wesley, 2002.
  13. Koskela, J., Software Configuration Management in Agile Methods, VTT Publication, Finland, 2003.
  14. Jeffries, R., Anderson, A., Hendrickson, C. Extreme Programming Installed. NJ: Addison-Wesley, 2001.
  15. Lippert, M., Roock, S., Wolf, H. Extreme Programming in Action: Practical Experiences from Real World Projects. England: John Wiley & Sons, 2002.
  16. Alyahya, S., Ivins, WK., Gray, WA., Co-ordination Support for Managing Progress of Distributed Agile Projects, IEEE International Conference on, pp. 31-34, 2011 IEEE Sixth International Conference on Global Software Engineering Workshop, 2011.
  17. Fowler, M., Continuous Integration. Integration The Vlsi Journal, 26(1), p.1-6. 2006, Available at: http://martinfowler.com/articles/continuousIntegration.html
  18. Go, URL: http://thoughtworks-studios.com/go-agile-release-management. Cited 15 January 2012.
  19. Katz, R.H., Chang E. and Anwarrudia M. "A Version server for Computer-Aided Design Data. In Proceedings of ACM/IEEE 23rd Design Automation Conference, Las Vegas, U.S.A, pp 27-33, Jun 1986.
  20. Chou, H.T. and W. Kim.: “A Unifying Framework for Version Control in a CAD Environment” In Proceedings of the 12th International Conference on Very Large Databases, Kyoto, Japan, pp 336-344, Aug 1986.
  21. Ivins W K, Gray W A, Miles J C, A process-based approach to managing changes in a system to support engineering product design, Proc of the Engng Design Conf , (2002) 469-478 ISBN 1 86058 372 5.
  22. Zimmermann, T., Changes and Bugs: Mining and Predicting Software Development Activities, Books on Demand Gmbh, 2009.
  23. Geipel, M., & Schweitzer, F.: Software change dynamics: evidence from 35 java projects, ESEC/SIGSOFT FSE, 2009.
  24. Jeffries, R., A Metric Leading to Agility, in XProgramming, 2004.
Index Terms

Computer Science
Information Sciences

Keywords

Distributed Agile Development Versioning System Co-ordination Progress Tracking