SlideShare una empresa de Scribd logo
1 de 63
Descargar para leer sin conexión
Agile Concepts
Introduction To Agile Practices
Joaquim Ferreira
About Me
Joaquim Ferreira
.NET Engineer
@ Truphone
Email:
joaquimf@truphone.com
Profile:
http://www.linkedin.com/in
/joaquimluisdaluzferreira
Certified Scrum Master
License 000138872
June 2011 to June 2015
Agenda
1 2 3 4 5
6
Agile Manifesto
Features
When
Principles Benefits
Differences
7
How
8
Practices
9
Scrum
10
Kanban
Agile Manifest
Individuals and
interactions over
processes and tools
Working software
over comprehensive
documentation
Customer
collaboration over
contract negotiation
Responding to
change over
following a plan
http://www.agilemanifesto.org/
Kent Beck
Mike Beedle
Arie van Bennekum
Alistair Cockburn
Ward Cunningham
Martin Fowle
James Grenning
Jim Highsmith
Andrew Hunt
Ron Jeffries
Jon Kern
Brian Marick
Robert C. Martin
Steve Mellor
Ken Schwaber
Jeff Sutherland
Dave Thomas
12 Principles
Our highest priority is to satisfy
the customer
through early and continuous
delivery
of valuable software
Welcome changing
requirements, even late in
development. Agile processes
harness change for
the customer's competitive
advantage
Deliver working software
frequently, from a
couple of weeks to a couple of
months, with a
preference to the shorter
timescale
Business people and
developers must work
together daily throughout the
project
Build projects around
motivated individuals.
Give them the environment
and support they need,
and trust them to get the job
done
The most efficient and effective
method of
conveying information to and
within a development
team is face-to-face
conversation
12 Principles
Working software is the primary
measure of progress
Agile processes promote
sustainable development.
The sponsors, developers, and
users should be able
to maintain a constant pace
indefinitely
Continuous attention to
technical excellence
and good design enhances
agility
Simplicity--the art of
maximizing the amount
of work not done--is essential
The best architectures,
requirements, and designs
emerge from self-organizing
teams
At regular intervals, the team
reflects on how
to become more effective,
then tunes and adjusts
its behavior accordingly
Features
Iterative
1. Entire work is distributed in incremental units called iteration:
2. Development time of each iteration is small (couple of weeks) and fixed;
3. Every Iteration is a mini increment of the functionality and is build on top of previous
iteration;
Feature driven
1. More emphasis is on providing the required features in the application;
2. 80/20 principle is applied to decide the 20% features which would be used 80% of the
time ( Pareto Principle );
Active Customer involvement
1. There is lot of client involvement and face-to-face interaction;
2. Every iteration is tested and approved by client;
3. The feedback obtained is implemented in subsequent iterations;
Features
Priority based delivery
1. Features are prioritized depending on customer need, development risk etc.;
2. High priority features are developed first;
3. After every iteration, the project priorities are re-evaluated;
Adaptive
1. The applications that are developed can receive new requirements throughout its
development;
2. The goal is not to remove the uncertainty in the very beginning;
3. But is to adapt to the changing needs;
Empowered Teams
1. The project teams are generally small and have lot of interaction and communication;
2. Since entire team is actively involved, team is empowered to take decisions;
3. No separate team to manage project;
Features
People Centric
1. Emphasis is on using the adequately skilled people to do the development than on
following the processes;
2. The documentation and other non-development activities are minimized and more
time is devoted to development and testing;
More disciplined
1. So the process involves lot of team and self discipline thus, it requires highly skilled
and organized team members;
Rapid development
1. Being rapid, everything has to be delivered correctly first time.
Features
Simplicity
1. Emphasis is on keeping things as simple as possible and being open to change;
Fixed Time
1. Each iteration has a fixed time span in which it is delivered;
Benefits
For the customer
1. Customer is more actively involved, and gets higher priority;
2. He gets to know regular and frequent status of the application;
3. Requirements are accepted after each iteration;
4. Since the methodology emphasizes rapid delivery, time-to-
market is less. So the key functionalities can be available to use
sooner;
5. Delivery is defined by fixed timescale. So customer is assured of
receiving some functionality by a fixed time period;
6. More Testing is done, so better software quality is delivered;
Benefits
For the project team
• Project teams are involved more actively in all the
stages;
• The teams collaboratively take the decisions and
are more empowered;
• Development is Incremental, teams can focus on
the specific requirements at any given point of
time;
Benefits
For the project team
• More emphasis is on developing the application only;
• The teams receive frequent feedback as the testing is
integrated; so the rework is reduced;
• Less time is spent in gathering requirements as all the
requirements are not gathered upfront and are
implemented as and when they arise;
Benefits
For the project team
• Less cost of development as rework, management,
documentation and other non-development work
related cost is reduced;
• Teams develop applications collaboratively and in
cooperative environment;
• So less time is required for planning;
Differences
Requirements Fixed Evolve
AgileTraditional
Time & People May Change Fixed
Costumer Involvement Before, After Throughout
Negotiable Estimates Schedule
Testing After Work Integrated
Feedback After Work During
Concentration On Processes; Reviews Finished Work
Focus On Plan On Value
Stages
Requirements, Design, Code, Test,
Feedbacks
Plan-Do-Check-Adjust
When
We use Agile when …
We have the customer available.
We can split the deliver.
The requirements are flexible.
The team is skilled enough.
When
Because we will need
Organization support
Hierarchy
ready to
empower
teams
Culture
open to
changes
Focus on add value to the
business
Infrastructure and team
support
Preferable the team and the
customer should be co-located
Hardware support for
continuous integration and
other practices
Highly skilled
& flexible
people
More &
frequent
testing
How
Starts with a kick-off meeting
1. Get requirements and / or feedback;
2. Plan & evaluate priorities;
3. Design;
4. Develop;
5. Test;
6. Document what is done;
7. Deliver;
1
2
3
4
5
6
7
Split the functionalities in small delivers and repeat:
Practices
Scrum
Kanban
eXtreme Programing
ScrumBan
Lean Software Development
DynamicSystemsDevelopmentMethods
Feature Driven Development
Scrum
Is an agile process
that allows us to
focus on delivering
the highest
business value in
the shortest time.
Allows us to rapidly and repeatedly inspect
actual work.
The business sets the priorities.
The Teams self-organize to determine the best
way to deliver the highest priority features.
So that in the end of an iteration anyone can
see real work and decide to release it as is or
continue to enhance it for another iteration.
What
Scrum
No specific engineering
practices prescribed
Self-organizing teams
Product progresses in a series of
month-long “sprints”
Requirements are captured as
items in a list of “product backlog”
Characteristics
Uses generative rules to
create an agile environment
for delivering projects
Scrum
Sprint
Requirements
Starts with a kick-off meeting
• Scrum projects make progress
in a series of “sprints”;
• Typical duration is 2–4 weeks
or a calendar month at most;
• Product is designed, coded,
and tested during the sprint;
• No changes during a sprint;
Design
Do
Test
Scrum
Rather than doing all of one thing at a time...
… Scrum teams do a little of everything all the time
Requirements
Design
Build
Test
Requirements
Design
Build
Test
Scrum
Framework
Roles Ceremonies
Artefacts
Scrum
Roles
Product Owner Scrum Master
Team
Scrum
Product Owner
Starts with a kick-off meeting
• Define the features of the product;
• Decide on release date and content;
• Be responsible for the profitability of the product
(R.O.I.);
• Prioritize features according to market value;
• Adjust features and priority every iteration, as
needed;
• Accept or reject work results;
Scrum
Scrum Master
Starts with a kick-off meeting
• Removes impediments;
• Represents management to the project;
• Responsible for enacting Scrum values and
practices;
• Ensure that the team is fully functional and
productive;
• Enable close cooperation across all roles and
functions;
• Shield the team from external interferences;
Scrum
Team
Members should be full-time
• Teams are self-organizing:
• Ideally, no titles but rarely a possibility;
• Cross-functional:
• Programmers, testers, user experience
designers, etc.;
• Members should be full-time;
• Membership should change only between sprints;
Scrum
Ceremonies
Sprint Planning
Sprint Review Sprint Retrospective
Daily Scrum
Scrum
Sprint Planning Meeting
Planning
Decide how to achieve sprint goal (design)
Create Sprint backlog (tasks) from Product
Backlog (Features/Stories)
Estimate Sprint Backlog in hours.
Scrum
Daily Scrum
Parameters
Daily
15-minutes
Stand-Up
Not for problem solving
Just to Inform
Only team members and Scrum Master talk
Whole world is invited
Others may talk if Team allow
Scrum
Daily Scrum
What will you do today ?
1
2
3 Is anything in your way ?
What did you do yesterday ?
3Questions
Scrum
Sprint Review/Demo
Members should be full-time
• 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;
Scrum
Sprint Retrospective
Members should be full-time
• Periodically take a look at what is and is not working;
• Done after every sprint;
• Whole team participates:
• Scrum Master;
• Product owner;
• Team;
• Possibly customers and others;
Scrum
Sprint Retrospective
Whole team gathers and discusses what they’d like to:
Start Doing
Continue Doing
Stop Doing
Scrum
Artefacts
Product Backlog
…Product Increment
Sprint Backlog
Scrum
Product Backlog
Members should be full-time
• Prioritized list of the functionality to be developed
in a product or service;
• User stories have emerged as the best and most
popular form of product backlog items;
• Ideally expressed such that each item has value to
the users or customers of the product;
• Prioritized by the product owner;
• Reprioritized at the start of each sprint;
Scrum
Sprint Backlog
Members should be full-time
• The list of tasks identified by the Scrum team
during sprint planning;
• Its is estimated in Hours;
• Individuals sign up for work of their own
choosing;
• Estimated work remaining is updated daily;
• Any team member can add, delete or change
the sprint backlog;
• Individuals sign up for work of their own
choosing;
Scrum
Product Increment
Members should be full-time
• In every Sprint is produced one;
• Must be of high enough quality to be given
to users
• Must meet the Scrum Team's current
Definition of Done
• Each component of it be acceptable to the
Product Owner
Scrum
User Story
Members should be full-time
• Short, simple description of a feature told from the
perspective of the person who desires the new
capability;
• They typically follow a simple template:
• As a <type of user>, I want <some goal> so
that <some reason>;
• Should contain the conditions of satisfaction for
the story be consider done (Acceptance Criteria);
Scrum
Task Board
Members should be full-time
• Used to update the changes of state of the tasks during the sprint;
• Each story have a row to the board;
• Each column represents a state of the work;
• The tasks change of state until be finished;
Scrum
Burn Down Charts
Members should be full-time
• Show the amount of work remaining either in a
sprint or a release:
• The Release Burn Down Chart tracks the
release remaining work;
• The Sprint Burn Down Chart tracks the
sprint remaining work;
• They determining at a glance whether a sprint
or release is on schedule to have all planned
work finished by the desired date;
Scrum
This is Scrum
Kanban
The Kanban is an
agile process based
on Lean practices
and aims to
streamline the
development
process of a
product
Means Visual Signaling
Visibility into the status of the work and how it
is proceeding
Shows what is happening on the process.
Allowing to detect the problems during the
process.
Gives more precise direction on how to invest
the energy into only the most valuable work
What
Kanban
Change the priorities anytime
Visualization of the work flow
Deliver anytime
No need of iterations
Characteristics
Optimize Existing Processes
Introduction of visualization and the
limiting of work-in-progress (WIP) will
catalyse change with minimal
disruption
Kanban
Core Principles
1 - Visualize the Workflow
Represent the work items and the workflow on a card wall or electronic board;
2 - Limit Work-in-Progress (WIP)
Set agreed upon limits to how many work items are in progress at a time;
3 - Measure & Manage Flow
Track work items to see if they are proceeding at a steady, even pace;
4 - Make Process Policies Explicit
Agree upon and post policies about how work will be handled;
5 - Use Models to Evaluate Improvement Oportunities
Adapt the process using ideas from Systems Thinking;
Kanban
Visualize the workflow
Todo InProgres BlockedTest Done
Members should be full-time
Kanban
Visualize the workflow
• The card wall should reflects the current work process, with the intent to
improve it over time.
• Draw columns on the board that represent the activities performed, in
the order first performed.
• The cards themselves could be sticky notes or index cards.
• They may represent features, stories or tasks.
• Critical information for a card would be title, reference number, and date
it entered the system;
Kanban
Limit Work In Progress ( W.I.P)
Todo InProgres BlockedTest Done
W.I.P: 10 W.I.P: 5 W.I.P: 4 W.I.P: 3
Members should be full-time
Kanban
Limit Work In Progress ( W.I.P)
• A limit on work-in-progress constrains how many work items can be in
each workflow step at a time;
• When a work item progresses, a slot opens and a new work item can flow
into the workflow step;
• A key result of a W.I.P. limit is that blocked work “holds up the line”;
• No new work can progress on the workflow step until the block is
resolved;
• The W.I.P. limit provokes the conversations that lead to improvements;
Kanban
Limit Work In Progress ( W.I.P)
How big a limit ?
• W.I.P. limits for workflow steps should be set as an average number of items
per person;
• Limits should be in the range of one to three items per person, pair or team;
Agreed upon limits ?
• W.I.P. limits should be agreed upon through consensus with up- and
downstream stakeholders and senior function management as well as the
development team;
• Not every step must have a limit;
Kanban
Limit Work In Progress ( W.I.P)
No W.I.P. limit?
Care should be taken when establishing any unlimited on workflow steps !!!
• Does not introduce bottlenecks;
• Cause excessive transaction;
• Cause excessive coordination costs when are made;
Kanban
Measure And Manage Flow
Todo InProgres BlockedTest Done
W.I.P: 10 W.I.P: 5 W.I.P: 4 W.I.P: 3
Lead Time
Kanban
Measure And Manage Flow
Lead Time
Starts when the request is made and ends at delivery;
Is what the customer sees;
Cycle Time
Starts when work begins on the request and ends when the item is ready for delivery;
What the team can influence by itself by changing its work process
Reaction Time
The time until the work begins on the request.
Lead Time
Reaction
To reduce Lead Times one should reduce Cycle Time.
But often the time before the work starts is really long.
So this wait time should be reduced also.
Cycle Time
Kanban
Explicit Process policies
It is often best to post explicit process policies in a public team area such as next
to the card wall
Workflow
Should agree upon policies regarding:
W.I.P Limits
Approvals Prioritization
Other Process Topics
Kanban
Use models to evaluate improvement
• Womack & Jones on Waste Reduction
• Eliyahu M. Goldratt on Theory of Constraints
• John Seddon and Peter Senge on Systems Thinking
• W. Edwards Deming’s System of Profound Knowledge and specifically his work on variability
• Taiichi Ohno (Toyota Production System) on muda, muri and mura.
Flow Time
Gather data on system performance as:
W.I.P
Useful models to learn and use may include work from:
Kanban Vs Scrum
Scrum Kanban
Fixed-length iterations Required Optional
Commitment to a specific amount of
work
Required - at the personal daily level and
at the team level (per sprint)
Optional
Metrics for planning process
improvement
Velocity Lead Time
Cross-functional teams Required Optional
Item size So it can be completed within one sprint No particular
Prescribed diagram type Burn down chart No particular
Work-in-progress limits Per sprint Per workflow state
Kanban Vs Scrum
Scrum Kanban
Estimations Required Optional
Adding new items to ongoing iteration Not allowed Allowed
Sharing sprint backlog/ kanban board Within one team With multiple teams or individuals
Prescribed team roles
Project Owner, Scrum Master, Team
Member
No
Board life-time Reset after each iteration Persistent
Prioritization Requires a prioritized product backlog No
How do you work?
Kanban Scrum
• Your work is often interrupted with new,
immediate tasks.
• You need to be flexible and highly responsive to
changes.
• You are unable to lock your backlog for a couple
of weeks.
• Your work more often involves repeatable tasks
than new ones.
• You do feature development which relies heavily on
stakeholders' feedback.
• You can run only one project at a time.
Kanban Vrs Scrum
What is your team type?
Kanban Scrum
• You have a small, medium or large team of
specialists in the same or related fields.
• Your team is small and cross-functional.
Kanban Vrs Scrum
What is the specificity of your organization?
Kanban Scrum
• Your organization has low maturity.
• You have a limited capability of risk taking, change
management and decisions making.
• You have time to let the culture and performance
evolve and improve.
• Your organization is highly mature.
• You are capable of assessing risk, managing changes,
evaluating alternatives and making good quality
decisions.
• You can only make changes in your company using
shock therapy - revolution in your organizational
culture and approach to team and project
management
Kanban Vrs Scrum
Sources
Manifesto for Agile Software
Development
http://www.agilemanifesto.org/
http://www.mountaingoatsoftware.com/
Portions of this presentation are based on the next sources:
http://www.indicthreads.com/1439/quick-
introduction-to-agile-software-development/
http://refcardz.dzone.com/refcardz/ge
tting-started-kanban
Questions

