Organisational culture encompasses the shared values, beliefs, and practices that define how individuals within an organization interact and work together. It reflects the company’s identity, influences decision-making, and shapes employee behaviour.
Discover five effective strategies to build consensus and foster collaboration within your team or organization.
Discover the power of transformational leadership and how it can inspire positive change within organizations.
Uncover the intricacies of the Scrum process and learn how this agile framework can revolutionize project management.
Discover the power of a product vision and how it shapes the future of a business.
Discover the essential principles and strategies of change management in this insightful article.
Discover the significance of a product goal and how it drives the direction and focus of a project.
Discover the debate of whether a Product Owner can effectively take on the role of Scrum Master.
Explore the concept of evidence-based management and discover how this approach leverages data and research to make informed business decisions.
Discover the power of self-organizing teams and how they can revolutionize your organization.
Discover the key principles and strategies behind agile leadership in this insightful article.
Discover the key principles and benefits of agile project management in this comprehensive guide.
Discover the key principles and strategies behind agile transformation in this insightful article.
Discover the ins and outs of leadership development in this insightful article.
Discover the importance of setting a sprint goal in agile project management.
Discover the ins and outs of a Kanban card with our comprehensive guide.
Discover the key differences between an Agile Coach and a Scrum Master in this insightful article.
Discover the ins and outs of the elusive “spike” in Scrum methodology.
Discover the ins and outs of iterations in Agile methodology with our comprehensive guide.
Discover the power of cross-functional teams and how they can revolutionize your organization.
Discover the key principles and strategies behind Agile Transformation in this comprehensive article.
Learn all about timeboxing in Scrum with our comprehensive guide.
Discover how feedback loops in Scrum can drive continuous improvement and enhance team collaboration.
Uncover the transformative power of Kanban Flight Levels in this comprehensive article.
Learn how to identify and overcome impediments in Scrum with our comprehensive guide.
Discover the key principles and strategies behind an agile organization in this insightful article.
Discover the secrets to creating a teal organisation and achieving a self-managed workplace.
By embracing Lean Thinking as a foundational pillar of their Agile practices, organizations can pave the way for sustained growth, innovation, and customer-centricity.
In this blog post, we will explore the top five scrum tools that can help you achieve your goals.
In this post, we delve into the renowned Tuckman Model, a comprehensive and insightful framework that illuminates the stages of team development
In this in depth resource you will learn more about how agile transformation leads to Increased flexibility in finance
Today, we’ll unveil the best books on Scrum that you shouldn’t miss, aiming to help you sharpen your Scrum skills and methodologies
The Scrum Guide is the official Scrum Body of Knowledge. It was written by Ken Schwaber and Jeff Sutherland, co-creators of Scrum.
The Scrum values serve as guiding principles that not only shape the culture within teams but also drive the success of product development.
The Agile Release Train incorporates people needed to implement, test, deploy and release the product.
What is the perfect Scrum team size? Let’s dive deep into the Agile and Scrum frameworks to determine the magic number.
This insightful guide will shed light on SAFe’s structure, core values, principles, and potential impact on your organisation.
Scrum Estimation is a team-driven approach with the purpose of forecasting the effort needed to complete each user story.
In Scrum, the acceptance criteria refer to a set of conditions or requirements that a user story must meet to be considered complete or acceptable.
The Scrum Team is made up of three key roles which include the Scrum Master, the Product Owner and the Developers.
Popularized by Mike Cohn, Planning Poker is a facilitation technique for estimation.
In this article, we will explore Agile vs. Scrum and the key similarities and differences.
We’ll take a closer look at the role of the Product Owner and the benefits they have to the team and organisation. If you are interested in becoming certified in this field, we also have a course made just for you. Let’s get started.
We will explore the benefits of using Kanban Boards, the key elements, and what they look like in practice, to get you started with this useful Agile project management tool.
Velocity in Scrum is a measure of the amount of work a team can complete in a sprint usually measured in story points.
Story points are typically expressed as a numerical value, with each value representing a different level of effort and complexity.
The fundamental differences between the two are relating to their core philosophies. Learn everything you need to know right here.
Confused which is better Scrum and Kanban? It’s a flawed question. Or at least, a question based on a flawed premise.
When talking about Kanban, there are actually three definitions which cause confusion.
The Definition of Done (DoD) is when an item meets a collection of criteria for it to be considered complete, or “done”.
Dual Track is an Agile product development methodology that sees cross-functional product teams divide their daily activities into two tracks.
Capacity represents the amount of work that can be completed within a given time based on the number of hours a team has available.
The purpose of a User Story is to explain how some functionality will provide value to a certain type customer.
We will take a closer look at the three pillars, how they work together and why they are essential in the successful adoption of Scrum.
In this article, we’ll take a look in more detail at exactly what the Product Owner and Scrum Master do and break down the key differences of each during the Scrum process.
In this article, we’ll take a look in more detail at exactly what the Product Owner and Scrum Master do and break down the key differences.
Before we dive straight into Agile Values and Principles, it’s first important to understand Agile.
Agile is an umbrella term which encompasses many frameworks and approaches to delivering value in a complex environment. Learn more.
Sprint Retrospective is a time for Scrum Teams to reflect on everything that happend in the Sprint and identify opportunities to improve.
Daily Scrum is a meeting held daily to give the team a chance to review goals and identify any potential concerns or roadblocks. As described in the Scrum Guide, its
An Epic is a large chunk of work which is too much for a single Sprint and then can be divided into smaller chucks of work.
The Scrum Sprint is a short, time-boxed period where a Scrum Team works to complete an agreed amount of features.
We’ll take a look at Product Increment in more detail, who is responsible, and what it means for teams. Then, we’ll also explore the Definition of Done, and how this is a crucial part of the Increment.
We’ll take a look at both Sprint Burndown Charts and Release Burndown Charts and how they can be utilised in Scrum.
Meetings in Scrum are an opportunity for teams, management and stakeholders to align.
The Scrum Guide defines it as the act of breaking down and further defining Product Backlog items into smaller more precise items.
Agile methodology is a way of helping teams self-organize so they can develop products quickly and efficiently while still meeting users needs and client budgets.
Sprint Planning is the first event of the Sprint in which the Scrum Team makes a plan what they want to accomplish in the Sprint.
Scrum Artifacts are critical for the success of any Scrum Team and defines all the work that needs to be done in a project.
A Scrum Board is a visual representation of the work that needs to be completed within a single Sprint. It is sometimes also referred to as a Sprint Board or Kanban Board.
The Scrum Team is made up of three accountabilities which include the Scrum Master, the Product Owner and the Developers.
You can think of Scrum Events as the key meetings in product development.
The Product Backlog in Scrum is a prioritised list of what is needed to improve or develop a product or service.
Scrum is a framework where people can address complicated and adaptive problems, while delivering products of highest possible value.
A sprint review is a meeting held at the end of each sprint to review the work that has been completed and to gather feedback from stakeholders.
In this article, we will take a closer look at exactly what a Scrum Master does, their key responsibilities and why this is so important in Scrum. We also have information on how to become a Scrum Master, so if you are short on time, skip to the bottom to find out more.
Let's Talk About
How We Can Help!
Are you enjoying our articles? Even better you can talk to us in person! Get in touch with us so we can schedule something!