Skip to main content

Introduction to Agile and Scrum

[PLACEHOLDER]

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:
Anonymous

Trending posts

Apple's App Tracking Transparency sealing Meta's fate

Anonymous
If you have been following the recent news on Meta (formerly Facebook) you may have read that Meta recently projected their ad revenue will be cut by a staggering $10 billion in 2022 due to Apple’s new App Tracking Transparency feature (also known as ATT). This has resulted in Meta’s stock to plummet by over 20%. Photo by julien Tromeur on Unsplash - modified by Beolle So what is Apple’s ATT and how does it impact ad revenue? Apple has been releasing multiple privacy features for the last few years. This included Apple’s Mail Privacy Protection and Apple’s App Tracking Transparency feature. You can learn more about Apple’s Mail Privacy Protection in our earlier post by clicking here .  Apple’s App Tracking Transparency (ATT) was launched in iOS 14.5 and iPadOS 14.5 where it prompted users to select if they wanted the app to track their activities across other apps on the device. The prompt is displayed when the user opens an app like Facebook or Instagram for the first time o...
Read more

Goal setting frameworks for Product Management - OKR and HOSKR

Anonymous
As a business analyst and product manager we often use various frameworks to synthesize and organize our product ideas and goals. I think of frameworks as tools in our product management tool kit which we use depending on the task at hand.  And speaking of goals, OKR is a very popular framework that I often use to set the goals for the products I am managing. However recently I participated the #ProductCon conference hosted by Product School  and I stumbled upon one of the talks in which Rapha Cohen, the CPO at Google Waze introduced a more effective framework for setting product goals. The framework is called HOSKR.  In this post I'll describe both the OKR and HOSKR frameworks in more details using examples. I hope this will provide you, our readers, more practical insights on how to effectively use these frameworks to set your product goals.  OKR OKR stands for O bjectives and K ey R esults. If you are reading this post then you are on our Beolle blog and I am goi...
Read more

Digital Sovereignty in a Polarised World - Data, Cloud Power, and the Search for Trusted Alternatives

 Relationships have deteriorated, with trust diminished to an extent that may preclude restoration. The world, once structured to favour certain regions, has undergone significant shifts; for numerous countries, such advantages never existed. In this polarised reality, stakeholders are re-evaluating alliances, as former partners now often embody the role of "frenemy," thereby threatening freedom. This phenomenon is longstanding, rooted in historical power dynamics. When politics and influence supersede principles of fairness, respect, and integrity, ethical boundaries become blurred. Previously, issues that did not directly affect you would get overlooked out of principle, but current risks necessitate action to safeguard sovereignty. Information has consistently served as a key strategic asset, a trend only intensified by technological advancements that have elevated data as the principal factor. In other words, technology has amplified that, and data is the name of the game...
Read more

Assembling MLOps practice - part 2

 Part I of this series, published in May, discussed the definition of MLOps and outlined the requirements for implementing this practice within an organisation. It also addressed some of the roles necessary within the team to support MLOps. Lego Alike data assembly - Generated with Gemini   This time, we move forward by exploring part of the technical stack that could be an option for implementing MLOps.  Before proceeding, below is a CTA to the first part of the article for reference. Assembling an MLOps Practice - Part 1 ML components are key parts of the ecosystem, supporting the solutions provided to clients. As a result, DevOps and MLOps have become part of the "secret sauce" for success... Take me there Components of your MLOps stack. The MLOps stack optimises the machine learning life-cycle by fostering collaboration across teams, delivering continuous integration and depl...
Read more

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