SlideShare a Scribd company logo
Agile Scrum Process
2016
Introduction
• Traditional Methodologies
• Agile Methodology
• Scrum
• Scrum Framework: Roles
• Scrum Framework: Ceremonies
• Scrum Framework: Artifacts
• Clarion Scrum Process-Review
Traditional Methodologies: Waterfall Model
• You complete one phase (e.g. design)
before moving on to the next
phase(e.g. development)
• You rarely aim to re-visit a ‘phase’ once
it’s completed. That means, you better
get whatever you’re doing right the first
time!
Traditional Methodologies: Waterfall Model
• You don’t realize any value until the end
of the project
• You leave the testing until the end
• You don’t seek approval from the
stakeholders until late in the day
• Takes too long…
**This approach is highly risky, often
more costly and generally less efficient
than Agile approaches
Takes too long
Changes
Skipped
Agile Meaning (Literally)
Ability to move quickly and easily….
Agile Methodology
Not a process, it's a philosophy or set of values…
Rapid Adaptive Agile Quality-Driven Cooperative Iterative
Process and tools
Comprehensive documentation
Following a plan
Contract negotiation
Agile Manifesto
Individuals and interactions
Working software
Customer collaboration
Responding to change
O
V
E
R
12 Agile Principles
• Our highest priority is to satisfy the customer through early and continuous
delivery of valuable software.
1 ROI
12 Agile Principles
• Welcome changing requirements, even late in development. Agile processes
harness change for the customer's competitive advantage.
2 CHANGEABILITY
12 Agile Principles
• Deliver working software frequently, from a couple of weeks to a couple of
months, with a preference to the shorter timescale.
3 GETTING REAL
12 Agile Principles
• Business people and developers must work together daily throughout the
project.
4 ALIGNMENT
12 Agile Principles
• Build projects around motivated individuals. Give them the environment and
support they need, and trust them to get the job done.
5 SELF
ORGANIZATION
12 Agile Principles
• The most efficient and effective method of conveying information to and within
a development team is face-to-face conversation.
6 BANDWIDTH
12 Agile Principles
• Working software is the primary measure of progress.
7 DONE
12 Agile Principles
• Agile processes promote sustainable development. The sponsors, developers,
and users should be able to maintain a constant pace indefinitely.
8 SUSTAINABILITY
12 Agile Principles
• Continuous attention to technical excellence and good design enhances agility.
9 IMPROVEMENT
12 Agile Principles
• Simplicity —the art of maximizing the amount of work not done —is essential.
10 KEEP IT SIMPLE,
STUPID (KISS)
12 Agile Principles
• The best architectures, requirements, and designs emerge from self-organizing
teams.
11 EMERGE
12 Agile Principles
• At regular intervals, the team reflects on how to become more effective, then
tunes and adjusts its behavior accordingly.
12 INSPECT & ADOPT
Various Agile Methodologies
Meaning Of Scrum (Literally)
What Is Scrum?
• Scrum is an agile framework that allows us to focus on delivering the highest
business value in the shortest time.
• It allows us to rapidly and repeatedly inspect actual working software (every two
weeks to one month).
• The business sets the priorities. Teams self-organize to determine the best way
to deliver the highest priority features.
• Every two weeks to a month anyone can see real working software and decide
to release it as is or continue to enhance it for another sprint.
Scrum Origins
Controversies
Some professionals believe
that Jeff Sutherland, John
Scumniotales and Jeff
McKenna invented Scrum
in 1993.
Others, who vouch for
HirotakaTakeuchi and
IkujiroNonakaas inventing
Scrum in 1986.
Who Is Using Scrum?
Electronic Arts
Lockheed Martin
Microsoft
Google
Siemens Capital
One
Ipswitching Sabre BBC
High Moon Studios
Turner Broadcasting
First American Real Estate
Nielsen Media
Lexis Nexis
Salesforce.com
Amazon
Yahoo
BMC Software
John Deere Time Warner
Clarion Technologies
Where To Use Scrum?
• Commercial software
• In-house development
• Contract development
• Fixed-price projects
• Financial applications
• ISO 9001-certified applications
• Embedded systems
• 24x7 systems with 99.999% uptime
requirements
• The Joint Strike Fighter
• Video game development
• FDA-approved, life-critical
systems
• Satellite-control software
• Websites
• Handheld software
• Mobile phones
• Network switching applications
• ISV applications
• Some of the largest applications
in use
Scrum Framework
• Product owner
• Scrum Master
• Team
Roles
• Sprint planning
• Sprint review
• Sprint retrospective
• Daily scrum meeting
Ceremonies
• Product backlog
• Sprint backlog
• Burndown charts
Artifacts
Scrum Framework
• Product owner
• Scrum Master
• Team
Roles
• Sprint planning
• Sprint review
• Sprint retrospective
• Daily scrum meeting
Ceremonies
• Product backlog
• Sprint backlog
• Burndown charts
Artifacts
Role: Product Owner
• Define the features of the product
• Decide on release date and content
• Be responsible for the profitability of the product (ROI)
• Prioritize features according to market value
• Adjust features and priority every iteration, as needed
• Accept or reject work results
Role: Scrum Master
• Represents management to the project
• Responsible for enacting Scrum values and practices
• Removes impediments
• Ensure that the team is fully functional and productive
• Enable close cooperation across all roles and functions
• Shield the team from external interferences
Role: The Team
• 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
• Ideally, no titles but rarely a possibility
• Membership should change only between sprints.
Clarion Role Mapping
Product owner/
Shadow product owner
Scrum master
Cross functional scrum
team
Product owner is generally from client side and
shadow product owner would be from BA/SA
offshore side. In some cases product owner could
be from offshore, who has gained detailed
product/system knowledge, this scenario does not
require Shadow PO.
Team facilitator from offshore side to drive overall
scrum process
Technical Architect (onsite + offshore), Technical
Leader, QA, Developers and Designers.
Scrum Master
PO PO
Cross-functional
scrum team
Scrum Framework
• Product owner
• Scrum Master
• Team
Roles
• Sprint planning
• Sprint review
• Sprint retrospective
• Daily scrum meeting
Ceremonies
• Product backlog
• Sprint backlog
• Burndown charts
Artifacts
Ceremony: Sprint Planning Meeting
• Team selects items from the product backlog they can commit to completing
• Sprint backlog is created
• Tasks are identified and each is estimated (1-16 hours)
• Collaboratively, not done alone by the Scrum Master
• High-level design is considered
Clarion: Sprint Planning Meeting
• Purpose: At every sprint start, sprint backlog is created out of product backlog.
• Participants: Product owner, scrum master, team
• Duration: This is a time-boxed meeting, duration depends on the duration of
sprint and complexity of the items.
• Highlights:
• Fibonacci point based estimates which would be related to the complexity / time of
the tasks.
• Stories are discussed in sprint planning meeting and estimation will be given by
developers on based of story, planning poker is used for the user story
estimation.
• Generally for 1 point we consider 2-3 hours work, 2 pointer it is a half day work, 3
pointer is a days work and 5 pointer is 2 days work.
Planning Poker
• Product Owner reads story
• Team estimates (including QA/Testing)
• Team Discusses
• Team estimates again
This process is repeated till consensus
is reached.
PO
... …… …..
5
3
1
Clarion Pre-sprint Planning Meeting
• Happens a day before actual Sprint planning meeting.
• All the internal team members participate.
• Few the tentative stories are picked from the prioritized product backlog.
• Team discuss and understands the stories and the underlying challenges and
questions in the upcoming stories.
• For the new team it is suggested to do the point estimation also during pre-
sprint planning.
• The purpose is to facilitate the main Sprint planning with client.
Ceremony: Daily Standup
• Parameters
• Daily
• 15-minutes
• Stand-up
• Not for problem solving
• Whole world is invited
• Only team members, Scrum Master, Product Owner, can talk
• Helps avoid other unnecessary meetings
Clarion DSM
Purpose:
• Each team member summarizes
• What was done yesterday
• What would be done today
• If there are any Issues being faced.
• This helps coordinating priorities of the
day.
• Participants: Product owner, scrum
master, team
• Duration: Short duration of around 15
minutes.
Scrum Master
PO PO
Cross-functional
scrum team
Yesterday I did…
Today I plan to…
I am facing some impediments...
Ceremony: Sprint Review
• Team presents what it accomplished during the sprint
• Typically takes the form of a demo of new features or underlying architecture
• Informal
• 2-hour prep time rule
• No slides
• Whole team participates
• Invite the world
Ceremony: Sprint Review
• Purpose: At the sprint execution end, sprint
review meeting would be held for following
• Shippable product would be demoed to the
Product Owner (PO) in this meeting.
• Product Owner (PO) can accept or reject the
Scrum Backlog items presented in the demo.
• There could be new product backlog items
identified during this meeting
• Participants: Product owner, scrum master,
team, interested stakeholders
• Duration: In general this meeting should not
be longer than one hour per week of sprint
duration.
Scrum Master
PO PO
Cross-functional
scrum team
I declare that following product
backlog items as “Done”
1.…
2.…
Based on feedback we need to
add some new product backlog
items.
Stakeholders
(optional)
Ceremony: Sprint Retrospective
• Periodically take a look at what is and is not working
• Typically 15–30 minutes
• Done after every sprint
• Whole team participates
• Scrum Master
• Product owner
• Team
• Possibly customers and others
Clarion Sprint Retrospective Meeting
• Purpose: This meeting is held at the end of
each sprint (after the sprint review), it
facilitates team to inspect and adapt its
process to optimize efficiency.
• In this meeting following points would be
discussed.
• What went well in the sprint.
• What did not went well in the sprint.
• How can we enhance.
• The output of this meeting becomes the input
for next sprint for enhancing the practice.
• Participants: Product owner, scrum master,
team
• Duration: In general this meeting should not
be longer than 45 minutes for each week of
sprint duration.
Scrum Master
PO PO
Cross-functional
scrum team
... …… …..
... …… …..
... …… …..
Add On’s: Clarion Product Backlog Grooming meeting
• Purpose: This is done couple of work
days before next sprint planning meeting,
which give product owner little time to
revise priorities before commitments are
made. Team focuses on top few items
only, this helps the team to clarify &
decompose the higher priority PBIs
• Participants: Product owner, scrum
master
• Duration: In general this meeting should
not be longer than 2 hours.
Scrum Master
PO PO
Cross-functional
scrum team
Requirement Requirement
Requirement Requirement
Requirement Requirement
Requirement Requirement
Requirement
Requirement
Requirement
Requirement
Requirement Requirement
Sprint Planned
Groomed
Future
Sprintable
Actionable/ User Stories
Epic / Cosmic Stories
Scrum Framework
• Product owner
• Scrum Master
• Team
Roles
• Sprint planning
• Sprint review
• Sprint retrospective
• Daily scrum meeting
Ceremonies
• Product backlog
• Sprint backlog
• Burndown charts
Artifacts
Artifact: Product Backlog
• The requirements
• A list of all desired work on the project
• Ideally expressed such that each item has value to the users or customers of
the product
• Prioritized by the product owner
• Reprioritized before the start of each sprint
Clarion Product Backlog
• It is prioritized list of user stories
covering whole product/system.
• Before the sprint planning meeting
product Backlog items will be created by
Product Owner(PO) in collaboration with
Business Analyst(BA) from offshore side,
who would act as a shadow product
owner.
• Stories defined should follow INVEST
principle of Scrum.
• Break down Epics.
Scrum Master
PO PO
Cross-functional
scrum team
WORK ITEM 1
High Priority Items
WORK ITEM 2
WORK ITEM 3
WORK ITEM 4
WORK ITEM 5
WORK ITEM 6
User Story
A concise, written description of a piece of functionality that will be
valuable to a user (or owner) of the software.
A user story should be detailed enough for the team to start work from,
and further details can be established and clarified at the time of
development.
3C’s Of User Story
• Card - A written description of the user story for planning purposes and as a
reminder.
• Conversation - A section for capturing further information about the user story
and details of any conversations.
• Confirmation - A section to convey what tests will be carried out to confirm the
user story is complete and working as expected.
User Story: Invest In It
• Independent - User Stories should be as independent as possible.
• Negotiable - User Stories are not a contract. They are not detailed
specifications. They are reminders of features for the team to discuss and
collaborate to clarify the details near the time of development.
• Valuable - User Stories should be valuable to the user (or owner) of the
solution. They should be written in user language. They should be features, not
tasks.
• Estimable - User Stories need to be possible to estimate. They need to provide
enough information to estimate, without being too detailed.
• Small - User Stories should be small. Not too small. But not too big.
• Testable - User Stories need to be worded in a way that is testable, i.e. not too
subjective and to provide clear details of how the User Story will be tested.
User Story: Format
As a [role] I want to [a feature] so that [reason, value].
As a frequent traveler I want to be able to quickly rebook frequently booked
flights so that I can save time during the booking process.
User Story: Example
• Epic#1: User Authentication and Authorization Module
• Story#1: Registration System for school user
• Description: As a visitor of the site, I want to be able to register by providing my
email and password in order to use the available features.
• Acceptance Criteria:
• I should be presented with a link on top right corner to register titled ‘Register’.
• I should be presented with a form asking email, password, password confirmation.
• I should be presented with a Register button, clicking on which I should be
registered as a user on app.
• I should be presented with errors in case of incorrect email format and a password
shorter than 8 chars.
Artifact: Sprint Backlog
• The sprint backlog is a list of tasks identified by the Scrum team to be
completed during the Scrum “Sprint”.
• During the sprint planning meeting, the team selects some number of product
backlog items
What Is Sprint?
A sprint is a set period of time during which specific work has to be
completed and made ready for review.
More precisely we can say a Sprint is a Time Box.
• During the actual sprint, team implements the user stories committed to the
sprint backlog in continuous integration mode.
• Duration: Usually from 2 weeks to 4 weeks.
Clarion Sprint Cycle
Design &
Analysis
Implementation
& unit testing
Continuous
Integration
Testing & QA
Deployment
Detailed
requirements
Every sprint consists of iteration of following tasks
Actual Sprint - Starting Mid-week
• Advantages & probable scenarios when this cycle would be suggested
• This way even if we have to stretch a bit to finish some tasks, team would not
hesitate to do it during mid-week.
• In addition to this if teams are working in distributed agile set-up, then mid-week
start helps the product owner to be easily available.
• This cycle is suitable when the releases can be done on weekdays.
2 WEEK SPRINT STARTING MID WEEK (10 WORKING DAYS)
TUE WED THU FRI MON TUE WED THU MONFRI
-----------
-----------------------------------------------------------------------------------------------------
---------------------------------------------
-----------
Sprint
planning
meeting
Daily standup meeting Product backlog grooming Sprint review /
retrospective
Actual Sprint - Starting On Monday
• Advantages & probable scenarios when this cycle would be suggested
• This cycle is suitable when the releases can only be done on weekends.
2 WEEK SPRINT STARTING MID WEEK (10 WORKING DAYS)
MON TUE WED THU FRI MON TUE WED FRITHU
-----------
-----------------------------------------------------------------------------------------------------
---------------------------------------------
-----------
Sprint
planning
meeting
Daily standup meeting Product backlog grooming Sprint review /
retrospective
Sprint Zero
• Purpose: This is carried out to initiate
the overall scrum process and the
logistics related to the project.
• Participants: all the team participates
in this sprint and it is driven by scrum
master.
• Duration: Approximately 2 weeks
Scrum Master
PO PO
Cross-functional
scrum team
Sprint Zero High Level Tasks
• Initial grooming of the product catalog.
• Decide maximum base point for user story.
• Decide the sprint duration and sprint release cycle.
• Technical understanding by team.
• How and where QA would be done.
• Setting up environments.
Artifact: Burn-down Chart
• Tells us about:
• How much work is remaining to be
done in the project
• How much deviation we are having
from the current estimation or are we
pulling in lot of tasks in the sprint
Ideal Team Great Team Nice Team Too Fast Too Late
Sample burn down and inferences
0
50
100
150
200
250
300
Add On’s: Burn-up Chart
• Tells us about:
• How much work has been completed,
and the total amount of work.
• How the sprint is progressing with
reference to change in scope.
0
10
20
30
40
50
60
1 1 / 4 1 2 / 4 1 3 / 4 1 6 / 4 1 7 / 4 1 8 / 4 1 9 / 4 2 0 / 4 2 3 / 4 2 4 / 4
No.oftickets
BU R N U P TASK
Total April
Add On’s: Velocity Chart
• Shows the amount of value delivered in
each sprint, enabling you to predict the
amount of work the team can get done
in future sprints.
• It is useful during your sprint planning
meetings, to help you decide how much
work you can feasibly commit to.
• Initial velocity figures could below,
however a steam moves forward we get
the better idea about the capability of
the team.
Sprint 1 Sprint 2 Sprint 3 Sprint 4
Commitment 40 53 56 57
Completed 37 47 50 57
0
10
20
30
40
50
60
StoryPoints
V ELO CITY CHAR T
Commitment Completed
Clarion Scrum Process - An Overview
Information Radiator
Online Scrum Tool
Cross-functional
scrum team
WORK ITEM 1
WORK ITEM 2
WORK ITEM 3
WORK ITEM 4
WORK ITEM 5
WORK ITEM 6
PRODUCT BACKLOG
WORK ITEM 1
WORK ITEM 2
WORK ITEM 3
SPRINT BACKLOG
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
TASK
PRODUCT
INCREMENT
Sprint
Preplanning
Sprint
Zero
Sprint Planning
Meeting
Daily
Scrum
Meeting
Sprint
Review
Meeting
Sprint
Retrospective
Meeting
Design Code
Analysis
Deploy Test
CI
Scrum
Master
PO PO
Product
Backlog
Grooming
Clarion Scrum Process
Thank You!

