The Agile Fundamentals for Scrum Masters

Thinking of becoming a Scrum Master? Or are you already one, but you’re still new to the job? No matter what level of experience you have with being a Scrum Master, it’s always great to get your bases covered! Let’s discuss some of the fundamentals of Agile: what it is, and what it isn’t:

What is Agile?

More than a project management approach or a software development methodology, it’s best to think of Agile as a mindset. It’s a discipline, a set of values that focuses on the people, the process, and the product. Agile is a philosophy made up of different values, principles, and methodologies.

A Brief History of Agile

When enterprises began to use PC computing more heavily during the early 1990’s, industry experts observed that an average software development project takes about three years for to cycle from validating the business needs to finishing the actual application. But many things can happen in a year alone – needs can be reprioritized, new technological trends can come in, and sometimes, businesses themselves can change.

By then, there were many different software methodologies being developed here and there. One of them is the famous Scrum Process by Jeff Sutherland and Ken Schwaber, presented in 1995 during an object-oriented conference. Kent Beck has also come up with extreme programming (XP), a methodology for various software development best practices that aim to rapidly deliver high-quality software to customers.

59 Seconds Agile - The Agile Fundamentals

59 Seconds Agile – The Agile Fundamentals

A Brief History of Agile

On February 11-13, 2001 at Snowbird in the Wasatch mountains of Utah, seventeen people representing XP, Scrum, DSDM, Crystal, Feature-Driven Development, and others looking for alternatives to heavyweight software development decided to meet up. Thanks to this special meeting, the many efforts of developing these iterative and incremental software development techniques were unified. Together, they came up with what is known today as the Agile “Software Development” Manifesto.

The Agile Manifesto

The Agile Manifesto is written as follows:
“We are uncovering better ways of developing software by doing it and helping others do it. Through this work, we have come to value:”

1. Individuals and interactions over processes and tools.
2. Working software over comprehensive documentation.
3. Customer collaboration over contract negotiation.
4. Responding to change over following a plan.

It is important to note the following statement: “That is, while there is a value in the items on the right we value the items on the left more.” This does not mean that documentation, contracts, plans, and processes should be done away completely – in fact, these are still needed. What the Agile Manifesto wants to say is that teams should simply put more importance on the people, the product, the collaboration, and the resilience to changes, if needed.

Prev <— Continue Reading —> Next

Our Favourite Agile Books

Read Our Reviews

The History of Agile For Scrum Masters

Prior to the 1990’s software development was very slow, often taking years to complete development and release the product to market. The industry was following a very formal methodology for products and software development…

Read More

What is Agile to the Scrum Master?

While traditional project management is still widely used, the benefits of an Agile approach to running a project are becoming more and more recognized. Where Agile has a distinct advantage over classic project management is the development of new products…

Read More

Why Use Agile as a Scrum Master?

When determining if a move to Agile is right, a PESTLE can be used to simplify what factors should be considered. While Agile is sometimes thought of as a software development project management method, it isn’t just for these types of technology-centric companies…

Read More

The Agile Manifesto For Scrum Masters

Agile is a quick, simple, lightweight and effective way of managing projects. In traditional project management models…

Read More

The Agile Principles For Scrum Masters

When the Agile Manifesto was drawn up in 2001, it embodied four values and twelve principles that signaled a new approach to…

Read More

The Agile Fundamentals For Scrum Masters

Thinking of becoming a Scrum Master? Or are you already one, but you’re still new to the job? No matter what level of experience…

Read More

The Declaration of Interdependence For Scrum Masters

The Declaration of Interdependence establishes that all members, stakeholders, and customers are interdependent and…

Read More

The Agile Frameworks For Scrum Masters

There are many different Agile frameworks – all of them share the same philosophy and are built around the Agile Manifesto and Principles. But they vastly differ in their approaches, values, and structure. …

Read More

The Scrum Framework For Scrum Masters

The Agile Scrum framework is designed to deliver products and projects of any size. This includes projects, programs, and portfolios. Scrum provides guidelines on delivery techniques, events, and roles. Many of the same ceremonies are held within both a standard Agile scrum project and an Agile Scrum…

Read More

The Scrum Roles For Scrum Masters

Scrum is a useful tool for the creation, maintenance, plan, and execution of diverse products and services. The tool consists of…

Read More

The Scrum Team Size For Scrum Masters

The basics of Scrum can be easy but implementing them and succeeding with Scrum can be infinitely harder. Scrum …

Read More

The Agile Project Vision For Scrum Masters

At the heart of any great product is a great vision. It describes the primary goal or goals of a product and creates a focus that…

Read More

Forming the Scrum Team For Scrum Masters

Scrum is a framework that encourages delivery of potentially shippable product increments every 2-6 weeks. The work is…

Read More

Developing Epics For Scrum Masters

The term ‘epic’ in agile refers to a large user story that has not yet been defined in detail. Typically, an epic will cover a single…

Read More

The Agile Product Backlog For Scrum Masters

A Product Backlog is an organized collection of the existing User Stories (aka Wants and Needs) for an explicit business endeavor. Think of a shopping catalog of User Stories, ordered by urgency, that can be perused and selected from to determine what will be worked on during the current…

Read More

Release Planning For Scrum Masters

Although flexibility and adaptability are part and parcel of an agile methodology, this does not mean that no planning is required when…

Read More

Creating User Stories For Scrum Masters

User Stories are an integral part of the agile development process. They are an important agile technique that is used to frame…

Read More

Estimating User Stories For Scrum Masters

One of the principles of self-managing teams in Agile Scrum is working collaboratively with the Product Owner to effectively deliver…

Read More

Creating Tasks For Scrum Masters

According to The Agile Manifesto: “The best architectures, requirements, and designs emerge from self-organizing teams.” As a…

Read More

Estimating Agile Tasks For Scrum Masters

In Scrum, a list of user stories is produced and put together to form a product backlog, and each of these user stories will need to…

Read More

Creating the Sprint Backlog For Scrum Masters

The Sprint Backlog is defined as a group of user stories that are grouped together during the Sprint Planning Meeting.  This…

Read More

Creating the Deliverables For Scrum Masters

Agile Scrum provides the framework for delivery of the vision of an organization. Execution of the vision includes processes, ceremonies and project deliverables that are also known as artifacts…

Read More

The Daily Stand-Up For Scrum Masters

The daily scrum is an opportunity for developers or anyone committed to working in the sprint to talk to each other to make sure the…

Read More

Product Backlog Prioritisation For Scrum Masters

The product backlog is a key element of Agile software development. It facilitates a development environment that creates valuable features and products for stakeholders…

Read More

The Sprint Review Meeting For Scrum Masters

The Sprint Review meeting comes at the end of the sprint and the goal of this meeting is to have key people in the room to be able …

Read More

Demonstrating and Validating the Sprint For Scrum Masters

As organizations migrate to Agile principles, there may be questions about how the organization can prove that there is value…

Read More

The Sprint Retrospective For Scrum Masters

A very simple step by step guide to help you choose the appropriate product development methodology from…

Read More

Releasing the Product For Scrum Masters

One of the most important milestones any project will ever have is finally releasing their product and putting it out there. It’s the…

Read More

Regression Testing For Scrum Masters

In companies using agile development, it is common to introduce changes in a product incrementally. Along with the new changes, unexpected issues may arise, testing whether the existing functionality is broken or not becomes very important…

Read More

Product Owners

Find out more about the Agile and the Product Owner Role

Read More

Developers

Find out more about the Agile and the Developer Role

Read More

More Articles

Read More

Chicken Appreciation Society

Share
Translate »