scholarly journals Agile Software Development Framework in a Small Project Environment

2013 ◽  
Vol 9 (1) ◽  
pp. 69-88 ◽  
Author(s):  
Seiyoung Lee ◽  
Hwan-Seung Yong
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Development Framework ◽  
Project Environment ◽  
Small Project ◽  
Agile Software

Agile Software Development Quality Assurance

2009 ◽  
pp. 2680-2699
Author(s):  
James F. Kile ◽  
Maheshwar R. Inampudi
Keyword(s):  
Software Development ◽  
High Performance ◽  
General Rule ◽  
Adaptive Methods ◽  
Agile Software Development ◽  
Agile Development ◽  
Performance Requirements ◽  
Small Project ◽  
Software Development Methodologies ◽  
Agile Software

Of great interest to software development professionals is whether the adaptive methods found in agile methodologies can be successfully implemented in a highly disciplined environment and still provide the benefits accorded to fully agile projects. As a general rule, agile software development methodologies have typically been applied to non-critical projects using relatively small project teams where there are vague requirements, a high degree of anticipated change, and no significant availability or performance requirements (Boehm & Turner, 2004). Using agile methods in their pure form for projects requiring either high availability, high performance, or both is considered too risky by many practitioners (Boehm et al., 2004; Paulk, 2001). When one investigates the various agile practices, however, one gets the impression that each may still have value when separated from the whole. This chapter discusses how one team was able to successfully drive software development quality improvements and reduce overall cycle time through the introduction of several individual agile development techniques. Through the use of a common-sense approach to software development, it is shown that the incorporation of individual agile techniques does not have to entail additional risk for projects having higher availability, performance, and quality requirements.

Implementation of Change Management in Software Development by using Scrum Framework

2017 ◽  
Vol 7 (7) ◽  
pp. 400
Author(s):  
Rupali Pravinkumar Pawar ◽  
Kirti Nilesh Mahajan
Keyword(s):  
Software Development ◽  
Change Management ◽  
Implementation Process ◽  
Agile Software Development ◽  
Primary Data ◽  
Secondary Source ◽  
Process Of Change ◽  
Development Framework ◽  
Study Implementation ◽  
Agile Software

This paper will focus on implementation of change management in Scrum software development framework . Scrum is one of the mostly used software development framework from the Agile software development methodology. Scrum is based on iterative and incremental process. It is suitable for unstable  requirements. The use of Scrum proved to be beneficial due to tight schedule and loosely defined user requirements that often changed during the development. The aim of the paper to study  implementation process of change management in  Scrum . First part of paper gives detailed information of Scrum framework.  The middle of the paper presented the organizational process of agile software development using Scrum. Finally, the paper point out key points for managing changes in Scrum implementation.  The primary data collection method was interviews of the industry expertise. The secondary source of data is reference books and Internet articles. This paper will help to understand basics of Scrum software development framework and process of change management in developing projects by using Scrum framework.

Agile Software Development Quality Assurance

2011 ◽  
pp. 186-205
Author(s):  
J. Kile
Keyword(s):  
Software Development ◽  
High Performance ◽  
General Rule ◽  
Adaptive Methods ◽  
Agile Software Development ◽  
Agile Development ◽  
Performance Requirements ◽  
Small Project ◽  
Software Development Methodologies ◽  
Agile Software

Of great interest to software development professionals is whether the adaptive methods found in agile methodologies can be successfully implemented in a highly disciplined environment and still provide the benefits accorded to fully agile projects. As a general rule, agile software development methodologies have typically been applied to non-critical projects using relatively small project teams where there are vague requirements, a high degree of anticipated change, and no significant availability or performance requirements (Boehm & Turner, 2004). Using agile methods in their pure form for projects requiring either high availability, high performance, or both is considered too risky by many practitioners (Boehm et al., 2004; Paulk, 2001). When one investigates the various agile practices, however, one gets the impression that each may still have value when separated from the whole. This chapter discusses how one team was able to successfully drive software development quality improvements and reduce overall cycle time through the introduction of several individual agile development techniques. Through the use of a common-sense approach to software development, it is shown that the incorporation of individual agile techniques does not have to entail additional risk for projects having higher availability, performance, and quality requirements.

Coordination artifacts in Agile Software Development

2020 ◽  
Vol 30 (2) ◽  
pp. 100288 ◽  
Author(s):  
Anna Zaitsev ◽  
Uri Gal ◽  
Barney Tan
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Software

Reflections on Reflection in Agile Software Development

2006 ◽  
Author(s):  
D. Talby ◽  
O. Hazzan ◽  
Y. Dubinsky ◽  
A. Keren
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Software
Sign in / Sign up

Export Citation Format

Share Document