Agile methodology: an overview- By Agile Cockpit

Agile methodology definition:

A brief history of Agile software development

What is the Agile Manifesto?


  1. Individuals and interactions over processes and tools
  2. Working software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan


  1. Customer satisfaction through early and continuous software delivery
  2. Accommodate changing requirements throughout the development process
  3. Frequent delivery of working software
  4. Collaboration between the business stakeholders and developers throughout the project
  5. Support, trust, and motivate the people involved
  6. Enable face-to-face interactions
  7. Working software is the primary measure of progress
  8. Agile processes to support a consistent development pace
  9. Attention to technical detail and design enhances agility
  10. Simplicity
  11. Self-organizing teams encourage great architectures, requirements, and designs
  12. Regular reflections on how to become more effective

What is an Agile project management?

The deliverables

  1. Product vision statement: A summary that articulates the goals for the product.
  2. Product roadmap: The high-level view of the requirements needed to achieve the product vision.
  3. Product backlog: Ordered by priority, this is the full list of what is needed to be done to complete your project.
  4. Release plan: A timetable for the release of a working product.
  5. Sprint backlog: The user stories (requirements), goals, and tasks linked to the current sprint.
  6. Increment: The working product functionality that is presented to the stakeholders at the end of the sprint, and could potentially be given to the customer.

Agile Scrum methodology

Scrum team roles

  • Product owner: Product expert who represents the stakeholders, and is the voice of the customer.
  • Development team: Group of professionals who deliver the product (developers, programmers, designers).
  • Scrum master: Organized servant-leader who ensures the understanding and execution of Scrum is followed.

Scrum events

  • Sprint: Iterative time boxes where a goal is accomplished. The time frame does not exceed one calendar month and is consistent throughout the development process.
  • Sprint planning: Where the entire Scrum team gets together — at the beginning of every Sprint — to plan the upcoming sprint.
  • Daily Scrum: 15-minute time-boxed meeting held at the same time, every day of the Sprint, where the previous day’s achievements are discussed, as well as the expectations for the following one.
  • Sprint review: An informal meeting held at the end of every Sprint where the Scrum team present their Increment to the stakeholders and discuss feedback.
  • Sprint retrospective: A meeting where the Scrum team reflect on the proceedings of the previous Sprint and establish improvements for the next Sprint.

Scrum Artifacts

  • Product backlog: Managed by the Product Owner, it’s where all the requirements needed for a viable product are listed in order of priority. Includes features, functions, requirements, enhancements, and fixes that authorize any changes to be made to the product in future releases.
  • Sprint backlog: A list of the tasks and requirements that need to be accomplished during the next Sprint. Sometimes accompanied by a Scrum task board, which is used to visualize the progress of the tasks in the current Sprint, and any changes that are made in a ‘To Do, Doing, and Done’ format.


Its six general practices are:

  1. Visualization
  2. Limiting work in progress
  3. Flow management
  4. Making policies explicit
  5. Using feedback loops
  6. Collaborative or experimental evolution
  • Kanban board: A visual management tool used to visualize the development process. It can be either physical and can be used for personal productivity, as well as professional use.
  • Kanban cards: Cards that depict a work item/task in the work process. Used to communicate progress with your team, it represents information such as status, cycle time, and impending deadlines.
  • Kanban swimlanes: A visual element on the board that allows you to further distinguish tasks/items by categorizing them. Flowing horizontally, it offers distinction and provides a better overview of the workflow.




We help companies focus on becoming more Agile end to end. Review our website for more extra reports.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Seven Segment Search: Day 8: Advent of Code 2021 — Python Solution

Developing your Website Portfolio

Fixing (software) estimation issues using first principles

Building Spring Boot GraalVM Native Images

Strange Admin Panel Bypass Story | | Bug Bounty

AnyStake Protocol Upgrade

Bash Scripts —  Part 7 — Word Processing

I Send Myself the Best Messages: Self-Referential Associations

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store


We help companies focus on becoming more Agile end to end. Review our website for more extra reports.

More from Medium

An attempt at estimating a sprint’s Story Points capacity

Move Work Forward at speed

Role of a SAFe Scrum Master: Things to know.

The Whole Story: Technical Ticket Writing in Software Development