More Related Content

What's hot

Scrum
ScrumScrum
Scrum
Sujoy Saha
 
Agile - Scrum Presentation
Agile - Scrum PresentationAgile - Scrum Presentation
Agile - Scrum Presentation
gihanlsw
 
Agile Scrum Presentation-Detailed
Agile Scrum Presentation-DetailedAgile Scrum Presentation-Detailed
Agile Scrum Presentation-Detailed
Prashaanth T R
 
Scrum framework
Scrum frameworkScrum framework
Scrum framework
Rashmi Pathak
 
Agile Introduction - Scrum Framework
Agile Introduction - Scrum FrameworkAgile Introduction - Scrum Framework
Agile Introduction - Scrum Framework
Kshitij Yelkar MBA/PMP/CSM/ICP-ACC
 
Scrum In Ten Slides (v2.0) 2018
Scrum In Ten Slides (v2.0) 2018Scrum In Ten Slides (v2.0) 2018
Scrum In Ten Slides (v2.0) 2018
pmengal
 
Scrum 101
Scrum 101 Scrum 101
Scrum 101
Ozgur Ertem
 
Scrum In Ten Slides
Scrum In Ten SlidesScrum In Ten Slides
Scrum In Ten Slides
pmengal
 
Scrum 101: Introduction to Scrum
Scrum 101: Introduction to ScrumScrum 101: Introduction to Scrum
Scrum 101: Introduction to Scrum
Arrielle Mali
 
