OpenWest 2014/Agile

by Hala Saleh, Dir. Product Management, Rentlr

Agile Manifesto - http://agilemanifesto.org

• 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 Principles principles

• Collaboration
• Continuous feedback and improvements
• Self-organizing teams
• Simplicity
• Retrospectives
• Frequent and Continuous delivery
• Inspect-adapt cycle
• Sustainable pace
• Timeboxing

Agile development - iterative and incremental approach to developing software that incorporates continuous feedback loops, adaptability and collaboration

But agile is not only for software

Ready to work?

• Step 1: Identify the Problem
• Step 2: Is Agile the Answer? Is your culture compatible? Start with processes and implement incremental changes.
  • book "Becoming Agile in an Imperfect World" by Smith and Sidky

Conclusion:

• Agile can't make you a better executive (it is not a silver bullet)
• Learn it, Live it, Do it
• Learn from others
• Cultivate a tolerance for Failing Fast

---

   Agile Principle 1: Satisfy the Customer
   Agile Principle 2: Embrace Change
   Agile Principle 3: Frequent Delivery
   Agile Principle 4: Cross-Functional Collaboration
   Agile Principle 5: Support and Trust
   Agile Principle 6: Face-to-Face Conversation
   Agile Principle 7: Working Software
   Agile Principle 8: Sustainable Pace
   Agile Principle 9: Technical Excellence
   Agile Principle 10: Keep it Simple
   Agile Principle 11: Self-Organization
   Agile Principle 12: Inspect and Adapt

---

Principles behind the Agile Manifesto
http://agilemanifesto.org/principles.html

We follow these principles:

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

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

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

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

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

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

Working software is the primary measure of progress.

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

Continuous attention to technical excellence
and good design enhances agility.

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

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

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