Agile Methodology

Presented to:
Eng. Ebtesam Hussain
Team Members

1. Adham Salah El-Din Basheir

2. Salma Yasser Sayed

3. Mohamed Eid Mohamed

4. Mostafa Mohamed Anwar

 Agenda

1 2 3 4
Intro to waterfall Intro to Agile Lean Agile Scrum
model model

5 6 7 8
Kanban Kanban vs Scrum Scrumban Jira
Demo
Waterfall
model
Agile Values

Individuals and Working Software

Interactions over
over Comprehensive
Processes and Tools Documentation

Customer Collaboration Responding to Change

over over
Contract Negotiation Following a Plan
Agile Principles

Individuals and Working Customer Responding to

interactions software collaboration change
• Customer • Working Software is • Collaboration • Welcome
Satisfaction through the Primary Measure between Business Changing
Early and of Progress Stakeholders and Requirements,
Continuous Delivery Developers
Even Late in
• Maintain a Development
• Build Projects Sustainable Pace of • Simplicity—the Art
around Motivated Work of Maximizing the
Individuals Amount of Work Not • Deliver Working
• Continuous Done Software
• Face-to-face Attention to Frequently, with a
communication is Technical Excellence • Regular Reflection preference to the
the Most Effective and Good design on Team shorter timescale
Effectiveness
• Self-Organizing
Teams
What is Lean Agile ?

• It is a transformative approach that combines the

principles of Lean methodology with Agile practices.

• Its goal is to enhance efficiency and deliver value to

customers.
 Lean Agile Principles

Maximizing Value Minimizing Waste Continuous Efficient Delivery

Improvement
 Scrum

CONTINUOUS ADAPTABILITY REPRIORITIZATION SHORT

LEARNING RELEASE
CYCLES
Scrum Terminology

People Artifacts Key Concepts Rituals

Product Owner User Stories Done Backlog Grooming
Stakeholder Product Backlog Story Points Sprint
Development Team Sprint Backlog Velocity Sprint Planning
Scrum Master Charts Sprint Backlog
Refinement
Sprint Review
Sprint Retrospective
Daily scrum
Sprint
Velocity Chart
Burndown
Kanban

Kanban is an agile framework that

focuses on visualizing workflow,
Kan + Ban limiting work in progress (WIP),
看 板 and enabling continuous
improvement. It's often described
signboard as a "pull" system, where work is
pulled through the process as it
becomes available.
Key Principles of Kanban

Visualize Workflow:
Make your workflow visible to everyone involved. This helps
to identify bottlenecks and areas for improvement.

Limit Work in Progress (WIP):

Restrict the number of tasks being worked on at any given
time to prevent overwork and improve efficiency.

Continuous Improvement:
Constantly analyze the workflow and identify ways to improve
processes, reduce waste, and increase productivity.
 Kanban Methodology Example

Story Backlog To Do Implementation Testing Deploy Done

2 2 1 1
ongoing waiting ongoing waiting
A B

C D

E F

G H

Product owner
 Kanban Methodology Example

Story Backlog To Do Implementation Testing Deploy Done

2 2 1 1
A B ongoing waiting ongoing waiting

C D

E F

G H

Product owner
 Kanban Methodology Example

Story Backlog To Do Implementation Testing Deploy Done

2 2 1 1
ongoing waiting ongoing waiting

C D A

E F
B
G H

Product owner
 Kanban Methodology Example

Story Backlog To Do Implementation Testing Deploy Done

2 2 1 1
ongoing waiting ongoing waiting
I C
D A

E F
B
G H

Product owner
 Kanban Methodology Example

Story Backlog To Do Implementation Testing Deploy Done

2 2 1 1
ongoing waiting ongoing waiting
I C
D A

E F
B
G H

Product owner
 Kanban Methodology Example

Story Backlog To Do Implementation Testing Deploy Done

2 2 1 1
ongoing waiting ongoing waiting
I C
D
A
E F
B
G H

Product owner
 Kanban Methodology Example

Story Backlog To Do Implementation Testing Deploy Done

2 2 1 1
ongoing waiting ongoing waiting A
D C
I B

E F

G H

Product owner
 Kanban Methodology Example

Story Backlog To Do Implementation Testing Deploy Done

2 2 1 1
ongoing waiting ongoing waiting A
D E
I B

F
C
G H

Product owner
 Kanban Methodology Example

Story Backlog To Do Implementation Testing Deploy Done

2 2 1 1
ongoing waiting ongoing waiting A
D E
I B

F
C
G H

Product owner
Limiting Work in Progress (WIP)

1
Reduce Bottlenecks:
Limited WIP prevents too many tasks from accumulating in a single stage,
ensuring a smooth flow of work.

