1 / 13

Agile Software Development

Agile Software Development. Agenda. What is „Agility“?. „Agility is the ability to both create and respond to change in order to profit in a turbulent buisness environment.“ [Jim Highsmith, Agile Software Development Ecosystems, Preface XXIII]. Chaordic – Chaos mixed with order.

hina
Download Presentation

Agile Software Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agile Software Development JASS 2006

  2. Agenda JASS 2006

  3. What is „Agility“? „Agility is the ability to both create and respond to change in order to profit in a turbulent buisness environment.“ [Jim Highsmith, Agile Software Development Ecosystems, Preface XXIII] JASS 2006

  4. Chaordic – Chaos mixed with order • Natural blend of Chaos and Order • Most organisations and projects exhibt chaordic structures • Is about self-organisation and self-governance, evolutionary like nature • Often used to describe agile software development processes. JASS 2006

  5. Management and Developing before Agile • Countermovement to heavy and bureaucratic software development processes • Waterfall • V-Modell • Beginning in the early 1990ies, became publically known in 1999 with Kent Becks „Extreme Programming“ JASS 2006

  6. Agile Manifesto • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan [Source: Agile Manifesto, http://agilemanifesto.org, 3/29/2006 ] JASS 2006

  7. This does NOT mean... • ... processes and tools don‘t matter. • ... that we need no documentation. • ... that we need no contracts. • ... make a plan and follow it is obsolete. JASS 2006

  8. Principles • Keep it { simple, small } and { stupid, straigthforward, smart } (KISS) • Use resources carefully • „Chaordic“ nature of projects and organisations JASS 2006

  9. Flavours of Agile Development JASS 2006

  10. Extreme Programming • iterative • adaptive • continous integration/build • became generally known with Kent Beck JASS 2006

  11. Scrum • living backlog of prioritized work to be done • Completion of a fixed set of backlog items in a series of short iterations (sprints) • Brief planning session to define backlog items for the next sprint • Retrospective for all team members to reflect the last sprint JASS 2006

  12. Crystal • Different methods for different group sizes • Common feature set: • Frequent Delivery • Reflective Improvement • Close Communication • „Crystal Clear“ most known JASS 2006

  13. Any questions? JASS 2006

More Related