Agile 101

Tech Talk Tuesday
June 12th, 2018

Topics

  • Agile Manifesto
  • Agile Principles
  • Agile in Practice
  • Open Discussion

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

Agile Manifesto

  • Created in 2001
  • Involved representatives of Scrum, XP, and others
  • Meant to be "an alternative to documentation driven, heavyweight software development processes"

Agile Principles

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

Agile Principles

Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

Agile Principles

Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

Agile Principles

Business people and developers must work together daily throughout the project.

Agile Principles

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

Agile Principles

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

Agile Principles

Working software is the primary measure of progress.

Agile Principles

Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

Agile Principles

Continuous attention to technical excellence and good design enhances agility.

Agile Principles

Simplicity--the art of maximizing the amount of work not done--is essential.

Agile Principles

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

Agile Principles

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Agile in Practice

JIS uses a time boxed, iterative approach to software delivery that builds software incrementally from the start of the project.

Agile in Practice

Projects are broken down into little bits of user functionality called user stories (aka cards).

Agile in Practice

Work is prioritized and then continuously delivered in short two week cycles called iterations (aka sprints).

Agile in Practice

Teams may customize their processes to optimize how they work, but certain ceremonies and events are required.

Open Discussion