Agile Methodology

An overarching set of methodologies that implement an iterative approach to delivering a project throughout its life cycle. Click on each step to learn more!

Click here to learn about each step!

Plan

  1. Analyze concept and requirements

  2. Determine current state and expectations

  3. Arrange teams and tools
    • Break project into small manageable tasks
    • Set KPIs (key performance indicators)
  4. Choose a project management system (Notion, Trello, etc.) to keep track of everything

Design

Map user and stakeholders needs to product features, prototyping. Visualize your product and how it will function in the real world

Develop

Manufacturing, software development, i.e. fulfill steps needed to produce the “product”

Test

Ensure product functions as its intended, address any issues/concerns that may arise

  1. Plan, design, and development may change during this step

  2. Conduct interviews with potential users, internal testing (running through scenarios), etc.

Release

Present product to stakeholders and push it to the market, start tracking KPIs, collect feedback

Feedback

Reflect upon KPIs and feedback, repeat Agile cycle

Slideshow!

View the information on this page in a slideshow format! Useful for classrooms and all other group settings.

Learning Objectives

  • Understand the Agile Mindset: Describe the Agile values and principles and explain how they differ from traditional project management approaches.
  • Plan Iterations and Sprints: Understand how to plan and manage sprints, including defining sprint goals, estimating tasks, and setting realistic timelines.
  • Deliver Incremental Value to Customers: Understand the concept of delivering in increments, gathering customer feedback after each iteration, and using it to improve the product and plan future work.

Characteristics

  • Works best when a project doesn’t have clear constraints, timelines, or available resources
  • “Sprints”
    • Each phase follows a cycle, changing based on progress as well as user and stakeholder needs
    • Quick turnover
  • Feature by feature launch
  • Collective accountability
    • Everyone is responsible for the success of the initiative

Benefits

  • You can deploy to market quickly, which allows you to get feedback and responses in a short span
  • You waste fewer resources (including time) because you always work on up-to-date tasks
  • Short “sprints” allow you to detect and fix issues and defects faster
  • Well known.

Drawbacks

  • Short “sprints” do not leave time for documentation, which makes it difficult to avoid repeating past mistakes
  • Demands more man power
  • No clear end
  • Short cycles don’t leave enough time for the design thinking process

Example

How Can We utilize this approach?

Ensure product functions as its intended, address any issues/concerns that may arise

  1. Plan, design, and development may change during this step

  2. Conduct interviews with potential users, internal testing (running through scenarios), etc.