Model Proses Perangkat Lunak AGILE

Roger Pressman mengemukakan beberapa hal terkait model proses perangkat lunak agile (lunak); yakni:

Agile software engineering represents a reasonable compromise between to conventional software. 

Agile development processes can deliver successful systems quickly

Agile development stresses continuous communication and collaboration among developers and customers

Agile software engineering embraces a philosophy that encourages customer satisfaction, incremental software delivery, small project teams (composed of software engineers and stakeholders), informal methods, and minimal software engineering work products 

Agile software engineering development guidelines stress on-time delivery of an operational software increment over analysis and design (the only really important work product is an operational software increment)

Yang dapat dipahami dari pendapat Roger Pressman tersebut adalah model proses agile merupakan suatu model proses perangkat lunak yang menitikberatkan pada membangun perangkat lunak yang cepat, dan di-delivered kepada pengguna dengan cepat.

Apakah paradigma agile berarti "mengabaikan" disiplin software engineering? Tentu saja tidak! Karena yang namanya "process model" tentu saja, masih ber-proses. Dan proses memiliki pentahapan dengan sejumlah aktivitas tertentu yang harus dikerjakan. Pendapat saya, model proses agile, harus dipahami dalam konteks melibatkan user (dan stakeholders lainnya) secara penuh dalam pengembangan perangkat lunak; dengan terus-menerus mengadopsi kebutuhan user (yang akan cenderung berubah-ubah); dengan demikian harus memiliki tim pengembang yang siap dengan perubahan.

Silahkan melihat juga tulisan saya tentang Paradigma Web 2.0: Agile Process disini:

http://stanlysk.blogspot.com/2012/05/paradigma-web-20-agile-process.html

Pressman mengemukakan beberapa prinsip terkait model proses agile, diantaranya adalah:

1. Highest priority is to satisfy customer through early and continuous delivery of valuable software

2. Welcome changing requirements even late in development, accommodating change is viewed as increasing the customer’s competitive advantage

3. Delivering working software frequently with a preference for shorter delivery schedules (e.g. every 2 or 3 weeks)

4. Business people and developers must work together daily during the project

5. Build projects around motivated individuals, given them the environment and support they need, trust them to get the job done

6. Face-to-face communication is the most effective method of conveying information within the development team

7. Working software is the primary measure of progress

8. Agile processes support sustainable development, developers and customers should be able to continue development indefinitely

9. Continuous attention to technical excellence and good design enhances agility

10. Simplicity (defined as maximizing the work not done) is essential

11. The best architectures, requirements, and design emerge from self-organizing teams 

12. At regular intervals teams reflects how to become more effective and adjusts its behavior accordingly

Dari pengalaman saya, dalam mengembangkan perangkat lunak dengan pendekatan agile, maka prinsip utama yang harus dimiliki adalah KOMITMEN. Yakni komitmen tim pengembang dan komitmen stakeholders untuk terlibat dalam pengembangan perangkat lunak sepenuhnya. Tidak ada prinsip kunci lain yang dibutuhkan dalam pengembangan agile.

Silahkan lihat disini, sebuah contoh model proses pengembangan perangkat lunak dengan pendekatan agile:

Bagian Pertama: http://stanlysk.blogspot.com/2012/06/research-paper-web-portal-ans.html

Bagian Kedua: http://stanlysk.blogspot.com/2012/06/research-paper-web-portal-ans-part-ii.html

Pressman mengemukakan beberapa varian dari model proses agile yakni:

Extreme Programming (XP)

Adaptive Software Development (ASD)

Scrum

Dynamic Systems Development Method (DSDM)

Crystal

Feature Driven Development (FDD)

Lean Software Development (LSD)

Agile Modeling (AM)

Agile Unified Process (AUP)

Universitas Indonesia (dalam ini Pusat Ilmu Komputer UI) mengemukakan sebuah model proses agile yang disebut PAUS (Pusilkom Agile Unified Process). Selengkapnya dapat dilihat pada link ini: http://ecl.cs.ui.ac.id/PAUS/index.htm