top of page

Agile Methodologies

Agile Methodologies

Agile methodologies include

Dynamic System Development Methodology

· Scrum

· Extreme Programming

· Test-driven Development

· Lean

· Kanban

Scrum Definition

Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.

1. A Product Owner orders the work for a complex problem into a Product Backlog.

2. The Scrum Team turns a selection of the work into an Increment of value during a Sprint.

3. The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint.

Scrum process Framework

Scrum Team

The fundamental unit of Scrum is a small team of people, a Scrum Team. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal, Product Backlog, and Product Owner. The Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required. They are structured and empowered by the organization to manage their own work. Working in Sprints at a sustainable pace improves the Scrum Team’s focus and consistency. The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint. Scrum defines three specific accountabilities within the Scrum Team: the Developers, the Product Owner, and the Scrum Master


Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint. The specific skills needed by the Developers are often broad and will vary with the domain of work. However, the Developers are always accountable for:

● creating a plan for the Sprint, the Sprint Backlog

● quality

● adapting their plan each day toward the Sprint Goal

● holding each other accountable as professionals.

Product Owner

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. How this is done may vary widely across organizations, Scrum Teams, and individuals

The Product Owner is also accountable for effective Product Backlog management, which includes:

● developing and explicitly communicating the Product Goal

● Creating and clearly communicating Product Backlog items

● Ordering Product Backlog items

● ensuring that the Product Backlog is transparent, visible and understood.

The Product Owner may do the above work or may delegate the responsibility to others. Regardless, the Product Owner remains accountable. For Product Owners to succeed, the entire organization must respect their decisions. These decisions are visible in the content and ordering of the Product Backlog, and through the inspectable Increment at the Sprint Review. The Product Owner is one person, not a committee. The Product Owner may represent the needs of many stakeholders in the Product Backlog. Those wanting to change the Product Backlog can do so by trying to convince the Product Owner.

Scrum Master

Scrum master helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Scrum Master is accountable for the Scrum Team’s effectiveness. They do this by enabling the Scrum Team to improve its practices, within the Scrum framework.

The Scrum Master serves the Scrum Team in several ways, including:

● coaching the team members in self-management and cross-functionality

● helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done

● causing the removal of impediments to the Scrum Team’s progress

● ensuring that all Scrum events take place and are positive, productive, and kept within the time box. The Scrum Master serves the Product Owner in several ways, including:

Helping find techniques for effective Product Goal definition

Product Backlog management

● Helping the Scrum Team understand the need for clear and concise Product Backlog items

● Helping establish empirical product planning for a complex environment

● Facilitating stakeholder collaboration as requested or needed. The Scrum Master serves the organization in several ways,

● Leading, training, and coaching the organization in its Scrum adoption

● Planning and advising Scrum implementations within the organization

● Helping employees and stakeholders understand and enact an empirical approach for complex work

● Removing barriers between stakeholders and Scrum Teams.

Scrum Events

48 views0 comments

Recent Posts

See All


Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page