If you haven’t been living under a rock, it’s likely you’ll already be familiar with Agile methodology to some degree.
If you are, you’ll probably have heard of Scrum. No? Never mind, I’ve added a little description for any hermit crabs below.
So, what is Agile methodology?
Agile methodology, or Agile project management as it’s otherwise known, is all about being open to feedback. It’s having the capacity to change work priorities with developments as they come in. A simpler way of describing it would be that it’s basically the opposite of more linear-based methodologies, such as waterfall project management, because it works to free-up the time of teams and developers from the constraints that often come with more traditional methodologies. Scrum is a popular application of the agile framework, and is reliant on team collaboration and knowledge.
The ideal format for project scope and workflow, providing structure and by-the-book rules to the agile concept. Scrums are built to improve product progress, productivity and efficiency of teams, on an ongoing basis.
Scrums are split into “sprints”, and sprints are where a select number of tasks are assigned within a specific period of time, (usually a couple of weeks), with the expectation that tasks will be complete by the end of a sprint. There are no gaps between sprints, for instance, sprint 2 will come straight after sprint 1 and so on, until the end product is complete.
For you visual learners, I’ve included a table which breaks down the two.
As Scrum is an implementation of Agile practises, it’s worth noting that Scrum is a framework to help you achieve Agile. The points highlighted in the above table, therefore apply to one another.