This document provides an overview of agile methodologies, including Kanban and Scrum. It defines agile as an approach to project planning that emphasizes customer collaboration, working products, and responding to change. Kanban is introduced as an agile method used to manage work by limiting work in progress. Scrum is described as using iterative sprints to develop software in an incremental process involving product owners, scrum masters, and cross-functional teams. Key scrum rituals, metrics, and roles are outlined.

1. AGILE
METHODOLOGIES
Shristi Shrestha

2. OUTLINE OF TOPICS
Introduction to Agile
Kanban
Scrum
Overview

3. Introduction
to
Agile

4. Definition - agile
able to move quickly and easily

5. Projects - agile
an approach to planning
and working on projects

6. CUSTOMER COLLABORATION
OVER
Contract Negotiation
Agile
Manifesto
WORKING PRODUCT OVER
Comprehensive Documentation
INDIVIDUAL INTERACTIONS OVER
Processes and Tools
RESPONDING TO CHANGE OVER
Following a Plan

7. Introduction
to
Kanban

8. Definition - kanban
A Japanese word that means
"signboard"

9. Definition - kanban
An agile method used to manage a
continuous queue of work items

10. Limit Work in Progress
Turn work into bite sized pieces
Prioritize your task
Key Concepts

11. Limiting Work in
Progress

12. How?
Specify the minimum and/or
maximum number of issues
allowed in a certain Kanban
Board.

13. Why?
Better Flow
Visualize and identify bottlenecks
Prevents procrastination

15. Workspace
A single account can be attached to multiple trello
teams.

16. Boards
A free Trello workspace can have a maximum of
10 boards. Board can be made manually or using
templates.

17. Templates
You can use a pre-built template for your boards.

18. Power Ups
The additional services provided by Trello that
includes integration, card sync across multiple
boards, etc.

19. Hands On

20. Introduction
to
Scrum

21. Scrum is an agile, lightweight process
that can be used to manage and control
software and product development
using iterative and incremental
practices over boxed time periods
ranging from two to four weeks
Intended to give the team control of its
time and destiny

22. Scrum Process
Product Backlog Sprint Backog Sprint Working increment of
the software

23. Scrum
Roles

24. Product Owner
Define the features of the product
Decide on the release date and content
Be responsible for the profitability of the product
Prioritize features according to market value
Adjust features and priority every iteration, as needed
Accept or reject work results

25. Scrum Master
Responsible for ensuring that Scrum values, practices, and rules are
enacted and enforced
Represents management and the team to each other
Makes decisions and removes impediments
Sometimes making decisions without complete information (better
some decision rather than no decision)
Keep the team working at the highest possible level of productivity

26. Typically 5-9 people
Cross-functional:
Programmers, testers, user experience designers, etc.
Members should be full-time
May be exceptions (e.g., database administrator)
Teams are self-organizing
Membership should change only between sprints
Team Members

27. Sprint
Scrum project makes progress in a series of Sprints
Time boxed Period (2 - 4 weeks)
During Sprint, the team does:
Analysis
Design
Code
Test
Product is potentially releasable after every Sprint

28. Sprint
Team selects items from the product backlog they can commit to
completing
Sprint backlog is created
Tasks are identified and each is estimated (1 Point - 1 Day)
Fibonacci Practice (1,2,3,5,8, and so on.)
Plan is made collaboratively, not done alone by the Scrum Master

29. Scrum
Rituals

30. Daily Stand-up
Parameters
Daily
15-minutes
Stand-up
Not for problem-solving
Only team members, Scrum Master, Product Owner can talk
Helps avoid other unnecessary meetings

31. Sprint Planning
Before the sprint
Fix backlog
2 to 4 hours
Story point estimation

32. Sprint Retrospective
After the sprint
Reflection
Improvement for team
What went well
What could be better in the next sprint

33. Scrum
Metrics

34. Sprint Goal Success
A sprint goal can be the delivery
of a feature, addressing a risk,
or testing a feature
How?
Determine a sprint goal
Run the sprint
Validate if the goal has been
met

35. Team Velocity
How many user stories were
completed by the scrum team, on
average, in previous sprints
Importance: Estimation of how
much the team can accomplish in
future sprints
Team velocity is also a measure
that captures a scrum team's
progress
Story Points
0 10 20 30 40 50
1
2
3
4
5
6
7
8
9
10

36. Sprint Burndown
Representation of the
progress within a sprint
Tells whether a team is
on schedule to complete
the current sprint or not
The number of story
points remaining to
complete the stories
planned for the current
sprint

37. Q&A

38. Quiz

39. Relationship between
Agile and DevOps?

40. User + Stakeholders Designer, Developer, Tester Operations + Infrastucture
User + Stakeholders Designer, Developer, Tester Operations + Infrastucture
User + Stakeholders Designer, Developer, Tester Operations + Infrastucture
Agile
DevOps

41. Story
Points
Remaining
Story
Points
Remaining
Sprint Days Sprint Days

42. Thank You!