Más contenido relacionado

La actualidad más candente

Overview of Agile Methodology
Overview of Agile MethodologyOverview of Agile Methodology
Overview of Agile MethodologyHaresh Karkar
 
Scrum 101
Scrum 101Scrum 101
Scrum 101beLithe
 
Tips n' Tricks - Sprint Review
Tips n' Tricks - Sprint ReviewTips n' Tricks - Sprint Review
Tips n' Tricks - Sprint ReviewSteve Greene
 
Kanban Basics for Beginners
Kanban Basics for BeginnersKanban Basics for Beginners
Kanban Basics for BeginnersZsolt Fabok
 
Definition Of Done
Definition Of DoneDefinition Of Done
Definition Of DoneWei Zhu
 
Customer Success Management interview presentation
Customer Success Management interview presentationCustomer Success Management interview presentation
Customer Success Management interview presentationChris
 
PopcornFlow: Continuous Evolution Through Ultra-Rapid Experimentation
PopcornFlow: Continuous Evolution Through Ultra-Rapid ExperimentationPopcornFlow: Continuous Evolution Through Ultra-Rapid Experimentation
PopcornFlow: Continuous Evolution Through Ultra-Rapid ExperimentationClaudio Perrone
 
Management fundamentals scrum 101
Management fundamentals scrum 101Management fundamentals scrum 101
Management fundamentals scrum 101Bar-Ezer Yossi
 
