Agile Methods

Agile Methods

 

Add a note hereMethods (also called methodologies, although, strictly speaking they are not the same) play a crucial role in software projects. This is particularly so in large projects that include myriad variables such as people, technologies, risks, changing requirements, and fluctuating stakeholders. These variables are far too many to be handled by a single person in the role of a project manager. When the project requires a group of developers to work together, then coordinating and managing their tasks, expectations, and understanding, together with the demands of the customer, becomes highly complex.

Add a note hereFigure 1.2 illustrates the variables of time, budget, functionality, and quality. Balancing these four variables together with the interests of various stakeholders is a complex need that keeps changing from project to project. Methods are an attempt to learn from previous attempts at software development, and then abstract and enshrine these lessons in a discipline. Chapman (2007) describes a software development methodology as a documented set of policies, processes, and procedures employed in the development of an information system. Methods help to abstract, generalize, formalize, unify, and standardize the approaches to software development and maintenance.

Add a note herePlanned methods, in particular, isolate (or at least minimize) the impact of the product quality from the caliber of the individuals. As a result of these, methods equip the management to estimate the time, budget, and resources required in a project at an early stage of the project.

Add a note hereAgile methods, however, are a different brand of methods that subscribe to the Agile Manifesto. Instead of isolating the individual, these Agile methods encourage and respect the subjectivity of an individual and align it in a team effort. Some of these Agile methods have been quite popular and well accepted by the developers. Customers (users), who see the advantages of visible development, are also highly supportive of these approaches. The following is a list of methods belonging to the Agile family:

  • Add a note hereExtreme programming (XP) by Beck (2000): Perhaps this is the very first Agile method that is based on simple programming principles and focuses on individuals.

  • Add a note hereScrum (Schwaber, 1995; Schwaber and Beedle, 2001): This is the most popular of all Agile methods; it focuses on business value through demonstration and prioritization. The daily and 2- to 4-week cycles work well in practice.

  • Add a note hereCrystal (Cockburn, 2004): This is a family of methods that is applicable to varying development scenarios depending on size and criticality of the projects. However, the range of applicability varies, depending on essential money, discretionary money, and comfort.

  • Add a note hereFeature-driven development (FDD) (Palmer and Felsing, 2002): This is based around selection and integration of various development techniques to deliver prioritized features.

  • Add a note hereAdaptive software development (Highsmith, 2000): This method continuously adapts/modifies the process to cater to the rapidly changing development situation and is based on the speculate–collaborate–learn phases.

  • Add a note hereDynamic systems development method (Stapleton, 1997): This is an iterative and incremental approach with heavy emphasis on continuous user involvement.

  • Add a note hereTest-driven development (Beck, 2002): This method is based on the philosophy of writing the test cases first, before writing the code that is supposed to pass the test cases. It enables focus on quality and purpose of the code. Once the tests are passed, development can include refactoring of the code for future reuse.

Add a note hereA study of these methods and abstraction of their commonalities (described in detail in Chapter 2) forms the basis for the creation of a "composite" approach. Such composite Agile approach can be applied across an organization or to a program of work. This composite Agile approach to projects as well as organizations is envisaged as a very practical means of the use of methods. It forms the basis of most of the discussions in this book.

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值