2
Improved Focus:
By focusing on fewer tasks at once, teams can deliver higher-quality
work and avoid context switching.

Faster Delivery:

3 Work moves through the system more efficiently, leading

to quicker task completion and reduced cycle times.
Continuous Improvement
with Kanban

Data-Driven Decisions:
Regularly track metrics like
cycle time, lead time, and WIP
to identify areas for
improvement.

Regular Retrospectives:
Dedicate time for team
meetings to reflect on the
process, discuss challenges,
and implement solutions.

Process Optimization:
Experiment with changes to the
workflow, such as adding new
columns or modifying existing
ones, to optimize the system.
Kanban Metrics and Analytics

1- Lead Time :
The time it takes for a
task to move from the
backlog to
completion.

2- Cycle Time :
WIP The time it takes to
complete a task from
Cycle time start to finish.
Lead time

3-Work in
Progress (WIP) :
The average number
of tasks being worked
on at any given time.
Kanban Tools

1- JIRA

2- Trello

3-Microsoft Planner

4-Kanbanize
Scrum V Kanban

Kanban Scrum

Planning, release, and process

Period Iteration is timeboxed.
improvement can have separate cadences.

Process the lead time is used as the default

Velocity is used as the default metric.
improvement metric.

Team Cross-functional teams are optional. Cross-functional teams prescribed.

Project contract for difference( CFD) can be used

Burndown chart is prescribed.
Tracking to understand workflow progress.

WIP limited WIP limited directly (per workflow state). WIP limited indirectly (per sprint).

Can add new items whenever the WIP

Modification Cannot add items to ongoing iteration.
limit falls.
 Scrumban

Scrumban is an agile project

management methodology that
combines the principles of Scrum and
Kanban into one.

Originally used to help teams swap

from Scrum to Kanban, Scrumban has
been maintained by teams who
appreciate its flexible, adaptable
approach to product development.
Why Scrumban?

Challenges in Scrum:
Fixed sprints can limit responsiveness.
Less adaptable to rapidly changing priorities.
Challenges in Kanban:
Lack of structure may lead to ambiguity in complex projects.
Scrumban as the Solution:
Flexibility of Kanban: Continuous flow and adaptability.
Structure of Scrum: Organized task management and planning.
Best for Evolving Projects: Ideal for ongoing product development or
maintenance.
Core Principles of Scrumban

Pull System
•:
• Tasks are pulled by the team as capacity allows

• .
Work-In-Progress (WIP) Limits
•:
• Restricts the number of tasks to prevent overload

• . Improvement
Continuous
•:
• Regular retrospectives for process enhancement

• . on Demand
Prioritization
•:
• No fixed sprints; prioritize tasks as needed

• .
Flow Management
• Focus on identifying and eliminating bottlenecks
Benefits of Scrumban

Continuous Improved
Increased Flexibility Reduced Waste
Improvement Collaboration
• Combines • Promotes regular • Encourages • Uses visual tools
Scrum’s structure reviews to teamwork to identify and
with Kanban’s optimize through daily eliminate
adaptability, workflows and stand-ups and inefficiencies,
allowing teams to boost productivity progress reviews, streamlining
handle changing keeping everyone workflows
requirements and aligned
respond quickly
to challenges
Drawbacks of Scrumban

Implementation
Complexity Lack of Clarity
Challenges
• More intricate • Can cause • Difficult to
than Scrum or confusion about adopt without
Kanban alone, roles and prior
requiring responsibilities, experience,
thorough leading to necessitating
knowledge and delays extra training
planning. and resources
How Scrumban Work?
How Scrumban Work?
When to use Scrumban

•:
Transitioning from Scrum to Kanban
• .
•: Projects with evolving requirements
• .
•: Teams needing flexibility with some structure
• .
•: Maintenance and operational teams
• .
 Jira Demo

What is Jira?

Jira is the #1 agile project management tool used by teams to plan, track, release and support world-

class software with confidence. It is the single source of truth for your entire development lifecycle,

empowering autonomous teams with the context to move quickly while staying connected to the

greater business goal. Whether used to manage simple projects or to power your DevOps practices,

makes it easy for teams to move work forward, stay aligned, and communicate in context.
 Jira Demo

Who uses Jira?

Jira launched in 2002 as an issue tracking and project management tool for teams. Since then, 300,000+ companies globally

have adopted Jira for its flexibility to support any type of project and extensibility to work with thousands of apps and

integrations.

• Agile teams

• Bug tracking teams

• DevOps teams

• Product management teams

• Project management teams

• Software development teams

Q&A
Thank you for
your Time!