Taking Care of your Product by HubSpot PM
Taking Care of your Product by HubSpot PMTaking Care of your Product by HubSpot PM
Taking Care of your Product by HubSpot PMProduct School
 
Metodologia scrum actual
Metodologia scrum actualMetodologia scrum actual
Metodologia scrum actualMiriam Peña
 
Introduction to Agile Hardware
Introduction to Agile Hardware Introduction to Agile Hardware
Introduction to Agile Hardware Cprime
 
Agile Values, Principles and Practices
Agile Values, Principles and PracticesAgile Values, Principles and Practices
Agile Values, Principles and Practicesjackcrews
 
Kanban introduction
Kanban introductionKanban introduction
Kanban introductionAhmed Hammad
 
Training - Introducing Agile, Lean and Kanban
Training - Introducing Agile, Lean and KanbanTraining - Introducing Agile, Lean and Kanban
Training - Introducing Agile, Lean and KanbanSudipta Lahiri
 

La actualidad más candente (20)

Overview of Agile Methodology
Overview of Agile MethodologyOverview of Agile Methodology
Overview of Agile Methodology
 
Scrum 101
Scrum 101Scrum 101
Scrum 101
 
Kanban Trojan Horse_(2022).pdf
Kanban Trojan Horse_(2022).pdfKanban Trojan Horse_(2022).pdf
Kanban Trojan Horse_(2022).pdf
 
Tips n' Tricks - Sprint Review
Tips n' Tricks - Sprint ReviewTips n' Tricks - Sprint Review
Tips n' Tricks - Sprint Review
 
Agile
AgileAgile
Agile
 
Kanban Basics for Beginners
Kanban Basics for BeginnersKanban Basics for Beginners
Kanban Basics for Beginners
 
Definition Of Done
Definition Of DoneDefinition Of Done
Definition Of Done
 
Customer Success Management interview presentation
Customer Success Management interview presentationCustomer Success Management interview presentation
Customer Success Management interview presentation
 
Lean Canvas Workshop
Lean Canvas WorkshopLean Canvas Workshop
Lean Canvas Workshop
 
Agile
Agile Agile
Agile
 
Business Model You
Business Model YouBusiness Model You
Business Model You
 
Agile Metrics
Agile MetricsAgile Metrics
Agile Metrics
 
PopcornFlow: Continuous Evolution Through Ultra-Rapid Experimentation
PopcornFlow: Continuous Evolution Through Ultra-Rapid ExperimentationPopcornFlow: Continuous Evolution Through Ultra-Rapid Experimentation
PopcornFlow: Continuous Evolution Through Ultra-Rapid Experimentation
 
Management fundamentals scrum 101
Management fundamentals scrum 101Management fundamentals scrum 101
Management fundamentals scrum 101
 
Taking Care of your Product by HubSpot PM
Taking Care of your Product by HubSpot PMTaking Care of your Product by HubSpot PM
Taking Care of your Product by HubSpot PM
 
Metodologia scrum actual
Metodologia scrum actualMetodologia scrum actual
Metodologia scrum actual
 
Introduction to Agile Hardware
Introduction to Agile Hardware Introduction to Agile Hardware
Introduction to Agile Hardware
 
