Scribd
Upload
114 views3 pages

Agile Methodology

The document discusses several Agile methodologies including Scrum, Kanban, and Extreme Programming. It provides details on Agile values, Scrum framework, roles and artifacts, events, and how Scrum and Kanban processes differ. Scrum uses fixed length sprints, backlogs, and rituals while Kanban uses continuous flow and limits work in progress to maintain flow. Both aim to deliver working solutions frequently through collaboration and adapting to changes.

Uploaded by

Joseph Sta Maria Meneses
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
114 views3 pages

Agile Methodology

The document discusses several Agile methodologies including Scrum, Kanban, and Extreme Programming. It provides details on Agile values, Scrum framework, roles and artifacts, events, and how Scrum and Kanban processes differ. Scrum uses fixed length sprints, backlogs, and rituals while Kanban uses continuous flow and limits work in progress to maintain flow. Both aim to deliver working solutions frequently through collaboration and adapting to changes.

Uploaded by

Joseph Sta Maria Meneses
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Agile Methodology :

The benefits of Agile are tied directly to its faster, lighter, more engaged mindset. The process, in a
nutshell, delivers what the customer wants, when the customer wants it. There’s much less wasted time
spent developing in the wrong direction, and the entire system is quicker to respond to changes

Method 1 - Agile Values and Principles

Method 2 – Scrum - is a framework for developing and sustaining complex products

Method 3 - Kanban

Method 4 - Extreme Programming

Agile Values ,

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)

Scrum Definition
Scrum is a lightweight framework that helps people, teams and organizations generate value
through adaptive solutions for complex problems.
In a nutshell, Scrum requires a Scrum Master to foster an environment where:
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.
4. Repeat

Scrum Theory:
1. Transparency - Transparency enables inspection. Inspection without transparency is
misleading and wasteful.
2. Inspection - Inspection enables adaptation. Inspection without adaptation is considered
pointless. Scrum events are designed to provoke change.
3. Adaptation - Adaptation becomes more difficult when the people involved are not
empowered or self-managing. A Scrum Team is expected to adapt the moment it learns
anything new through inspection.

Scrum Values
Commitment, Focus, Openness, Respect, and Courage

Scrum Team
Developers, Product Owner and Scrum Master

Scrum Events
1. The Sprint – most commonly 2weeks in the durations
2. Sprint Planning
3. Daily Scrum
4. Sprint Review
5. Sprint Retrospective

Scrum Artifacts
1. Product Backlog
2. Sprint Backlog
3. Increment

The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do
this by 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.
Scrum Masters are true leaders who serve the Scrum Team and the larger organization.
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; and,
 Ensuring that all Scrum events take place and are positive, productive, and kept within the
timebox.
The Scrum Master serves the Product Owner in several ways, including:
 Helping find techniques for effective Product Goal definition and 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; and,
 Facilitating stakeholder collaboration as requested or needed.
The Scrum Master serves the organization in several ways, including:
 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; and,
 Removing barriers between stakeholders and Scrum Teams.

SCRUM – SCRUM MASTER


KANBAN – AGILE COACH

SCRUM Flow:
Product Backlog (Pull) - Sprint Backlog ( by using Scrum Board- TO DO – BUILD - TEST – DONE )
with daily meeting max 15mins - at the end the sprint the work complete package to RELEASE any
incomplete will go back to the product backlog , SPRINT end in 2 rituals the Sprint review (the
demonstration of the new functionality to the stakeholders) and Sprint Retrospective ( what went
well, what went to improve ) the aim of the retrospective is that the next sprint is more efficient and
effective from the last sprint

KANBAN – there’s no 2 weeks sprints, its continuous process and no sprint backlog. It’s board has
a working progress limit related into teams capacity.

KANBAN BOARD - visual assurance for what you have done per day
KANBAN CARDS per user stories
BACKLOG – TODAY – DOING – DONE

You might also like