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

Designing Habit Forming Mobile Application

Mobile Applications have become an integral part of our daily lives - we use mobile apps as alarm clocks to wake us up in the morning, to create to do lists when we start our day, to communicate with our colleagues at work via apps like Skype. We even check reviews of restaurants to visit on apps like Yelp and we seek entertainment on apps like Netflix and spotify. So what drives us to use these apps so seamlessly in our daily lives? Why we prefer some apps over others? Is there a science behind designing successful mobile apps like Facebook?   A study in US revealed that a user between the age of 18 and 44 visits the Facebook app on average 14 times a day [1]. This shows that using the Facebook app is a daily routine for many of its users. This makes Facebook a great example of a habit forming mobile app which is designed with human psychology in mind that encourages habit forming behavior in its users .   I recently attended a seminar on the design of such habit forming mo

Research around JIRA vs TFS

By: Carlos G.    An opportunity came from a colleague to discuss the case of company “X” for improving the ALM by introducing tools to this company. The challenge was to decide between Microsoft and Attlasian . He came to me because I’m a Microsoft kind of guy and he wanted the opinion from my perspective, not as a consultant, but as a friend of what he was trying to accomplish. He said that even though I was inclined to a technology I was able to explore other things and be “fair”. I agreed to be a part of his research because of 3 things: because of my curiosity I'm always willing to learn new techy stuff. Sometimes is good to be the dumbest one of the group. You learn so much! This was a story that I could blog about. (Of course no names are used in this post). My first impression was thinking “cool”; let’s compare Visual Studio TFS vs JIRA. Immediately I got a comment back with: “ Sure but JIRA by itself is more like an issue tracker in simple terms ”. That sa

AWS Amplify as low-code for infrastructure

Low-code development platforms are dominating many conversations lately. Many believe that low-code development platforms will account for millions of USD in revenue in the next five (5) years. An article by Forbes highlights that “ it will account for more than 65% of application development activity by 2024 ”. Some believe it will be the answer to all their development needs. Photo by Tima Miroshnichenko from Pexels  But low-code is not a new concept. The difference now is that its audience has amplified. For developers (or even advanced users) who have been in the Microsoft  ecosystem for a while have already experienced the assembly of software solutions with little effort using tools such as Microsoft Excel, Access, Visual Studio (assembling forms) and others. Putting Microsoft aside, and prior to this “low-code revolution” which has reached high altitude in the last couple of years, there have been many online veterans which allow a user to assemble simple to medium complex

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