Skip to main content

Introduction to Agile and Scrum


Agile has become a very popular development methodology in the software industry over the last decade. One of the key drivers behind the popularity of agile is it’s ability to enable teams to react quickly to changes in technology and customer needs. Unlike waterfall, one of the key principles of agile is to be open to changes in customer needs and subsequent changes in requirements as outlined by the Principles behind the Agile Manifesto. In this article I’ll discuss one of the popular agile frameworks called Scrum.


Scrum is a framework based on the agile principles that enables teams to address complex adaptive problems while productively and creatively delivering products of the highest possible value1.

At the core of the scrum framework is the organization of the Scrum team. A scrum team must consists of a Product Owner, the Development Team and a Scrum Master.


The Scrum Team develops a potentially releasable product increment at the end of a Sprint which is a time-boxed Scrum Event. A Sprint must be one month or less and must consist of the Sprint Planning, Daily Scrums, the development work, the Sprint Review and the Sprint Retrospective.


Now that we have understood the core principles of Scrum framework we can discuss how the framework lends itself to a development landscape with fast changing technology and customer needs. Given that a Sprint can only last for a month or less allows the Scrum Team to be more reactive to changes in technology and customer needs. For example, let’s assume that the client approaches the Product Owner with a new feature request at the end of the Sprint. The client thinks this new feature will provide a competitive advantage to his/her business and wants this feature to be developed as soon as possible. In this scenario a self-organizing Scrum Team is well positioned to meet this client's request given that the Product Owner has prioritized the request at the top of the Product Backlog. Unlike waterfall this is a very common practice in Scrum as the team only plans for a Sprint which last one month or less. In a waterfall approach the team has to assess the new feature request against the entire project deliverables, budget and timeline which can often take significant time.

Consequently Scrum is advisable to teams that need to react quickly to client requests. A self-organizing Scrum team working within an agile framework is best equipped to deliver solutions to meet client's changing needs in an effective and timely manner.

Reference:

Trending posts

Democratizing AI

Democratizing AI is all about empowering others to use it, by making it available to them. Audiences, such as marketers in a company, will be able to access AI capabilities as part of their MarTech solutions, without the need of being technical. It could also be schools, where the younger generations are learning how to use it in responsible, secure, innovative, and creative ways. This is the year where companies, after discovery phases and teams experimenting, are looking to activate and take advantage of the AI advances. Generated with Microsoft Designer   And so, questions emerge, such as “What to democratize when leveraging AI?” There are common scenarios, as well as specific ones, that will depend on the company, and the industry they belong to. A common scenario, seen in many industries, when democratizing data is the data visualization and reporting . In digital marketing, as an example, data scientists and data analysts can automate reporting, making them available to the c...

Productivity framework for 2024

Recently I was at a Christmas party and I found myself giving advice to a friend on being more productive. I shared the approaches that I take which helped me become more productive at work and in my personal life. The conversation with my friend inspired me to share my approaches in this blog .  Photo by Moose Photos from Pexels   My productivity framework has five key pillars and to remember them I use the mnemonic, POFOR = P lan your tasks, O rganize yourself, F ocus on your tasks, O ptimize yourself with habits and R eflect to ensure you are being productive on the right tasks. Plan Planning is very crucial as it sets the tone for the rest of the pillars. I always found I was more productive when I planned my tasks compared to when I didn’t, and hence planning has become my rule of thumb. I recommend taking 30 minutes at the end of each day to plan your next day. This means prioritizing your tasks and blocking your calendar accordingly. By not doing so, you are at risk o...

SRE, DevOps and ITOps

 If you are wondering what the differences between the SRE and DevOps are, as well as how these roles work with ITOps within an organisation then you are not alone; and best of all you are on the right blog post. Often enough business units in a company get confused, assigning the ServiceNow or Jira tickets or any other ticketing system of your preference, to the wrong group, and even having the incorrect expectations when doing resourcing. Let us go through definitions, insights and scenarios that will help you understand the difference. DevOps software development operations - AI Generated When it comes to DevOps and SRE, then you might be wondering which practice came first. While SRE may have originated a bit earlier, internally at Google, DevOps came first publicly as a practice and started to be used by companies. A few years later was when Google decided to open SRE to the world after the publication of the "Site Reliability Engineering" book. Therefore, technically sp...

Small Language Models

 Open source models will continue to grow in popularity. Small Language Models (SLMs) are smaller, faster to train with less compute.  They can be used for tackling specific cases while being at a lower cost.  Photo by Tobias Bjørkli via Pexels  SLMs can be more efficient SLMs are faster in inference speed, and they also require less memory and storage.    SLMs and cost Small Language models can run on less powerful machines, making them more affordable. This could be ideal for experimentation, startups and/or small size companies. Here is a short list Tiny Llama. The 1.1B parameters AI Model, trained on 3T Tokens. Microsoft’s Phi-2. The 2.7B parameters, trained on 1.4T tokens. Gemini Nano.  The 6B parameters. Deepseek Coder

This blog uses cookies to improve your browsing experience. Simple analytics might be in place for pageviews purposes. They are harmless and never personally identify you.

Agreed