Agile Vs Scrum

By Ranjana Kaushik – Delivery Lead

Agile vs scrum

As a delivery lead, its sometimes difficult to explain to teams and clients which methodology we use, Agile or Scrum.

Both have many similarities, meaning it is not always easy to clearly distinguish. Both focus on delivering software, work on iterative processes and accommodating changes, and encourage transparency and continued improvements.

Scrum comes under agile or in other words scrum is one way to implement agile, it is a methodology to implement agile philosophy to manage the project.

Under the Agile umbrella there are several different methodologies, these are Scrum, Kanban, XP (Extreme programming), Crystal, Dynamic Systems Development Method (DSDM) amongst others.

At Crimson Macaw

At Crimson, we use Kanban and Scrum methodologies to implement Agile ways of working. Scrum is the most used methodology at Crimson Macaw.

To better understand the differences between Agile and Scrum, I have listed the following comparisons:


  • Agile is not Scrum.
  • Agile is a project management philosophy that utilises a core set of values or principles.
  • In Agile, everything is delivered at the end of the project.
  • Agile involves members from various cross-functional teams.
  • Agile describes a set of principles in the Agile Manifesto for building software through iterative development.
  • If Agile works for the project, you need to choose which agile framework to use.
  • Use Agile if:
    • The final product is not clearly defined
    • The clients/stakeholders need to be able to change the scope
    • Changes need to be implemented during the entire process
    • The developers are adaptable and can think independently
    • Need to optimise for rapid deployment
  • Agile follows iterative approaches.  Continuous involvement of the client is needed to ensure that expectations are aligned and to allow the team and project to adapt to changes throughout the process.
  • In Agile Methodology, we need to have regular interactions with the client and/or end-users. We need to seek feedback for better understanding of the scope of the project and take an iterative approach to delivering the scope of work.


  • Scrum is Agile.
  • Scrum is a type of Agile Methodology that is used to facilitate a project.
  • Scrum is broken down into shorter sprints and smaller deliverables.
  • A Scrum project team includes specific roles, such as the Scrum Master, Product Owner, and Scrum Team.
  • Scrum is a specific set of rules to follow when practicing Agile software development.
  • Use Scrum when
    • The project requirements will change and evolve
    • Continuous feedback is required
    • When need to figure out how to do a large part of the work because it has not been done before
    • It does not need to commit to a fixed release date
    • The project team wants autonomy
    • Need to deliver software on a regular basis
  • In Scrum Methodology, project work is done in Sprints. During sprint planning, the project team identifies a small part of the scope to be completed during the upcoming sprint, which is usually a two-to-four-week period.
  • In Scrum, at the end of the sprint, the work is ready to deliver to the client, and is followed by a sprint review and retrospective. This cycle is repeated throughout the project lifecycle until the entire scope has been delivered.


Hopefully, that helps with your understanding of the differences between Agile and Scrum.

Want to know more about how we use Agile Methodologies here at Crimson Macaw? Check out our blogs on all things Agile here.

Want to know more about how we can help you? Get in touch here.