Scrum
ScrumScrum
Scrumban
ScrumbanScrumban
Scrum - Product Owner
Scrum - Product OwnerScrum - Product Owner
Scrum - Product Owner
Márcio Oya
 
Scrum Agile Methodlogy
Scrum Agile MethodlogyScrum Agile Methodlogy
Scrum Agile Methodlogy
Bahaa Farouk
 
Scrum
ScrumScrum
What does a Scrum Master do, or should do, all day?
What does a Scrum Master do, or should do, all day? What does a Scrum Master do, or should do, all day?
What does a Scrum Master do, or should do, all day?
Stefania Marinelli
 
Scrum master basics
Scrum master basics Scrum master basics
Scrum master basics
Elad Sofer
 
Scrum for Beginners
Scrum for BeginnersScrum for Beginners
Scrum for Beginners
Anjana Saxena
 
Agile & Scrum Training
Agile & Scrum TrainingAgile & Scrum Training
Agile & Scrum Training
Conscires Agile Practices
 
Scrum Process
Scrum ProcessScrum Process
Scrum Process
John Lewis
 
Agile Methodology
Agile MethodologyAgile Methodology
Agile Methodology
Aciron Consulting
 

What's hot (20)

Scrum
ScrumScrum
Scrum
 
Agile - Scrum Presentation
Agile - Scrum PresentationAgile - Scrum Presentation
Agile - Scrum Presentation
 
Agile Scrum Presentation-Detailed
Agile Scrum Presentation-DetailedAgile Scrum Presentation-Detailed
Agile Scrum Presentation-Detailed
 
Scrum framework
Scrum frameworkScrum framework
Scrum framework
 
Agile Introduction - Scrum Framework
Agile Introduction - Scrum FrameworkAgile Introduction - Scrum Framework
Agile Introduction - Scrum Framework
 
Scrum In Ten Slides (v2.0) 2018
Scrum In Ten Slides (v2.0) 2018Scrum In Ten Slides (v2.0) 2018
Scrum In Ten Slides (v2.0) 2018
 