Agile Values, Principles and Practices
Agile Values, Principles and PracticesAgile Values, Principles and Practices
Agile Values, Principles and Practices
 
Kanban introduction
Kanban introductionKanban introduction
Kanban introduction
 
Training - Introducing Agile, Lean and Kanban
Training - Introducing Agile, Lean and KanbanTraining - Introducing Agile, Lean and Kanban
Training - Introducing Agile, Lean and Kanban
 

Destacado

Agile Software Development Overview
Agile Software Development OverviewAgile Software Development Overview
Agile Software Development OverviewStewart Rogers
 
Agile Vietnam Five Core Concepts
Agile Vietnam Five Core ConceptsAgile Vietnam Five Core Concepts
Agile Vietnam Five Core ConceptsAgile Vietnam
 
Agile in a Nutshell
Agile in a NutshellAgile in a Nutshell
Agile in a NutshellPortia Tung
 
Kanban six core practices
Kanban six core practicesKanban six core practices
Kanban six core practicesAnders Beskow
 
Kanban 101 - 3 - Kanban Essentials
Kanban 101 - 3 - Kanban EssentialsKanban 101 - 3 - Kanban Essentials
Kanban 101 - 3 - Kanban EssentialsMichael Sahota
 
Agile Explained by LeanDog
Agile Explained by LeanDogAgile Explained by LeanDog
Agile Explained by LeanDogLeanDog
 
Kanban: No Answers, Just Questions
Kanban: No Answers, Just Questions  Kanban: No Answers, Just Questions
Kanban: No Answers, Just Questions Ralf Kruse
 
HowTo Design your kanban board
HowTo Design your kanban boardHowTo Design your kanban board
HowTo Design your kanban boardJo Seibert
 
10 years of kanban - what have we learned
10 years of kanban - what have we learned10 years of kanban - what have we learned
10 years of kanban - what have we learnedDavid Anderson
 
Continuous Delivery
Continuous DeliveryContinuous Delivery
Continuous DeliveryMike McGarr
 
Kanban 101 - An Introduction to Planning with Little's Law
Kanban 101 - An Introduction to Planning with Little's LawKanban 101 - An Introduction to Planning with Little's Law
Kanban 101 - An Introduction to Planning with Little's LawJack Speranza
 
Agile presentation
Agile presentationAgile presentation
Agile presentationinfolock
 
Continuous Delivery
Continuous DeliveryContinuous Delivery
Continuous DeliveryJez Humble
 
Kanban in 4 easy steps
Kanban in 4 easy steps Kanban in 4 easy steps
Kanban in 4 easy steps Shore Labs
 
Agile Retail: Embracing the pace of change
Agile Retail: Embracing the pace of changeAgile Retail: Embracing the pace of change
Agile Retail: Embracing the pace of changeFITCH
 
Kanban boards step by step
Kanban boards step by stepKanban boards step by step
Kanban boards step by stepGiulio Roggero
 

Destacado (20)

Agile Software Development Overview
Agile Software Development OverviewAgile Software Development Overview
Agile Software Development Overview
 
Scrum Concepts
Scrum ConceptsScrum Concepts
Scrum Concepts
 
Introduction to Kanban
Introduction to KanbanIntroduction to Kanban
Introduction to Kanban
 
Agile Vietnam Five Core Concepts
Agile Vietnam Five Core ConceptsAgile Vietnam Five Core Concepts
Agile Vietnam Five Core Concepts
 
Agile in a Nutshell
Agile in a NutshellAgile in a Nutshell
Agile in a Nutshell
 
Kanban six core practices
Kanban six core practicesKanban six core practices
Kanban six core practices
 
Kanban 101
Kanban 101Kanban 101
Kanban 101
 
Kanban 101 - 3 - Kanban Essentials
Kanban 101 - 3 - Kanban EssentialsKanban 101 - 3 - Kanban Essentials
Kanban 101 - 3 - Kanban Essentials
 
Agile Explained by LeanDog
Agile Explained by LeanDogAgile Explained by LeanDog
Agile Explained by LeanDog
 
Agile Methodologies & Key Principles
Agile Methodologies & Key Principles Agile Methodologies & Key Principles
Agile Methodologies & Key Principles
 
Kanban: No Answers, Just Questions
Kanban: No Answers, Just Questions  Kanban: No Answers, Just Questions
Kanban: No Answers, Just Questions
 
HowTo Design your kanban board
HowTo Design your kanban boardHowTo Design your kanban board
HowTo Design your kanban board
 
10 years of kanban - what have we learned
10 years of kanban - what have we learned10 years of kanban - what have we learned
10 years of kanban - what have we learned
 
Continuous Delivery
Continuous DeliveryContinuous Delivery
Continuous Delivery
 
Kanban 101 - An Introduction to Planning with Little's Law
Kanban 101 - An Introduction to Planning with Little's LawKanban 101 - An Introduction to Planning with Little's Law
Kanban 101 - An Introduction to Planning with Little's Law
 
Agile presentation
Agile presentationAgile presentation
Agile presentation
 
Continuous Delivery
Continuous DeliveryContinuous Delivery
Continuous Delivery
 
Kanban in 4 easy steps
Kanban in 4 easy steps Kanban in 4 easy steps
Kanban in 4 easy steps
 
Agile Retail: Embracing the pace of change
Agile Retail: Embracing the pace of changeAgile Retail: Embracing the pace of change
Agile Retail: Embracing the pace of change
 
Kanban boards step by step
Kanban boards step by stepKanban boards step by step
Kanban boards step by step
 

Similar a Agile concepts

Agile project management using scrum
Agile project management using scrumAgile project management using scrum
Agile project management using scrumPrudentialSolutions
 
Agile Development Overview
Agile Development OverviewAgile Development Overview
Agile Development OverviewMark Kovacevich
 
Agile Development Overview
Agile Development OverviewAgile Development Overview
Agile Development Overviewguestb4c770
 
Agile Truths and Misconceptions
Agile Truths and MisconceptionsAgile Truths and Misconceptions
Agile Truths and MisconceptionsRichard Cheng
 
About Agile & PMI Agile Certified Practitioner (PMI-ACP) Overview
About Agile & PMI Agile Certified Practitioner (PMI-ACP) OverviewAbout Agile & PMI Agile Certified Practitioner (PMI-ACP) Overview
About Agile & PMI Agile Certified Practitioner (PMI-ACP) OverviewAleem Khan
 
Introduction to Agile and Lean Software Development
Introduction to Agile and Lean Software DevelopmentIntroduction to Agile and Lean Software Development
Introduction to Agile and Lean Software DevelopmentThanh Nguyen
 
Agile software development development explained
Agile software development development explainedAgile software development development explained
Agile software development development explainedServan Huegen
 
Agile Implementations - Tim FitzGerald - US Assure
Agile Implementations - Tim FitzGerald - US AssureAgile Implementations - Tim FitzGerald - US Assure
Agile Implementations - Tim FitzGerald - US AssureJAX Chamber IT Council
 
pspotrainingbymanoharprasad-230119074638-553afd9f.ppt
pspotrainingbymanoharprasad-230119074638-553afd9f.pptpspotrainingbymanoharprasad-230119074638-553afd9f.ppt
pspotrainingbymanoharprasad-230119074638-553afd9f.pptMouhamed Anouar Fersi
 
