Category: Agile

WHAT IS the Difference Between Agile and Scrum in Project Management?

9/9/2021

Are you confused about the difference between Agile and Scrum in project management? Wrike created a short video that breaks down the key distinctions between these two approaches and provides insight into when and how to use them effectively.

Source: Wrike

Some key differences between the two include the timeline, team structure, and focus on customer input. The following table summarizes some of the key differences.

Characteristic	Agile	Scrum
Overview	Agile as a flexible, iterative approach to project management that is based on the values and principles outlined in the Agile Manifesto.	Scrum is a framework that helps teams implement the agile methodology and includes specific roles, events, and artifacts.
Scope	Agile is an umbrella term that covers a wide range of approaches.	Scrum is a more detailed and specific guideline for managing projects.
Feedback Loops	Agile offers constant feedback and updates.	Scrum uses short iterations called Sprints.
Management	Agile teams are cross-functional and led by a manager.	Scrum teams are self-organizing with specific roles such as the Product Owner and Scrum Master.

The choice between agile and Scrum depends on the team, organization, and project, and factors to consider may include the importance of client input, the need for speed, and the complexity of the project.

The Agile Manifesto

3/26/2021

Are you looking to understand the foundation of Scrum and agile project management? The Agile Manifesto is an influential document, first introduced in 2001, outlines the values and principles that form the basis of Scrum and other agile methodologies. Whether you're new to Scrum or an experienced practitioner, the Agile manifesto is an essential resource for understanding the foundations of agile software development.

Content of the Agile Manifesto

The 4 values of the Agile manifesto are:

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

The 12 principles of the Agile manifesto are:

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Business people and developers must work together daily throughout the project.
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Continuous attention to technical excellence and good design enhances agility.
Simplicity--the art of maximizing the amount of work not done--is essential.
The best architectures, requirements, and designs emerge from self-organizing teams.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

It was created by a group of software developers who were seeking a more effective and flexible approach to software development, and it has since become a widely-adopted framework for agile project management.

There are several potential reasons why it is important for developers to be familiar with the Agile manifesto:

The Agile manifesto is a widely-adopted framework for agile project management, and many organizations use it as a guide for their software development processes. Being familiar with the values and principles of the Agile manifesto can help developers understand how their organization approaches projects and how they can contribute to their success.
The Agile manifesto promotes a focus on delivering high-quality products and services to customers, and it encourages transparency, collaboration, and continuous improvement. Understanding these principles can help developers work more effectively with their team and contribute to a positive work culture.
The Agile manifesto has influenced the development of various agile methodologies, such as Scrum, Lean, and Extreme Programming. Familiarity with the Agile manifesto can provide a foundation for understanding these methodologies and how they might be applied in a software development context.
Many organizations value Scrum certification as a way to demonstrate knowledge and skills in agile project management. The Agile manifesto forms the basis of Scrum, so familiarity with the manifesto can be helpful for preparing for Scrum certification exams.

Visit the Agile Manifesto Website

Subway Map to Agile Practices

1/6/2021

It can be very confusing navigating the different terms and overlaps between difference methodologies and practices related to Agile. To help with that, Agile Alliance produced a "Subway Map" of Agile practices and terms (see screenshot below).

The subway map of agile practices (preview image)

This map shows the Agile practices and terms in context (including overlaps) in the following areas:

Extreme Programming
Teams
Lean
Scrum
Product Management
DevOps
Design
Testing
Fundamentals

Download PDF of Agile Subway Map

UPDATES

Sharing Scrum related Ideas, Resources, and Tools

WHAT IS the Difference Between Agile and Scrum in Project Management?

The Agile Manifesto

Subway Map to Agile Practices

Categories