Scrum 101
Scrum 101 Scrum 101
Scrum 101
 
Scrum In Ten Slides
Scrum In Ten SlidesScrum In Ten Slides
Scrum In Ten Slides
 
Scrum 101: Introduction to Scrum
Scrum 101: Introduction to ScrumScrum 101: Introduction to Scrum
Scrum 101: Introduction to Scrum
 
Scrum
ScrumScrum
Scrum
 
Scrumban
ScrumbanScrumban
Scrumban
 
Scrum - Product Owner
Scrum - Product OwnerScrum - Product Owner
Scrum - Product Owner
 
Scrum Agile Methodlogy
Scrum Agile MethodlogyScrum Agile Methodlogy
Scrum Agile Methodlogy
 
Scrum
ScrumScrum
Scrum
 
What does a Scrum Master do, or should do, all day?
What does a Scrum Master do, or should do, all day? What does a Scrum Master do, or should do, all day?
What does a Scrum Master do, or should do, all day?
 
Scrum master basics
Scrum master basics Scrum master basics
Scrum master basics
 
Scrum for Beginners
Scrum for BeginnersScrum for Beginners
Scrum for Beginners
 
Agile & Scrum Training
Agile & Scrum TrainingAgile & Scrum Training
Agile & Scrum Training
 
Scrum Process
Scrum ProcessScrum Process
Scrum Process
 
Agile Methodology
Agile MethodologyAgile Methodology
Agile Methodology
 

Viewers also liked

Agile Scrum Training, Day 1 (1/2)
Agile Scrum Training, Day 1 (1/2)Agile Scrum Training, Day 1 (1/2)
Agile Scrum Training, Day 1 (1/2)
Jens Wilke
 
Attention Middle Management Chickens
Attention Middle Management ChickensAttention Middle Management Chickens
Attention Middle Management Chickens
Siddhi
 
Egg3 | Agile CRM Deployment
Egg3 | Agile CRM DeploymentEgg3 | Agile CRM Deployment
Egg3 | Agile CRM Deployment
Olivier Caeymaex
 
Get_Bent_On_Agile
Get_Bent_On_AgileGet_Bent_On_Agile
ITIL for Agile
ITIL for AgileITIL for Agile
ITIL for Agile
rslomkow
 
K16-PPM-SCRUM-Presentation
K16-PPM-SCRUM-PresentationK16-PPM-SCRUM-Presentation
K16-PPM-SCRUM-Presentation
Charles A. Dyer, MBA, PMP
 
Agile Scrum training
Agile Scrum trainingAgile Scrum training
Agile Scrum training
jagannathun manoharan
 
Agile games
Agile gamesAgile games
Agile games
Aaron Corcoran
 
On agile games and how to develop one
On agile games and how to develop oneOn agile games and how to develop one
On agile games and how to develop one
Ralf Kruse
 
D3 Design By Games Agile India Pune 2005
D3 Design By Games   Agile India   Pune 2005D3 Design By Games   Agile India   Pune 2005
D3 Design By Games Agile India Pune 2005
Henry Jacob
 
Game On!
Game On!Game On!
Game On!
Jeremy Hutton
 
Agile Mëtteg - April 2011
Agile Mëtteg - April 2011Agile Mëtteg - April 2011
Agile Mëtteg - April 2011
Agile Partner S.A.
 
Agile games night
Agile games night Agile games night
Agile games night
BestBrains
 
Agile Scrum Training (Part 3)
Agile Scrum Training (Part 3)Agile Scrum Training (Part 3)
Agile Scrum Training (Part 3)
Jeremy Hutton
 
Disruptus Spiel - AUG Bremen Oldenburg von Kai Hermanns & Christian Beck
Disruptus Spiel - AUG Bremen Oldenburg von Kai Hermanns & Christian BeckDisruptus Spiel - AUG Bremen Oldenburg von Kai Hermanns & Christian Beck
Disruptus Spiel - AUG Bremen Oldenburg von Kai Hermanns & Christian Beck
Ralf Kruse
 
Play at Work: Agile Games for Productive Teams
Play at Work: Agile Games for Productive TeamsPlay at Work: Agile Games for Productive Teams
Play at Work: Agile Games for Productive Teams
xianpants
 