Agile Modeling & Scrum Development.pptx
Agile Modeling & Scrum Development.pptxAgile Modeling & Scrum Development.pptx
Agile Modeling & Scrum Development.pptxSamira AlShahrani
 
Agile ncr pramila hitachi consulting_future_coaching
Agile ncr pramila hitachi consulting_future_coachingAgile ncr pramila hitachi consulting_future_coaching
Agile ncr pramila hitachi consulting_future_coachingAgileNCR2016
 
Agile project management 101 (tai lieu tham khao)
Agile project management 101 (tai lieu tham khao)Agile project management 101 (tai lieu tham khao)
Agile project management 101 (tai lieu tham khao)nguyenanvuong2007
 
Scrum-Agile : An Introduction
Scrum-Agile : An IntroductionScrum-Agile : An Introduction
Scrum-Agile : An IntroductionGlobal SQA
 
Agile vs waterfall
Agile vs waterfallAgile vs waterfall
Agile vs waterfallgosain20
 
Essence of agile part 1
Essence of agile part 1Essence of agile part 1
Essence of agile part 1Parul Jain
 
AGILE PROJECT MANAGEMENT NOTES.docx
AGILE PROJECT MANAGEMENT NOTES.docxAGILE PROJECT MANAGEMENT NOTES.docx
AGILE PROJECT MANAGEMENT NOTES.docxVardha Mago
 

Similar a Agile concepts (20)

Agile project management using scrum
Agile project management using scrumAgile project management using scrum
Agile project management using scrum
 
Agile Development Overview
Agile Development OverviewAgile Development Overview
Agile Development Overview
 
Agile Development Overview
Agile Development OverviewAgile Development Overview
Agile Development Overview
 
Agile Truths and Misconceptions
Agile Truths and MisconceptionsAgile Truths and Misconceptions
Agile Truths and Misconceptions
 
About Agile & PMI Agile Certified Practitioner (PMI-ACP) Overview
About Agile & PMI Agile Certified Practitioner (PMI-ACP) OverviewAbout Agile & PMI Agile Certified Practitioner (PMI-ACP) Overview
About Agile & PMI Agile Certified Practitioner (PMI-ACP) Overview
 
Introduction to Agile and Lean Software Development
Introduction to Agile and Lean Software DevelopmentIntroduction to Agile and Lean Software Development
Introduction to Agile and Lean Software Development
 
Agile software development development explained
Agile software development development explainedAgile software development development explained
Agile software development development explained
 
Agile Implementations - Tim FitzGerald - US Assure
Agile Implementations - Tim FitzGerald - US AssureAgile Implementations - Tim FitzGerald - US Assure
Agile Implementations - Tim FitzGerald - US Assure
 
pspotrainingbymanoharprasad-230119074638-553afd9f.ppt
pspotrainingbymanoharprasad-230119074638-553afd9f.pptpspotrainingbymanoharprasad-230119074638-553afd9f.ppt
pspotrainingbymanoharprasad-230119074638-553afd9f.ppt
 
Agile Modeling & Scrum Development.pptx
Agile Modeling & Scrum Development.pptxAgile Modeling & Scrum Development.pptx
Agile Modeling & Scrum Development.pptx
 
PSPO Training by Manohar Prasad.ppt
PSPO Training by Manohar Prasad.pptPSPO Training by Manohar Prasad.ppt
PSPO Training by Manohar Prasad.ppt
 
Agile Development Process
Agile Development ProcessAgile Development Process
Agile Development Process
 
Planning for DevOps
Planning for DevOpsPlanning for DevOps
Planning for DevOps
 
Agile ncr pramila hitachi consulting_future_coaching
Agile ncr pramila hitachi consulting_future_coachingAgile ncr pramila hitachi consulting_future_coaching
Agile ncr pramila hitachi consulting_future_coaching
 
Agile project management 101 (tai lieu tham khao)
Agile project management 101 (tai lieu tham khao)Agile project management 101 (tai lieu tham khao)
Agile project management 101 (tai lieu tham khao)
 
Scrum-Agile : An Introduction
Scrum-Agile : An IntroductionScrum-Agile : An Introduction
Scrum-Agile : An Introduction
 
Agile vs waterfall
Agile vs waterfallAgile vs waterfall
Agile vs waterfall
 
Essence of agile part 1
Essence of agile part 1Essence of agile part 1
Essence of agile part 1
 
AGILE PROJECT MANAGEMENT NOTES.docx
AGILE PROJECT MANAGEMENT NOTES.docxAGILE PROJECT MANAGEMENT NOTES.docx
AGILE PROJECT MANAGEMENT NOTES.docx
 
The 2021 PMP Exam_ Agile.pptx
The 2021 PMP Exam_ Agile.pptxThe 2021 PMP Exam_ Agile.pptx
The 2021 PMP Exam_ Agile.pptx
 

Último

The Importance of Indoor Air Quality (English)
The Importance of Indoor Air Quality (English)The Importance of Indoor Air Quality (English)
The Importance of Indoor Air Quality (English)IES VE
 
Explore the UiPath Community and ways you can benefit on your journey to auto...
Explore the UiPath Community and ways you can benefit on your journey to auto...Explore the UiPath Community and ways you can benefit on your journey to auto...
Explore the UiPath Community and ways you can benefit on your journey to auto...DianaGray10
 
Patch notes explaining DISARM Version 1.4 update
Patch notes explaining DISARM Version 1.4 updatePatch notes explaining DISARM Version 1.4 update
Patch notes explaining DISARM Version 1.4 updateadam112203
 
TrustArc Webinar - How to Live in a Post Third-Party Cookie World
TrustArc Webinar - How to Live in a Post Third-Party Cookie WorldTrustArc Webinar - How to Live in a Post Third-Party Cookie World
TrustArc Webinar - How to Live in a Post Third-Party Cookie WorldTrustArc
 
2024.03.12 Cost drivers of cultivated meat production.pdf
2024.03.12 Cost drivers of cultivated meat production.pdf2024.03.12 Cost drivers of cultivated meat production.pdf
2024.03.12 Cost drivers of cultivated meat production.pdfThe Good Food Institute
 
March Patch Tuesday
March Patch TuesdayMarch Patch Tuesday
March Patch TuesdayIvanti
 
How to release an Open Source Dataweave Library
How to release an Open Source Dataweave LibraryHow to release an Open Source Dataweave Library
How to release an Open Source Dataweave Libraryshyamraj55
 
Webinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - Tech
Webinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - TechWebinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - Tech
Webinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - TechProduct School
 
Design and Modeling for MySQL SCALE 21X Pasadena, CA Mar 2024
Design and Modeling for MySQL SCALE 21X Pasadena, CA Mar 2024Design and Modeling for MySQL SCALE 21X Pasadena, CA Mar 2024
Design and Modeling for MySQL SCALE 21X Pasadena, CA Mar 2024Alkin Tezuysal
 
3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud Data3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud DataEric D. Schabell
 
EMEA What is ThousandEyes? Webinar
EMEA What is ThousandEyes? WebinarEMEA What is ThousandEyes? Webinar
EMEA What is ThousandEyes? WebinarThousandEyes
 
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptxGraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptxNeo4j
 
