Abstract

Agile methodologies are at present widely used in industry. Many agile software development metrics are irrelevant to practitioners since they are dependent on the scope or content [Fenton and Neil, 2000]. Currently estimation is done by the team for each of the prioritized features [1] in order to commit to the number of features that can be implemented in each sprint. Each sprint is time-boxed; meaning the time to deliver is fixed. Risk in agile development is failing to deliver planned features in each sprint. There could be many reasons for not being able to deliver. Two of the reasons are discussed in this paper; one being incorrect time estimation and the other reason could be technical impediments. Actually the time taken to complete the task (feature implementation) depends on the proficiency of the development team and there has been no publication on estimation based on how and when to measure this. This is one of the gaps the research paper is trying to address. The scrum master assists the team in removing the impediments that obstructs the progress. In other words scrum master helps in facilitating productivity [2]. Hence, preparedness to resolve impediments as and when it arises is essential. This second risk is addressed by using semantic agents which is discussed in this paper.

References

• http://msdn. microsoft. com/en-us/library/hh273052(v=vs. 88). aspx
• www. scrummethodology. com/the-scrummaster-role/
• "Software Schedule Estimation and Uncertainty Surrounding the Cone of Uncertainty," T. Little, IEEE Software, May 2006, Vol. 23, No. 3
• http://guide. agilealliance. org/guide/daily. html.
• Glen B. Alleman," Agile Development Versus Traditional Development",2009, http://herdingcats. typepad. com/my_weblog/2009/06/agile-development-versus-traditional-development. html
• http://xp123. com/xplor/impediments/
• Mountain Goat Software ,"The Daily ScrumMeeting", http://www. mountaingoatsoftware. com/scrum/daily-scrum
• Scrum Guides ,"The Official Scrum Rule book" , http://www. scrum. org/Scrum-Guides
• Extreme programming ,"Daily Stand Up Meeting ", http://www. extremeprogramming. org/rules/standupmeeting. html
• Scrum methodology, "Scrum Impediments", http://scrummethodology. com/scrum-impediments/
• Joe Little," The Basics of SCRUM " May 30th, 2011
• http://ieeexplore. ieee. org/xpl/articleDetails. jsp?tp=&arnumber=6139390&queryText%3DPerformance+assessment+of+ASD+team+Using+Football+Rules+As+Reference
• http://ieeexplore. ieee. org/xpl/login. jsp?tp=&arnumber=5552340&url=http%3A%2F%2Fieeexplore. ieee. org%2Fxpls%2Fabs_all. jsp%3Farnumber%3D5552340-- A decision support system utilizing a semantic agent.
• Protègè OWL : http://protege. stanford. edu/overview/protege-owl. html
• Mike Griffiths," The Top Five Software Project Risks", http://www. projectsmart. co. uk/top-five-software-project-risks. html
• Vasant honavar," Tutorials- Intelligent Agents and Multi-Agent Systems", IEEE Conference on Evolutionary Computation (CEC), 1999
• Jin Pan, Stephen Cranefield and Daniel Carter, "A Lightweight Ontology Repository", International Foundation for Autonomous Agents and Multiagent Systems, AAMAS'03, 2003
• http://info. thoughtworks. com/rs/thoughtworks2/images/twebook-perspectives-estimation_1. pdf
• Colucci, S. ; Di Noia, T. ; Di Sciascio, E. ; Donini, F. M. ; Mongiello, M. ; Mottola, M"A Formal Approach to Ontology-Based Semantic Match of Skills Descriptions" Journal of Universal Computer Science Vol. 9, No. 12 2003,pp. 1437-1454
• http://docs. oracle. com/cd/E35215_01/admin. 11222/e35070/crawler_performance_metrics. htm
• Jørgensen, M. "A Review of Studies on Expert Estimation of Software Development Effort"