Let`s Agile !
Let`s Agile !Let`s Agile !
Agile Games 2012 Keynote - Games Landscape and Importance of Play
Agile Games 2012 Keynote - Games Landscape and Importance of PlayAgile Games 2012 Keynote - Games Landscape and Importance of Play
Agile Games 2012 Keynote - Games Landscape and Importance of Play
Michael Sahota
 
Agile Tour Delhi NCR2014 - Agile innovation games rahul sudame
Agile Tour Delhi NCR2014 - Agile innovation games   rahul sudameAgile Tour Delhi NCR2014 - Agile innovation games   rahul sudame
Agile Tour Delhi NCR2014 - Agile innovation games rahul sudame
India Scrum Enthusiasts Community
 
Putting it All Together: Agile & ITIL
Putting it All Together: Agile & ITILPutting it All Together: Agile & ITIL
Putting it All Together: Agile & ITIL
Beyond20
 

Viewers also liked (20)

Agile Scrum Training, Day 1 (1/2)
Agile Scrum Training, Day 1 (1/2)Agile Scrum Training, Day 1 (1/2)
Agile Scrum Training, Day 1 (1/2)
 
Attention Middle Management Chickens
Attention Middle Management ChickensAttention Middle Management Chickens
Attention Middle Management Chickens
 
Egg3 | Agile CRM Deployment
Egg3 | Agile CRM DeploymentEgg3 | Agile CRM Deployment
Egg3 | Agile CRM Deployment
 
Get_Bent_On_Agile
Get_Bent_On_AgileGet_Bent_On_Agile
Get_Bent_On_Agile
 
ITIL for Agile
ITIL for AgileITIL for Agile
ITIL for Agile
 
K16-PPM-SCRUM-Presentation
K16-PPM-SCRUM-PresentationK16-PPM-SCRUM-Presentation
K16-PPM-SCRUM-Presentation
 
Agile Scrum training
Agile Scrum trainingAgile Scrum training
Agile Scrum training
 
Agile games
Agile gamesAgile games
Agile games
 
On agile games and how to develop one
On agile games and how to develop oneOn agile games and how to develop one
On agile games and how to develop one
 
D3 Design By Games Agile India Pune 2005
D3 Design By Games   Agile India   Pune 2005D3 Design By Games   Agile India   Pune 2005
D3 Design By Games Agile India Pune 2005
 
Game On!
Game On!Game On!
Game On!
 
Agile Mëtteg - April 2011
Agile Mëtteg - April 2011Agile Mëtteg - April 2011
Agile Mëtteg - April 2011
 
Agile games night
Agile games night Agile games night
Agile games night
 
Agile Scrum Training (Part 3)
Agile Scrum Training (Part 3)Agile Scrum Training (Part 3)
Agile Scrum Training (Part 3)
 
Disruptus Spiel - AUG Bremen Oldenburg von Kai Hermanns & Christian Beck
Disruptus Spiel - AUG Bremen Oldenburg von Kai Hermanns & Christian BeckDisruptus Spiel - AUG Bremen Oldenburg von Kai Hermanns & Christian Beck
Disruptus Spiel - AUG Bremen Oldenburg von Kai Hermanns & Christian Beck
 
Play at Work: Agile Games for Productive Teams
Play at Work: Agile Games for Productive TeamsPlay at Work: Agile Games for Productive Teams
Play at Work: Agile Games for Productive Teams
 
Let`s Agile !
Let`s Agile !Let`s Agile !
Let`s Agile !
 
Agile Games 2012 Keynote - Games Landscape and Importance of Play
Agile Games 2012 Keynote - Games Landscape and Importance of PlayAgile Games 2012 Keynote - Games Landscape and Importance of Play
Agile Games 2012 Keynote - Games Landscape and Importance of Play
 
Agile Tour Delhi NCR2014 - Agile innovation games rahul sudame
Agile Tour Delhi NCR2014 - Agile innovation games   rahul sudameAgile Tour Delhi NCR2014 - Agile innovation games   rahul sudame
Agile Tour Delhi NCR2014 - Agile innovation games rahul sudame
 
Putting it All Together: Agile & ITIL
Putting it All Together: Agile & ITILPutting it All Together: Agile & ITIL
Putting it All Together: Agile & ITIL
 

Similar to Agile Scrum Training Process

Scrum workshop - September 7, 2012
Scrum workshop - September 7, 2012Scrum workshop - September 7, 2012
Scrum workshop - September 7, 2012
MrAlexRosales
 
scrum
scrumscrum
scrum
Noman sial
 
Practicing Agile through Scrum
Practicing Agile through ScrumPracticing Agile through Scrum
Practicing Agile through Scrum
Naveen Kumar Singh
 
Scrum in action
Scrum in actionScrum in action
Scrum in action
Mona Shokrof
 
Scrum methodology
Scrum methodology Scrum methodology
Scrum methodology
C.T.Co
 
Agile Session @ Universidade Portucalense
Agile Session @ Universidade PortucalenseAgile Session @ Universidade Portucalense
Agile Session @ Universidade Portucalense
Rui M. Barreira
 
Scrum toufiq
Scrum toufiqScrum toufiq
Scrum toufiq
Toufiq Mahmud
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Agile with scrum methodology
Agile with scrum methodologyAgile with scrum methodology
Agile with scrum methodology
Abhishek Srivastava
 
Agile Scrum CMMI
Agile Scrum CMMIAgile Scrum CMMI
Agile Scrum CMMI
Rabiraj Khadka
 
Introduction to scrum
Introduction to scrumIntroduction to scrum
Introduction to scrum
William Simms
 
Agile by KD
Agile by KDAgile by KD
Agile by KD
Karl Dickman
 
Agile by KD
Agile by KDAgile by KD
Agile by KD
Karl Dickman
 
SCRUM and Poker Game In Agile Project
SCRUM and Poker Game In Agile ProjectSCRUM and Poker Game In Agile Project
SCRUM and Poker Game In Agile Project
Nhan Nguyen
 
Scrum Intro for E-works
Scrum Intro for E-worksScrum Intro for E-works
Scrum Intro for E-works
Nora Papazyan
 
Introduction to Scrum – Hassan Jaffal
Introduction to Scrum – Hassan Jaffal Introduction to Scrum – Hassan Jaffal
Introduction to Scrum – Hassan Jaffal
Agile Tour Beirut
 
Agile-Scrum Methodology-An Introduction
Agile-Scrum Methodology-An IntroductionAgile-Scrum Methodology-An Introduction
Agile-Scrum Methodology-An Introduction
XBOSoft
 
Agile Methodology
Agile MethodologyAgile Methodology
Agile Methodology
AnveshPatel7
 
English redistributable-intro-scrum
English redistributable-intro-scrumEnglish redistributable-intro-scrum
English redistributable-intro-scrum
Sean Mike
 
Scrum training
Scrum trainingScrum training
Scrum training
Qasim Mehmood MBA-PM
 

Similar to Agile Scrum Training Process (20)

Scrum workshop - September 7, 2012
Scrum workshop - September 7, 2012Scrum workshop - September 7, 2012
Scrum workshop - September 7, 2012
 
scrum
scrumscrum
scrum
 
Practicing Agile through Scrum
Practicing Agile through ScrumPracticing Agile through Scrum
Practicing Agile through Scrum
 
Scrum in action
Scrum in actionScrum in action
Scrum in action
 
Scrum methodology
Scrum methodology Scrum methodology
Scrum methodology
 
Agile Session @ Universidade Portucalense
Agile Session @ Universidade PortucalenseAgile Session @ Universidade Portucalense
Agile Session @ Universidade Portucalense
 
Scrum toufiq
Scrum toufiqScrum toufiq
Scrum toufiq
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
 
Agile with scrum methodology
Agile with scrum methodologyAgile with scrum methodology
Agile with scrum methodology
 
Agile Scrum CMMI
Agile Scrum CMMIAgile Scrum CMMI
Agile Scrum CMMI
 
Introduction to scrum
Introduction to scrumIntroduction to scrum
Introduction to scrum
 
Agile by KD
Agile by KDAgile by KD
Agile by KD
 
Agile by KD
Agile by KDAgile by KD
Agile by KD
 
SCRUM and Poker Game In Agile Project
SCRUM and Poker Game In Agile ProjectSCRUM and Poker Game In Agile Project
SCRUM and Poker Game In Agile Project
 
Scrum Intro for E-works
Scrum Intro for E-worksScrum Intro for E-works
Scrum Intro for E-works
 
Introduction to Scrum – Hassan Jaffal
Introduction to Scrum – Hassan Jaffal Introduction to Scrum – Hassan Jaffal
Introduction to Scrum – Hassan Jaffal
 
Agile-Scrum Methodology-An Introduction
Agile-Scrum Methodology-An IntroductionAgile-Scrum Methodology-An Introduction
Agile-Scrum Methodology-An Introduction
 
Agile Methodology
Agile MethodologyAgile Methodology
Agile Methodology
 
English redistributable-intro-scrum
English redistributable-intro-scrumEnglish redistributable-intro-scrum
English redistributable-intro-scrum
 
Scrum training
Scrum trainingScrum training
Scrum training
 

Recently uploaded

FREE A4 Cyber Security Awareness Posters-Social Engineering part 3
FREE A4 Cyber Security Awareness  Posters-Social Engineering part 3FREE A4 Cyber Security Awareness  Posters-Social Engineering part 3
FREE A4 Cyber Security Awareness Posters-Social Engineering part 3
Data Hops
 
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframeDigital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Precisely
 
Serial Arm Control in Real Time Presentation
Serial Arm Control in Real Time PresentationSerial Arm Control in Real Time Presentation
Serial Arm Control in Real Time Presentation
tolgahangng
 
5th LF Energy Power Grid Model Meet-up Slides
5th LF Energy Power Grid Model Meet-up Slides5th LF Energy Power Grid Model Meet-up Slides
5th LF Energy Power Grid Model Meet-up Slides
DanBrown980551
 
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
Jason Yip
 
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Biomedical Knowledge Graphs for Data Scientists and BioinformaticiansBiomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Neo4j
 
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success StoryDriving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Safe Software
 
WeTestAthens: Postman's AI & Automation Techniques
WeTestAthens: Postman's AI & Automation TechniquesWeTestAthens: Postman's AI & Automation Techniques
WeTestAthens: Postman's AI & Automation Techniques
Postman
 
Digital Marketing Trends in 2024 | Guide for Staying Ahead
Digital Marketing Trends in 2024 | Guide for Staying AheadDigital Marketing Trends in 2024 | Guide for Staying Ahead
Digital Marketing Trends in 2024 | Guide for Staying Ahead
Wask
 
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
Alex Pruden
 
GNSS spoofing via SDR (Criptored Talks 2024)
GNSS spoofing via SDR (Criptored Talks 2024)GNSS spoofing via SDR (Criptored Talks 2024)
GNSS spoofing via SDR (Criptored Talks 2024)
Javier Junquera
 
Taking AI to the Next Level in Manufacturing.pdf
Taking AI to the Next Level in Manufacturing.pdfTaking AI to the Next Level in Manufacturing.pdf
Taking AI to the Next Level in Manufacturing.pdf
ssuserfac0301
 
"Choosing proper type of scaling", Olena Syrota
"Choosing proper type of scaling", Olena Syrota"Choosing proper type of scaling", Olena Syrota
"Choosing proper type of scaling", Olena Syrota
Fwdays
 
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
saastr
 
JavaLand 2024: Application Development Green Masterplan
JavaLand 2024: Application Development Green MasterplanJavaLand 2024: Application Development Green Masterplan
JavaLand 2024: Application Development Green Masterplan
Miro Wengner
 
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptxChoosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Brandon Minnick, MBA
 
Apps Break Data
Apps Break DataApps Break Data
Apps Break Data
Ivo Velitchkov
 
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development ProvidersYour One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
akankshawande
 
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing InstancesEnergy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Alpen-Adria-Universität
 
Dandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity serverDandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity server
Antonios Katsarakis
 

Recently uploaded (20)

FREE A4 Cyber Security Awareness Posters-Social Engineering part 3
FREE A4 Cyber Security Awareness  Posters-Social Engineering part 3FREE A4 Cyber Security Awareness  Posters-Social Engineering part 3
FREE A4 Cyber Security Awareness Posters-Social Engineering part 3
 
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframeDigital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
 
Serial Arm Control in Real Time Presentation
Serial Arm Control in Real Time PresentationSerial Arm Control in Real Time Presentation
Serial Arm Control in Real Time Presentation
 
5th LF Energy Power Grid Model Meet-up Slides
5th LF Energy Power Grid Model Meet-up Slides5th LF Energy Power Grid Model Meet-up Slides
5th LF Energy Power Grid Model Meet-up Slides
 
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
 
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Biomedical Knowledge Graphs for Data Scientists and BioinformaticiansBiomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
 
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success StoryDriving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
 
WeTestAthens: Postman's AI & Automation Techniques
WeTestAthens: Postman's AI & Automation TechniquesWeTestAthens: Postman's AI & Automation Techniques
WeTestAthens: Postman's AI & Automation Techniques
 
Digital Marketing Trends in 2024 | Guide for Staying Ahead
Digital Marketing Trends in 2024 | Guide for Staying AheadDigital Marketing Trends in 2024 | Guide for Staying Ahead
Digital Marketing Trends in 2024 | Guide for Staying Ahead
 
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
 
GNSS spoofing via SDR (Criptored Talks 2024)
GNSS spoofing via SDR (Criptored Talks 2024)GNSS spoofing via SDR (Criptored Talks 2024)
GNSS spoofing via SDR (Criptored Talks 2024)
 
Taking AI to the Next Level in Manufacturing.pdf
Taking AI to the Next Level in Manufacturing.pdfTaking AI to the Next Level in Manufacturing.pdf
Taking AI to the Next Level in Manufacturing.pdf
 
"Choosing proper type of scaling", Olena Syrota
"Choosing proper type of scaling", Olena Syrota"Choosing proper type of scaling", Olena Syrota
"Choosing proper type of scaling", Olena Syrota
 
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
 
JavaLand 2024: Application Development Green Masterplan
JavaLand 2024: Application Development Green MasterplanJavaLand 2024: Application Development Green Masterplan
JavaLand 2024: Application Development Green Masterplan
 
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptxChoosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
 
Apps Break Data
Apps Break DataApps Break Data
Apps Break Data
 
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development ProvidersYour One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
 
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing InstancesEnergy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
 
Dandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity serverDandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity server
 

Agile Scrum Training Process

  • 2. Introduction • Traditional Methodologies • Agile Methodology • Scrum • Scrum Framework: Roles • Scrum Framework: Ceremonies • Scrum Framework: Artifacts • Clarion Scrum Process-Review
  • 3. Traditional Methodologies: Waterfall Model • You complete one phase (e.g. design) before moving on to the next phase(e.g. development) • You rarely aim to re-visit a ‘phase’ once it’s completed. That means, you better get whatever you’re doing right the first time!
  • 4. Traditional Methodologies: Waterfall Model • You don’t realize any value until the end of the project • You leave the testing until the end • You don’t seek approval from the stakeholders until late in the day • Takes too long… **This approach is highly risky, often more costly and generally less efficient than Agile approaches Takes too long Changes Skipped
  • 5. Agile Meaning (Literally) Ability to move quickly and easily….
  • 6. Agile Methodology Not a process, it's a philosophy or set of values… Rapid Adaptive Agile Quality-Driven Cooperative Iterative
  • 7. Process and tools Comprehensive documentation Following a plan Contract negotiation Agile Manifesto Individuals and interactions Working software Customer collaboration Responding to change O V E R
  • 8. 12 Agile Principles • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 1 ROI
  • 9. 12 Agile Principles • Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 2 CHANGEABILITY
  • 10. 12 Agile Principles • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 3 GETTING REAL
  • 11. 12 Agile Principles • Business people and developers must work together daily throughout the project. 4 ALIGNMENT
  • 12. 12 Agile Principles • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 5 SELF ORGANIZATION
  • 13. 12 Agile Principles • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 6 BANDWIDTH
  • 14. 12 Agile Principles • Working software is the primary measure of progress. 7 DONE
  • 15. 12 Agile Principles • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 8 SUSTAINABILITY
  • 16. 12 Agile Principles • Continuous attention to technical excellence and good design enhances agility. 9 IMPROVEMENT
  • 17. 12 Agile Principles • Simplicity —the art of maximizing the amount of work not done —is essential. 10 KEEP IT SIMPLE, STUPID (KISS)
  • 18. 12 Agile Principles • The best architectures, requirements, and designs emerge from self-organizing teams. 11 EMERGE
  • 19. 12 Agile Principles • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. 12 INSPECT & ADOPT
  • 21. Meaning Of Scrum (Literally)
  • 22. What Is Scrum? • Scrum is an agile framework that allows us to focus on delivering the highest business value in the shortest time. • It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month). • The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features. • Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.
  • 23. Scrum Origins Controversies Some professionals believe that Jeff Sutherland, John Scumniotales and Jeff McKenna invented Scrum in 1993. Others, who vouch for HirotakaTakeuchi and IkujiroNonakaas inventing Scrum in 1986.
  • 24. Who Is Using Scrum? Electronic Arts Lockheed Martin Microsoft Google Siemens Capital One Ipswitching Sabre BBC High Moon Studios Turner Broadcasting First American Real Estate Nielsen Media Lexis Nexis Salesforce.com Amazon Yahoo BMC Software John Deere Time Warner Clarion Technologies
  • 25. Where To Use Scrum? • Commercial software • In-house development • Contract development • Fixed-price projects • Financial applications • ISO 9001-certified applications • Embedded systems • 24x7 systems with 99.999% uptime requirements • The Joint Strike Fighter • Video game development • FDA-approved, life-critical systems • Satellite-control software • Websites • Handheld software • Mobile phones • Network switching applications • ISV applications • Some of the largest applications in use
  • 26. Scrum Framework • Product owner • Scrum Master • Team Roles • Sprint planning • Sprint review • Sprint retrospective • Daily scrum meeting Ceremonies • Product backlog • Sprint backlog • Burndown charts Artifacts
  • 27. Scrum Framework • Product owner • Scrum Master • Team Roles • Sprint planning • Sprint review • Sprint retrospective • Daily scrum meeting Ceremonies • Product backlog • Sprint backlog • Burndown charts Artifacts
  • 28. Role: Product Owner • Define the features of the product • Decide on release date and content • Be responsible for the profitability of the product (ROI) • Prioritize features according to market value • Adjust features and priority every iteration, as needed • Accept or reject work results
  • 29. Role: Scrum Master • Represents management to the project • Responsible for enacting Scrum values and practices • Removes impediments • Ensure that the team is fully functional and productive • Enable close cooperation across all roles and functions • Shield the team from external interferences
  • 30. Role: The Team • 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 • Ideally, no titles but rarely a possibility • Membership should change only between sprints.
  • 31. Clarion Role Mapping Product owner/ Shadow product owner Scrum master Cross functional scrum team Product owner is generally from client side and shadow product owner would be from BA/SA offshore side. In some cases product owner could be from offshore, who has gained detailed product/system knowledge, this scenario does not require Shadow PO. Team facilitator from offshore side to drive overall scrum process Technical Architect (onsite + offshore), Technical Leader, QA, Developers and Designers. Scrum Master PO PO Cross-functional scrum team
  • 32. Scrum Framework • Product owner • Scrum Master • Team Roles • Sprint planning • Sprint review • Sprint retrospective • Daily scrum meeting Ceremonies • Product backlog • Sprint backlog • Burndown charts Artifacts
  • 33. Ceremony: Sprint Planning Meeting • Team selects items from the product backlog they can commit to completing • Sprint backlog is created • Tasks are identified and each is estimated (1-16 hours) • Collaboratively, not done alone by the Scrum Master • High-level design is considered
  • 34. Clarion: Sprint Planning Meeting • Purpose: At every sprint start, sprint backlog is created out of product backlog. • Participants: Product owner, scrum master, team • Duration: This is a time-boxed meeting, duration depends on the duration of sprint and complexity of the items. • Highlights: • Fibonacci point based estimates which would be related to the complexity / time of the tasks. • Stories are discussed in sprint planning meeting and estimation will be given by developers on based of story, planning poker is used for the user story estimation. • Generally for 1 point we consider 2-3 hours work, 2 pointer it is a half day work, 3 pointer is a days work and 5 pointer is 2 days work.
  • 35. Planning Poker • Product Owner reads story • Team estimates (including QA/Testing) • Team Discusses • Team estimates again This process is repeated till consensus is reached. PO ... …… ….. 5 3 1
  • 36. Clarion Pre-sprint Planning Meeting • Happens a day before actual Sprint planning meeting. • All the internal team members participate. • Few the tentative stories are picked from the prioritized product backlog. • Team discuss and understands the stories and the underlying challenges and questions in the upcoming stories. • For the new team it is suggested to do the point estimation also during pre- sprint planning. • The purpose is to facilitate the main Sprint planning with client.
  • 37. Ceremony: Daily Standup • Parameters • Daily • 15-minutes • Stand-up • Not for problem solving • Whole world is invited • Only team members, Scrum Master, Product Owner, can talk • Helps avoid other unnecessary meetings
  • 38. Clarion DSM Purpose: • Each team member summarizes • What was done yesterday • What would be done today • If there are any Issues being faced. • This helps coordinating priorities of the day. • Participants: Product owner, scrum master, team • Duration: Short duration of around 15 minutes. Scrum Master PO PO Cross-functional scrum team Yesterday I did… Today I plan to… I am facing some impediments...
  • 39. Ceremony: Sprint Review • Team presents what it accomplished during the sprint • Typically takes the form of a demo of new features or underlying architecture • Informal • 2-hour prep time rule • No slides • Whole team participates • Invite the world
  • 40. Ceremony: Sprint Review • Purpose: At the sprint execution end, sprint review meeting would be held for following • Shippable product would be demoed to the Product Owner (PO) in this meeting. • Product Owner (PO) can accept or reject the Scrum Backlog items presented in the demo. • There could be new product backlog items identified during this meeting • Participants: Product owner, scrum master, team, interested stakeholders • Duration: In general this meeting should not be longer than one hour per week of sprint duration. Scrum Master PO PO Cross-functional scrum team I declare that following product backlog items as “Done” 1.… 2.… Based on feedback we need to add some new product backlog items. Stakeholders (optional)
  • 41. Ceremony: Sprint Retrospective • Periodically take a look at what is and is not working • Typically 15–30 minutes • Done after every sprint • Whole team participates • Scrum Master • Product owner • Team • Possibly customers and others
  • 42. Clarion Sprint Retrospective Meeting • Purpose: This meeting is held at the end of each sprint (after the sprint review), it facilitates team to inspect and adapt its process to optimize efficiency. • In this meeting following points would be discussed. • What went well in the sprint. • What did not went well in the sprint. • How can we enhance. • The output of this meeting becomes the input for next sprint for enhancing the practice. • Participants: Product owner, scrum master, team • Duration: In general this meeting should not be longer than 45 minutes for each week of sprint duration. Scrum Master PO PO Cross-functional scrum team ... …… ….. ... …… ….. ... …… …..
  • 43. Add On’s: Clarion Product Backlog Grooming meeting • Purpose: This is done couple of work days before next sprint planning meeting, which give product owner little time to revise priorities before commitments are made. Team focuses on top few items only, this helps the team to clarify & decompose the higher priority PBIs • Participants: Product owner, scrum master • Duration: In general this meeting should not be longer than 2 hours. Scrum Master PO PO Cross-functional scrum team Requirement Requirement Requirement Requirement Requirement Requirement Requirement Requirement Requirement Requirement Requirement Requirement Requirement Requirement Sprint Planned Groomed Future Sprintable Actionable/ User Stories Epic / Cosmic Stories
  • 44. Scrum Framework • Product owner • Scrum Master • Team Roles • Sprint planning • Sprint review • Sprint retrospective • Daily scrum meeting Ceremonies • Product backlog • Sprint backlog • Burndown charts Artifacts
  • 45. Artifact: Product Backlog • The requirements • A list of all desired work on the project • Ideally expressed such that each item has value to the users or customers of the product • Prioritized by the product owner • Reprioritized before the start of each sprint
  • 46. Clarion Product Backlog • It is prioritized list of user stories covering whole product/system. • Before the sprint planning meeting product Backlog items will be created by Product Owner(PO) in collaboration with Business Analyst(BA) from offshore side, who would act as a shadow product owner. • Stories defined should follow INVEST principle of Scrum. • Break down Epics. Scrum Master PO PO Cross-functional scrum team WORK ITEM 1 High Priority Items WORK ITEM 2 WORK ITEM 3 WORK ITEM 4 WORK ITEM 5 WORK ITEM 6
  • 47. User Story A concise, written description of a piece of functionality that will be valuable to a user (or owner) of the software. A user story should be detailed enough for the team to start work from, and further details can be established and clarified at the time of development.
  • 48. 3C’s Of User Story • Card - A written description of the user story for planning purposes and as a reminder. • Conversation - A section for capturing further information about the user story and details of any conversations. • Confirmation - A section to convey what tests will be carried out to confirm the user story is complete and working as expected.
  • 49. User Story: Invest In It • Independent - User Stories should be as independent as possible. • Negotiable - User Stories are not a contract. They are not detailed specifications. They are reminders of features for the team to discuss and collaborate to clarify the details near the time of development. • Valuable - User Stories should be valuable to the user (or owner) of the solution. They should be written in user language. They should be features, not tasks. • Estimable - User Stories need to be possible to estimate. They need to provide enough information to estimate, without being too detailed. • Small - User Stories should be small. Not too small. But not too big. • Testable - User Stories need to be worded in a way that is testable, i.e. not too subjective and to provide clear details of how the User Story will be tested.
  • 50. User Story: Format As a [role] I want to [a feature] so that [reason, value]. As a frequent traveler I want to be able to quickly rebook frequently booked flights so that I can save time during the booking process.
  • 51. User Story: Example • Epic#1: User Authentication and Authorization Module • Story#1: Registration System for school user • Description: As a visitor of the site, I want to be able to register by providing my email and password in order to use the available features. • Acceptance Criteria: • I should be presented with a link on top right corner to register titled ‘Register’. • I should be presented with a form asking email, password, password confirmation. • I should be presented with a Register button, clicking on which I should be registered as a user on app. • I should be presented with errors in case of incorrect email format and a password shorter than 8 chars.
  • 52. Artifact: Sprint Backlog • The sprint backlog is a list of tasks identified by the Scrum team to be completed during the Scrum “Sprint”. • During the sprint planning meeting, the team selects some number of product backlog items
  • 53. What Is Sprint? A sprint is a set period of time during which specific work has to be completed and made ready for review. More precisely we can say a Sprint is a Time Box. • During the actual sprint, team implements the user stories committed to the sprint backlog in continuous integration mode. • Duration: Usually from 2 weeks to 4 weeks.
  • 54. Clarion Sprint Cycle Design & Analysis Implementation & unit testing Continuous Integration Testing & QA Deployment Detailed requirements Every sprint consists of iteration of following tasks
  • 55. Actual Sprint - Starting Mid-week • Advantages & probable scenarios when this cycle would be suggested • This way even if we have to stretch a bit to finish some tasks, team would not hesitate to do it during mid-week. • In addition to this if teams are working in distributed agile set-up, then mid-week start helps the product owner to be easily available. • This cycle is suitable when the releases can be done on weekdays. 2 WEEK SPRINT STARTING MID WEEK (10 WORKING DAYS) TUE WED THU FRI MON TUE WED THU MONFRI ----------- ----------------------------------------------------------------------------------------------------- --------------------------------------------- ----------- Sprint planning meeting Daily standup meeting Product backlog grooming Sprint review / retrospective
  • 56. Actual Sprint - Starting On Monday • Advantages & probable scenarios when this cycle would be suggested • This cycle is suitable when the releases can only be done on weekends. 2 WEEK SPRINT STARTING MID WEEK (10 WORKING DAYS) MON TUE WED THU FRI MON TUE WED FRITHU ----------- ----------------------------------------------------------------------------------------------------- --------------------------------------------- ----------- Sprint planning meeting Daily standup meeting Product backlog grooming Sprint review / retrospective
  • 57. Sprint Zero • Purpose: This is carried out to initiate the overall scrum process and the logistics related to the project. • Participants: all the team participates in this sprint and it is driven by scrum master. • Duration: Approximately 2 weeks Scrum Master PO PO Cross-functional scrum team Sprint Zero High Level Tasks • Initial grooming of the product catalog. • Decide maximum base point for user story. • Decide the sprint duration and sprint release cycle. • Technical understanding by team. • How and where QA would be done. • Setting up environments.
  • 58. Artifact: Burn-down Chart • Tells us about: • How much work is remaining to be done in the project • How much deviation we are having from the current estimation or are we pulling in lot of tasks in the sprint Ideal Team Great Team Nice Team Too Fast Too Late Sample burn down and inferences 0 50 100 150 200 250 300
  • 59. Add On’s: Burn-up Chart • Tells us about: • How much work has been completed, and the total amount of work. • How the sprint is progressing with reference to change in scope. 0 10 20 30 40 50 60 1 1 / 4 1 2 / 4 1 3 / 4 1 6 / 4 1 7 / 4 1 8 / 4 1 9 / 4 2 0 / 4 2 3 / 4 2 4 / 4 No.oftickets BU R N U P TASK Total April
  • 60. Add On’s: Velocity Chart • Shows the amount of value delivered in each sprint, enabling you to predict the amount of work the team can get done in future sprints. • It is useful during your sprint planning meetings, to help you decide how much work you can feasibly commit to. • Initial velocity figures could below, however a steam moves forward we get the better idea about the capability of the team. Sprint 1 Sprint 2 Sprint 3 Sprint 4 Commitment 40 53 56 57 Completed 37 47 50 57 0 10 20 30 40 50 60 StoryPoints V ELO CITY CHAR T Commitment Completed
  • 61. Clarion Scrum Process - An Overview
  • 62. Information Radiator Online Scrum Tool Cross-functional scrum team WORK ITEM 1 WORK ITEM 2 WORK ITEM 3 WORK ITEM 4 WORK ITEM 5 WORK ITEM 6 PRODUCT BACKLOG WORK ITEM 1 WORK ITEM 2 WORK ITEM 3 SPRINT BACKLOG TASK TASK TASK TASK TASK TASK TASK TASK TASK TASK TASK TASK TASK TASK TASK PRODUCT INCREMENT Sprint Preplanning Sprint Zero Sprint Planning Meeting Daily Scrum Meeting Sprint Review Meeting Sprint Retrospective Meeting Design Code Analysis Deploy Test CI Scrum Master PO PO Product Backlog Grooming Clarion Scrum Process