Flow Control | Block Size | ST Min | First Frame
Flow Control | Block Size | ST Min | First FrameFlow Control | Block Size | ST Min | First Frame
Flow Control | Block Size | ST Min | First FrameKapil Thakar
 
Automation Ops Series: Session 2 - Governance for UiPath projects
Automation Ops Series: Session 2 - Governance for UiPath projectsAutomation Ops Series: Session 2 - Governance for UiPath projects
Automation Ops Series: Session 2 - Governance for UiPath projectsDianaGray10
 
From the origin to the future of Open Source model and business
From the origin to the future of  Open Source model and businessFrom the origin to the future of  Open Source model and business
From the origin to the future of Open Source model and businessFrancesco Corti
 
Introduction - IPLOOK NETWORKS CO., LTD.
Introduction - IPLOOK NETWORKS CO., LTD.Introduction - IPLOOK NETWORKS CO., LTD.
Introduction - IPLOOK NETWORKS CO., LTD.IPLOOK Networks
 
LF Energy Webinar - Unveiling OpenEEMeter 4.0
LF Energy Webinar - Unveiling OpenEEMeter 4.0LF Energy Webinar - Unveiling OpenEEMeter 4.0
LF Energy Webinar - Unveiling OpenEEMeter 4.0DanBrown980551
 
Novo Nordisk's journey in developing an open-source application on Neo4j
Novo Nordisk's journey in developing an open-source application on Neo4jNovo Nordisk's journey in developing an open-source application on Neo4j
Novo Nordisk's journey in developing an open-source application on Neo4jNeo4j
 
Key Trends Shaping the Future of Infrastructure.pdf
Key Trends Shaping the Future of Infrastructure.pdfKey Trends Shaping the Future of Infrastructure.pdf
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
 

Último (20)

The Importance of Indoor Air Quality (English)
The Importance of Indoor Air Quality (English)The Importance of Indoor Air Quality (English)
The Importance of Indoor Air Quality (English)
 
SheDev 2024
SheDev 2024SheDev 2024
SheDev 2024
 
Explore the UiPath Community and ways you can benefit on your journey to auto...
Explore the UiPath Community and ways you can benefit on your journey to auto...Explore the UiPath Community and ways you can benefit on your journey to auto...
Explore the UiPath Community and ways you can benefit on your journey to auto...
 
Patch notes explaining DISARM Version 1.4 update
Patch notes explaining DISARM Version 1.4 updatePatch notes explaining DISARM Version 1.4 update
Patch notes explaining DISARM Version 1.4 update
 
TrustArc Webinar - How to Live in a Post Third-Party Cookie World
TrustArc Webinar - How to Live in a Post Third-Party Cookie WorldTrustArc Webinar - How to Live in a Post Third-Party Cookie World
TrustArc Webinar - How to Live in a Post Third-Party Cookie World
 
2024.03.12 Cost drivers of cultivated meat production.pdf
2024.03.12 Cost drivers of cultivated meat production.pdf2024.03.12 Cost drivers of cultivated meat production.pdf
2024.03.12 Cost drivers of cultivated meat production.pdf
 
March Patch Tuesday
March Patch TuesdayMarch Patch Tuesday
March Patch Tuesday
 
How to release an Open Source Dataweave Library
How to release an Open Source Dataweave LibraryHow to release an Open Source Dataweave Library
How to release an Open Source Dataweave Library
 
Webinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - Tech
Webinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - TechWebinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - Tech
Webinar: The Art of Prioritizing Your Product Roadmap by AWS Sr PM - Tech
 
Design and Modeling for MySQL SCALE 21X Pasadena, CA Mar 2024
Design and Modeling for MySQL SCALE 21X Pasadena, CA Mar 2024Design and Modeling for MySQL SCALE 21X Pasadena, CA Mar 2024
Design and Modeling for MySQL SCALE 21X Pasadena, CA Mar 2024
 
3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud Data3 Pitfalls Everyone Should Avoid with Cloud Data
3 Pitfalls Everyone Should Avoid with Cloud Data
 
EMEA What is ThousandEyes? Webinar
EMEA What is ThousandEyes? WebinarEMEA What is ThousandEyes? Webinar
EMEA What is ThousandEyes? Webinar
 
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptxGraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
 
Flow Control | Block Size | ST Min | First Frame
Flow Control | Block Size | ST Min | First FrameFlow Control | Block Size | ST Min | First Frame
Flow Control | Block Size | ST Min | First Frame
 
Automation Ops Series: Session 2 - Governance for UiPath projects
Automation Ops Series: Session 2 - Governance for UiPath projectsAutomation Ops Series: Session 2 - Governance for UiPath projects
Automation Ops Series: Session 2 - Governance for UiPath projects
 
From the origin to the future of Open Source model and business
From the origin to the future of  Open Source model and businessFrom the origin to the future of  Open Source model and business
From the origin to the future of Open Source model and business
 
Introduction - IPLOOK NETWORKS CO., LTD.
Introduction - IPLOOK NETWORKS CO., LTD.Introduction - IPLOOK NETWORKS CO., LTD.
Introduction - IPLOOK NETWORKS CO., LTD.
 
LF Energy Webinar - Unveiling OpenEEMeter 4.0
LF Energy Webinar - Unveiling OpenEEMeter 4.0LF Energy Webinar - Unveiling OpenEEMeter 4.0
LF Energy Webinar - Unveiling OpenEEMeter 4.0
 
Novo Nordisk's journey in developing an open-source application on Neo4j
Novo Nordisk's journey in developing an open-source application on Neo4jNovo Nordisk's journey in developing an open-source application on Neo4j
Novo Nordisk's journey in developing an open-source application on Neo4j
 
Key Trends Shaping the Future of Infrastructure.pdf
Key Trends Shaping the Future of Infrastructure.pdfKey Trends Shaping the Future of Infrastructure.pdf
Key Trends Shaping the Future of Infrastructure.pdf
 

