Penggunaan Agile dan Scrum

Untuk Development Project

Basic Agile

Introduction to Agile

Agile adalah sebuah mindset untuk dapat bertindak cepat, adaptif dan fleksibel

yang terdiri dari 4 values dan 12 principles.

Pentingnya Agile bagi Business User

  1. Time to Market
  2. Ability to Change
  3. Accelerate Product Delivery & Feasibility
  4. Customer Satisfaction
  5. Business Existency

Pentingnya Agile bagi Project Team

  1. Collaboration IT & Business
  2. Removed Silo Mindset
  3. Self Organized

Agile Value dan Agile Principles

Agile Manifesto ditemukan pada 11-13 Februari 2001 di The Lodge, salah satu resort di Utah, Amerika Serikat yang terdiri dari 4 values dan 12 principles.

4 Agile Value

  1. Individuals and interactions over processes and tools
  2. Working software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan

12 Agile Principles

  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software
  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage
  3. Deliver working software frequently, from a couple of weeks

to a couple of months, with a preference to the shorter timescale

  1. Business people and developers must work together daily throughout the project
  2. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done
  3. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation
  4. Working software is the primary measure of progress
  5. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely
  6. Continuous attention to technical excellence and good design enhances agility
  7. Simplicity–the art of maximizing the amount of work not done–is essential
  8. The best architectures, requirements, and designs emerge from self-organizing teams
  9. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly


Leave a Reply