Agile Methodology

Manifesto

Agile involves short phases of collaborative, iterative work with frequent testing and regularly-implemented improvements. Some phases and tasks happen at the same time as others. In Agile projects, teams share responsibility for managing their own work. Scrum and Kanban are examples of Agile frameworks, which are specific development approaches based on the Agile philosophy.

AgileWaterfall
RequirementsFollow informal process to changes in requirements; frequent.Follow formal process to initiate requirement changes; infrequent
DocumentationUse more in-person communication than documentationUse many types of documentation
DeliverablesRelease deliverables in stagesRelease deliverable at end as a major event

Agile Manifesto - The 4 Values

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

Frameworks

Value-Driven Delivery

  • Principles
    • Build the right thing: Understand what the customers want.
    • Build the thing right: Ensure that the team only builds the requested or approved features.
    • Run it right: Though through how the user will interact with the product once it’s delivered.
  • Value roadmap
    • Product vision
    • Product roadmap
    • Release plans

Product Roadmap First Principles — Empower Scrum Teams, Align w/ Stakeholders | Scrum.org

Leading

  • See influence.
  • Coaching
  • Issues
    • Business collaboration issues
    • Value delivery issues
    • Team dynamics and culture
  • Coaching challenges
    • Managing a stable product roadmap
    • Incomplete implementation of Scrum
    • Lack of team stability

Agile Opportunities

  • DevOps
  • Business Agility, which helps the business thrive in high VUCA environment.

Scaling Agile

Positions