Agile concepts

  • 1. Agile Concepts Introduction To Agile Practices Joaquim Ferreira
  • 2. About Me Joaquim Ferreira .NET Engineer @ Truphone Email: joaquimf@truphone.com Profile: http://www.linkedin.com/in /joaquimluisdaluzferreira Certified Scrum Master License 000138872 June 2011 to June 2015
  • 3. Agenda 1 2 3 4 5 6 Agile Manifesto Features When Principles Benefits Differences 7 How 8 Practices 9 Scrum 10 Kanban
  • 4. Agile Manifest Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan http://www.agilemanifesto.org/ Kent Beck Mike Beedle Arie van Bennekum Alistair Cockburn Ward Cunningham Martin Fowle James Grenning Jim Highsmith Andrew Hunt Ron Jeffries Jon Kern Brian Marick Robert C. Martin Steve Mellor Ken Schwaber Jeff Sutherland Dave Thomas
  • 5. 12 Principles Our highest priority is to satisfy the customer through early and continuous delivery of valuable software Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale Business people and developers must work together daily throughout the project Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done The most efficient and effective method of conveying information to and within a development team is face-to-face conversation
  • 6. 12 Principles Working software is the primary measure of progress Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely Continuous attention to technical excellence and good design enhances agility Simplicity--the art of maximizing the amount of work not done--is essential The best architectures, requirements, and designs emerge from self-organizing teams At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly
  • 7. Features Iterative 1. Entire work is distributed in incremental units called iteration: 2. Development time of each iteration is small (couple of weeks) and fixed; 3. Every Iteration is a mini increment of the functionality and is build on top of previous iteration; Feature driven 1. More emphasis is on providing the required features in the application; 2. 80/20 principle is applied to decide the 20% features which would be used 80% of the time ( Pareto Principle ); Active Customer involvement 1. There is lot of client involvement and face-to-face interaction; 2. Every iteration is tested and approved by client; 3. The feedback obtained is implemented in subsequent iterations;
  • 8. Features Priority based delivery 1. Features are prioritized depending on customer need, development risk etc.; 2. High priority features are developed first; 3. After every iteration, the project priorities are re-evaluated; Adaptive 1. The applications that are developed can receive new requirements throughout its development; 2. The goal is not to remove the uncertainty in the very beginning; 3. But is to adapt to the changing needs; Empowered Teams 1. The project teams are generally small and have lot of interaction and communication; 2. Since entire team is actively involved, team is empowered to take decisions; 3. No separate team to manage project;
  • 9. Features People Centric 1. Emphasis is on using the adequately skilled people to do the development than on following the processes; 2. The documentation and other non-development activities are minimized and more time is devoted to development and testing; More disciplined 1. So the process involves lot of team and self discipline thus, it requires highly skilled and organized team members; Rapid development 1. Being rapid, everything has to be delivered correctly first time.
  • 10. Features Simplicity 1. Emphasis is on keeping things as simple as possible and being open to change; Fixed Time 1. Each iteration has a fixed time span in which it is delivered;
  • 11. Benefits For the customer 1. Customer is more actively involved, and gets higher priority; 2. He gets to know regular and frequent status of the application; 3. Requirements are accepted after each iteration; 4. Since the methodology emphasizes rapid delivery, time-to- market is less. So the key functionalities can be available to use sooner; 5. Delivery is defined by fixed timescale. So customer is assured of receiving some functionality by a fixed time period; 6. More Testing is done, so better software quality is delivered;
  • 12. Benefits For the project team • Project teams are involved more actively in all the stages; • The teams collaboratively take the decisions and are more empowered; • Development is Incremental, teams can focus on the specific requirements at any given point of time;
  • 13. Benefits For the project team • More emphasis is on developing the application only; • The teams receive frequent feedback as the testing is integrated; so the rework is reduced; • Less time is spent in gathering requirements as all the requirements are not gathered upfront and are implemented as and when they arise;
  • 14. Benefits For the project team • Less cost of development as rework, management, documentation and other non-development work related cost is reduced; • Teams develop applications collaboratively and in cooperative environment; • So less time is required for planning;
  • 15. Differences Requirements Fixed Evolve AgileTraditional Time & People May Change Fixed Costumer Involvement Before, After Throughout Negotiable Estimates Schedule Testing After Work Integrated Feedback After Work During Concentration On Processes; Reviews Finished Work Focus On Plan On Value Stages Requirements, Design, Code, Test, Feedbacks Plan-Do-Check-Adjust
  • 16. When We use Agile when … We have the customer available. We can split the deliver. The requirements are flexible. The team is skilled enough.
  • 17. When Because we will need Organization support Hierarchy ready to empower teams Culture open to changes Focus on add value to the business Infrastructure and team support Preferable the team and the customer should be co-located Hardware support for continuous integration and other practices Highly skilled & flexible people More & frequent testing
  • 18. How Starts with a kick-off meeting 1. Get requirements and / or feedback; 2. Plan & evaluate priorities; 3. Design; 4. Develop; 5. Test; 6. Document what is done; 7. Deliver; 1 2 3 4 5 6 7 Split the functionalities in small delivers and repeat:
  • 19. Practices Scrum Kanban eXtreme Programing ScrumBan Lean Software Development DynamicSystemsDevelopmentMethods Feature Driven Development
  • 20. Scrum Is an agile process that allows us to focus on delivering the highest business value in the shortest time. Allows us to rapidly and repeatedly inspect actual work. The business sets the priorities. The Teams self-organize to determine the best way to deliver the highest priority features. So that in the end of an iteration anyone can see real work and decide to release it as is or continue to enhance it for another iteration. What
  • 21. Scrum No specific engineering practices prescribed Self-organizing teams Product progresses in a series of month-long “sprints” Requirements are captured as items in a list of “product backlog” Characteristics Uses generative rules to create an agile environment for delivering projects
  • 22. Scrum Sprint Requirements Starts with a kick-off meeting • Scrum projects make progress in a series of “sprints”; • Typical duration is 2–4 weeks or a calendar month at most; • Product is designed, coded, and tested during the sprint; • No changes during a sprint; Design Do Test
  • 23. Scrum Rather than doing all of one thing at a time... … Scrum teams do a little of everything all the time Requirements Design Build Test Requirements Design Build Test
  • 26. Scrum Product Owner Starts with a kick-off meeting • Define the features of the product; • Decide on release date and content; • Be responsible for the profitability of the product (R.O.I.); • Prioritize features according to market value; • Adjust features and priority every iteration, as needed; • Accept or reject work results;
  • 27. Scrum Scrum Master Starts with a kick-off meeting • Removes impediments; • Represents management to the project; • Responsible for enacting Scrum values and practices; • Ensure that the team is fully functional and productive; • Enable close cooperation across all roles and functions; • Shield the team from external interferences;
  • 28. Scrum Team Members should be full-time • Teams are self-organizing: • Ideally, no titles but rarely a possibility; • Cross-functional: • Programmers, testers, user experience designers, etc.; • Members should be full-time; • Membership should change only between sprints;
  • 29. Scrum Ceremonies Sprint Planning Sprint Review Sprint Retrospective Daily Scrum
  • 30. Scrum Sprint Planning Meeting Planning Decide how to achieve sprint goal (design) Create Sprint backlog (tasks) from Product Backlog (Features/Stories) Estimate Sprint Backlog in hours.
  • 31. Scrum Daily Scrum Parameters Daily 15-minutes Stand-Up Not for problem solving Just to Inform Only team members and Scrum Master talk Whole world is invited Others may talk if Team allow
  • 32. Scrum Daily Scrum What will you do today ? 1 2 3 Is anything in your way ? What did you do yesterday ? 3Questions
  • 33. Scrum Sprint Review/Demo Members should be full-time • 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;
  • 34. Scrum Sprint Retrospective Members should be full-time • Periodically take a look at what is and is not working; • Done after every sprint; • Whole team participates: • Scrum Master; • Product owner; • Team; • Possibly customers and others;
  • 35. Scrum Sprint Retrospective Whole team gathers and discusses what they’d like to: Start Doing Continue Doing Stop Doing
  • 37. Scrum Product Backlog Members should be full-time • Prioritized list of the functionality to be developed in a product or service; • User stories have emerged as the best and most popular form of product backlog items; • Ideally expressed such that each item has value to the users or customers of the product; • Prioritized by the product owner; • Reprioritized at the start of each sprint;
  • 38. Scrum Sprint Backlog Members should be full-time • The list of tasks identified by the Scrum team during sprint planning; • Its is estimated in Hours; • Individuals sign up for work of their own choosing; • Estimated work remaining is updated daily; • Any team member can add, delete or change the sprint backlog; • Individuals sign up for work of their own choosing;
  • 39. Scrum Product Increment Members should be full-time • In every Sprint is produced one; • Must be of high enough quality to be given to users • Must meet the Scrum Team's current Definition of Done • Each component of it be acceptable to the Product Owner
  • 40. Scrum User Story Members should be full-time • Short, simple description of a feature told from the perspective of the person who desires the new capability; • They typically follow a simple template: • As a <type of user>, I want <some goal> so that <some reason>; • Should contain the conditions of satisfaction for the story be consider done (Acceptance Criteria);
  • 41. Scrum Task Board Members should be full-time • Used to update the changes of state of the tasks during the sprint; • Each story have a row to the board; • Each column represents a state of the work; • The tasks change of state until be finished;
  • 42. Scrum Burn Down Charts Members should be full-time • Show the amount of work remaining either in a sprint or a release: • The Release Burn Down Chart tracks the release remaining work; • The Sprint Burn Down Chart tracks the sprint remaining work; • They determining at a glance whether a sprint or release is on schedule to have all planned work finished by the desired date;
  • 44. Kanban The Kanban is an agile process based on Lean practices and aims to streamline the development process of a product Means Visual Signaling Visibility into the status of the work and how it is proceeding Shows what is happening on the process. Allowing to detect the problems during the process. Gives more precise direction on how to invest the energy into only the most valuable work What
  • 45. Kanban Change the priorities anytime Visualization of the work flow Deliver anytime No need of iterations Characteristics Optimize Existing Processes Introduction of visualization and the limiting of work-in-progress (WIP) will catalyse change with minimal disruption
  • 46. Kanban Core Principles 1 - Visualize the Workflow Represent the work items and the workflow on a card wall or electronic board; 2 - Limit Work-in-Progress (WIP) Set agreed upon limits to how many work items are in progress at a time; 3 - Measure & Manage Flow Track work items to see if they are proceeding at a steady, even pace; 4 - Make Process Policies Explicit Agree upon and post policies about how work will be handled; 5 - Use Models to Evaluate Improvement Oportunities Adapt the process using ideas from Systems Thinking;
  • 47. Kanban Visualize the workflow Todo InProgres BlockedTest Done
  • 48. Members should be full-time Kanban Visualize the workflow • The card wall should reflects the current work process, with the intent to improve it over time. • Draw columns on the board that represent the activities performed, in the order first performed. • The cards themselves could be sticky notes or index cards. • They may represent features, stories or tasks. • Critical information for a card would be title, reference number, and date it entered the system;
  • 49. Kanban Limit Work In Progress ( W.I.P) Todo InProgres BlockedTest Done W.I.P: 10 W.I.P: 5 W.I.P: 4 W.I.P: 3
  • 50. Members should be full-time Kanban Limit Work In Progress ( W.I.P) • A limit on work-in-progress constrains how many work items can be in each workflow step at a time; • When a work item progresses, a slot opens and a new work item can flow into the workflow step; • A key result of a W.I.P. limit is that blocked work “holds up the line”; • No new work can progress on the workflow step until the block is resolved; • The W.I.P. limit provokes the conversations that lead to improvements;
  • 51. Kanban Limit Work In Progress ( W.I.P) How big a limit ? • W.I.P. limits for workflow steps should be set as an average number of items per person; • Limits should be in the range of one to three items per person, pair or team; Agreed upon limits ? • W.I.P. limits should be agreed upon through consensus with up- and downstream stakeholders and senior function management as well as the development team; • Not every step must have a limit;
  • 52. Kanban Limit Work In Progress ( W.I.P) No W.I.P. limit? Care should be taken when establishing any unlimited on workflow steps !!! • Does not introduce bottlenecks; • Cause excessive transaction; • Cause excessive coordination costs when are made;
  • 53. Kanban Measure And Manage Flow Todo InProgres BlockedTest Done W.I.P: 10 W.I.P: 5 W.I.P: 4 W.I.P: 3 Lead Time
  • 54. Kanban Measure And Manage Flow Lead Time Starts when the request is made and ends at delivery; Is what the customer sees; Cycle Time Starts when work begins on the request and ends when the item is ready for delivery; What the team can influence by itself by changing its work process Reaction Time The time until the work begins on the request. Lead Time Reaction To reduce Lead Times one should reduce Cycle Time. But often the time before the work starts is really long. So this wait time should be reduced also. Cycle Time
  • 55. Kanban Explicit Process policies It is often best to post explicit process policies in a public team area such as next to the card wall Workflow Should agree upon policies regarding: W.I.P Limits Approvals Prioritization Other Process Topics
  • 56. Kanban Use models to evaluate improvement • Womack & Jones on Waste Reduction • Eliyahu M. Goldratt on Theory of Constraints • John Seddon and Peter Senge on Systems Thinking • W. Edwards Deming’s System of Profound Knowledge and specifically his work on variability • Taiichi Ohno (Toyota Production System) on muda, muri and mura. Flow Time Gather data on system performance as: W.I.P Useful models to learn and use may include work from:
  • 57. Kanban Vs Scrum Scrum Kanban Fixed-length iterations Required Optional Commitment to a specific amount of work Required - at the personal daily level and at the team level (per sprint) Optional Metrics for planning process improvement Velocity Lead Time Cross-functional teams Required Optional Item size So it can be completed within one sprint No particular Prescribed diagram type Burn down chart No particular Work-in-progress limits Per sprint Per workflow state
  • 58. Kanban Vs Scrum Scrum Kanban Estimations Required Optional Adding new items to ongoing iteration Not allowed Allowed Sharing sprint backlog/ kanban board Within one team With multiple teams or individuals Prescribed team roles Project Owner, Scrum Master, Team Member No Board life-time Reset after each iteration Persistent Prioritization Requires a prioritized product backlog No
  • 59. How do you work? Kanban Scrum • Your work is often interrupted with new, immediate tasks. • You need to be flexible and highly responsive to changes. • You are unable to lock your backlog for a couple of weeks. • Your work more often involves repeatable tasks than new ones. • You do feature development which relies heavily on stakeholders' feedback. • You can run only one project at a time. Kanban Vrs Scrum
  • 60. What is your team type? Kanban Scrum • You have a small, medium or large team of specialists in the same or related fields. • Your team is small and cross-functional. Kanban Vrs Scrum
  • 61. What is the specificity of your organization? Kanban Scrum • Your organization has low maturity. • You have a limited capability of risk taking, change management and decisions making. • You have time to let the culture and performance evolve and improve. • Your organization is highly mature. • You are capable of assessing risk, managing changes, evaluating alternatives and making good quality decisions. • You can only make changes in your company using shock therapy - revolution in your organizational culture and approach to team and project management Kanban Vrs Scrum
  • 62. Sources Manifesto for Agile Software Development http://www.agilemanifesto.org/ http://www.mountaingoatsoftware.com/ Portions of this presentation are based on the next sources: http://www.indicthreads.com/1439/quick- introduction-to-agile-software-development/ http://refcardz.dzone.com/refcardz/ge tting-started-kanban