SlideShare una empresa de Scribd logo
1 de 38
Descargar para leer sin conexión
Introducing Agile methodologies
Scrum, XP and Kanban
Kanban Board
www.torak.com
About Dimitri Ponomareff
Dimitri Ponomareff (www.linkedin.com/in/dimka5) is a Coach.
Whether it's a sports team, software products or entire
organizations, Dimitri has that ability to relate and energize
people. He is consistently recognized as a very passionate and
successful change agent, with an overwhelming capacity to
motivate and mobilize teams on their path to continuous
improvements. He is a master facilitator, as well as a captivating
speaker with consistent, positive feedback regarding his ability to
engage an audience.
www.torak.com
As a certified Coach, Project Manager and Facilitator of "The 7 Habits of Highly Effective
People", Dimitri brings a full spectrum of knowledge in his delivery of methodologies. Through
teaching by example, he is able to build teams of people who understand where to focus their work
to generate the most value.
He has coached and provided tailor-made services and training for a multitude of organizations.
The short list includes, American Express, Charles Schwab, Bank of America, Morgan
Stanley, Choice Hotels International, JDA Software, LifeLock, First Solar, Mayo Clinic and
Phoenix Children's Hospital. Dimitri enjoys his work, and does everything to ensure he shares his
knowledge with others who seek it.
Agile Overview
● Agile Manifesto
● Lean software development principles
● Flavors of Agile and timeline
● Prescriptive vs. Adaptive
● Sequential vs. Overlapping
● Envision / Explore cycles
● PDCA
www.torak.com
The Agile Manifesto
We are uncovering better ways of developing
software by doing it and helping others do it.
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
Source: www.agilemanifesto.org
www.torak.com
12 Principles of Agile Software
1. Our highest priority is to satisfy the
customer through early and continuous delivery
of valuable software.
2. Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
3. Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
4. Business people and developers must work
together daily throughout the project.
5. Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.
6. The most efficient and effective method
of conveying information to and within a
development team is face-to-face conversation.
7. Working software is the primary measure of
progress.
8. Agile processes promote sustainable
development. The sponsors, developers, and
users should be able to maintain a constant
pace indefinitely.
9. Continuous attention to technical
excellence and good design enhances agility.
10. Simplicity the art of maximizing the
amount of work not done--is essential.
11. The best architectures, requirements, and
designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on
how to become more effective, then tunes and
adjusts its behavior accordingly.
Source: www.agilemanifesto.org
www.torak.com
Lean software development principles
1. Eliminate waste
2. Amplify learning
3. Decide as late as possible
4. Deliver as fast as possible
5. Empower the team
6. Build integrity in
7. See the whole
www.torak.com
Flavors of Agile
Dynamic System Development Method (DSDM)
Dane Faulkner
Extreme Programming (XP)
Kent Beck
Feature Driven Development (FDD)
Jeff DeLuca
Scrum
Ken Schwaber
Lean Software Development
Mary Poppendieck and Tom Poppendieck
Adaptive Software Development (ASD)
Jim Highsmith
Crystal Clear
Allistair Cockburn
Behavior driven development (BDD)
www.torak.com
Agile Timeline
1970 1980 1990 2000
Waterfall
Spiral, RAD, RUP
Scrum, XP
Predictive: phases, documentation-centric, functional handoffs, get it right the first time
Iterative: process framework, phases, tool driven, artifact heavy
Adaptive: iterative, self-organizing teams, value driven, transparent
www.torak.com
Prescriptive vs. Adaptive
120+
13 9 6 0
RUP XP Scrum Kanban Do
Whatever
More
Prescriptive
More
Adaptive
(roles, activities & artifacts)
Source: Kanban and Scrum, making the most of both. Henrik Kniberg & Mattias Skarin
www.torak.com
Prescriptive vs. Adaptive
Waterfall
Predictive Process
The plan creates cost and
schedule estimates
Constraints
Estimates
Scope
(requirements)
Cost Time
Plan
Driven
Agile
Adaptive Process
The vision creates feature
estimates
Cost Time
Scope
(features)
Value/Vision
Driven
www.torak.com
Sequential vs. Overlapping development
Requirements Design Code Test
Source: “The New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986.
Rather than
doing all of one
thing at a time...
Agile teams do a
little of everything
all the time.
www.torak.com
Software development process
Time
Analysis
Design
Code
Test
Agile
Analysis
Design
Code
Test
Time
Traditional
50% complete?
0% usable
25% complete
100% usable
www.torak.com
Envision / Explore cycles
Constant User
Interactions
www.torak.com
PDCA - Plan, Do, Check, Act
ACT
PLAN DO
PDCA
Cycle
CHECK
Continuous Improvements
www.torak.com
Agile Methodologies
●Scrum
●XP - Extreme Programming
●Kanban
www.torak.com
Origins ...
Scrum
● 1986, Hirotaka Takeuchi and Ikujiro Nonaka described a new approach to commercial product development "holistic
or rugby approach"
● 1991, DeGrace and Stahl first referred to this as the scrum approach. Ken Schwaber used such an approach at his
company, Advanced Development Methods, and Jeff Sutherland, with John Scumniotales and Jeff McKenna,
developed a similar approach at Easel Corporation, and were the first to refer to it using the single word Scrum.
● 1995, Sutherland and Schwaber jointly presented a paper describing the Scrum methodology
● 2001, Ken Schwaber teamed up with Mike Beedle to describe the method in the book "Agile Software Development
with Scrum".
XP - Extreme Programming
● created by Kent Beck during his work on the Chrysler Comprehensive Compensation System (C3) payroll project,
who worked with Don Wells, Ron Jeffries, Martin Fowler and Chet Hendrickson
● takes software development "best practices" to extreme levels
Kanban for development
● Japanese for "signboard"
● Taiichi Onho developed 1940/1950 kanbans to control production between processes and to implement Just n Time
(JIT) manufacturing at Toyota manufacturing plants in Japan.
● 2003, David J. Anderson formulated the Kanban Method as an approach to incremental, evolutionary process and
systems change for organizations
www.torak.com
Scrum
Product
Backlog
(prioritized)
Sprint
Backlog
Sprint Planning
Sprint
Retrospective
Sprint Review
Daily Scrum
Product
Increment
Sprint
Task
Board
Sprint
Burndown
Scrum Master
Product Owner
Team
Stakeholders
Users
Roles
www.torak.com
Scrum
● focus on delivering the highest business value in the shortest time
● allows to rapidly and repeatedly inspect actual working software
● the business sets the priorities & teams self-organize to determine the
best way to deliver the work
● every sprint (1-4 weeks) anyone can see real working software and decide
to release it as is, or continue to enhance it for another sprint
www.torak.com
Scrum
1. Roles
● Product Owner
● Scrum Master
● Development Team
2. Ceremonies
● Daily Scrum
● Sprint Planning
● Sprint Review
● Sprint Retrospective
3. Artifacts
● Product backlog, sprint
backlog, user stories
● Burn-down chart
● Work increment
www.torak.com
XP - eXtreme Programming
● improve software quality and
responsiveness to changing
customer requirements
● frequent releases in short
development cycles
● improve productivity and
regular checkpoints with the
customer
● paired programming
www.torak.com
XP - eXtreme Programming
www.torak.com
www.torak.com
Kanban - 3 basic principles
1. Start with what you do now
● Kanban does not prescribe a specific set of roles
or process steps
2. Agree to pursue incremental, evolutionary change
● continuous small changes that stick vs. sweeping changes that fail due to resistance
and fear in the organization
3. Respect the current process, roles, responsibilities &
titles
● gain support, reduce fear/resistance to change and experience the benefits as a team
Kanban Board
www.torak.com
Kanban - 5 Core Properties
1. Visualize the workflow
● Kanban literally means "signboard" or "billboard"
2. Limit Work In Process (WIP)
● use a pull system - establish and respect your ideal
capacity
3. Manage Flow
● monitor, measure and report the flow of work through each state
4. Make Process Policies Explicit
● describe the process accurately in order to improve it
5. Improve Collaboratively
● using models & the scientific method (empirical) to implement continuous, incremental and
evolutionary changes
Kanban Board
www.torak.com
Kanban
source: http://finance.groups.yahoo.com/group/kanbandev/
www.torak.com
Kanban: Start 1
a
b
to do in process done
Start with a simple task board with 3 columns: to do, in process and done.
Each card represent a work item in the current scope. Names can be associated with
the cards.
The key is to setup an easy way to visualize the work, and create an area for social
interactions.
c
www.torak.com
Kanban: Start 2
a
b
to do in process done
Start with a simple task board with 3 columns: to do, in process and done.
Each card represent a work item in the current scope. Names can be associated with
the cards.
The key is to setup an easy way to visualize the work, and create an area for social
interactions.
b
a
to do in process done
A problem with such a simplistic board, is the lack of rules and the concept of time-
boxing.
A typical problem is accumulating too much work in progress (WIP).
Kanban is more than just adding work items on a board, it's also applying a PULL
process.
a
b a
b
a
c
c
c
a
c
www.torak.com
Kanban: Start 3
a
b
to do in process done
Start with a simple task board with 3 columns: to do, in process and done.
Each card represent a work item in the current scope. Names can be associated with
the cards.
The key is to setup an easy way to visualize the work, and create an area for social
interactions.
b
a
to do in process done
A problem with such a simplistic board, is the lack of rules and the concept of time-
boxing.
A typical problem is accumulating too much work in progress (WIP).
Kanban is more than just adding work items on a board, it's also applying a PULL
process.
a
b a
b
a
c
c
c
a
to do in process done
To truly embrace Kanban, we must regulate the volume of cards on the board. This
can easily be accomplished by identifying clear thresholds associated to better
defined stages of work (columns).
Another improvement is to set a multi-tasking limit per user (2) and using late binding
of tasks to owners. Note that not all team members must have 2 tasks with their
names, this is a maximum of 2.
b
c
a
ready
2 5
a
c
c
www.torak.com
Kanban: Mechanics
to do in process done
b
c
a
ready
2 5
a
c to do in process done
b
c
a
ready
2 5
a
c
to do in process done
b
c
a
ready
2 5
a
c
a
1. Team member A completes a card
and moves it to the "done" column.
2. Team member A pulls a new card
from the "ready" column and starts
working on it by placing it in the "in
process" column.
3. The team responds to the pull
event and selects the next priority
card by moving it to the "ready"
column.
www.torak.com
Scrumban: Flow
to do in process done
b
c
ready
2 5
a
c
b
to do specify done
b
c
ready
2 3
a
c
b
execute
2
Now that we have established our team capacity and we
have a pull system, we can streamline the ideal flow.
www.torak.com
Kanban: Flow
to do in process done
b
c
ready
2 5
a
c
b
to do specify done
b
c
ready
2 3
a
c
b
execute
2
Now that we have established our team capacity and we
have a pull system, we can streamline the ideal flow.
a
backlog specify done
b
ready
2 3
a
c
b
complete execute
3
c
8
www.torak.com
Highlights from each ...
Scrum
● ceremonies (daily scrum, review and retrospective)
● time-boxed work using sprints
● burn-down charts
XP - eXtreme Programming
● best practices
○ coding (standards, collective code ownership, simple design, metaphor)
○ continuous integration
○ test driven development (unit tests, automated testing, acceptance testing)
■ When a Bug is found tests are created before the bug is addressed (a bug is not
an error in logic, it is a test you forgot to write)
Kanban for development
● visual board
● pull system
● JIT backlog/work
● continuous flow
www.torak.com
Visualizing the work
www.torak.com
Scaled Agile Framework - Big Picture
www.torak.com
Resources
● http://www.extremeprogramming.org/
● http://xprogramming.com
● http://finance.groups.yahoo.com/group/kanbandev/
● Takeuchi, Hirotaka; Nonaka, Ikujiro. "The New New Product Development
Game". Harvard Business Review.
● DeGrace, Peter; Stahl, Leslie Hulet (1990-10-01). Wicked problems,
righteous solutions. Prentice Hall.
● Kanban: Successful Evolutionary Change for Your Technology Business by
David J. Anderson
● Agile Software Development with Scrum by Ken Schwaber and Mike
Beedle
● Mary Poppendieck, Tom Poppendieck (2003), "Lean Software
Development: An Agile Toolkit"
www.torak.com
Agile Coaching, Staffing and Training.
Learn more at www.torak.com
Learn more at www.AgileTestingFramework.com
Thank You
www.torak.com
This presentation was inspired by the work of many people and we have done our very best to
attribute all authors of texts and images, and recognize any copyrights. If you think that
anything in this presentation should be changed, added or removed, please contact us.
http://creativecommons.org/licenses/by-nc-nd/3.0/
www.torak.com

Más contenido relacionado

La actualidad más candente

Agile Scrum Presentation-Detailed
Agile Scrum Presentation-DetailedAgile Scrum Presentation-Detailed
Agile Scrum Presentation-Detailed
Prashaanth T R
 

La actualidad más candente (20)

Agile Methodology and Tools
Agile Methodology and ToolsAgile Methodology and Tools
Agile Methodology and Tools
 
Agile Scrum Presentation-Detailed
Agile Scrum Presentation-DetailedAgile Scrum Presentation-Detailed
Agile Scrum Presentation-Detailed
 
12 Agile Principles in Pictures
12 Agile Principles in Pictures12 Agile Principles in Pictures
12 Agile Principles in Pictures
 
Scrum 101
Scrum 101Scrum 101
Scrum 101
 
Scrum Process
Scrum ProcessScrum Process
Scrum Process
 
Agile - Scrum Presentation
Agile - Scrum PresentationAgile - Scrum Presentation
Agile - Scrum Presentation
 
Agile project management
Agile project managementAgile project management
Agile project management
 
Agile-overview: Agile Manifesto, Agile principles and Agile Methodologies
Agile-overview: Agile Manifesto, Agile principles and Agile MethodologiesAgile-overview: Agile Manifesto, Agile principles and Agile Methodologies
Agile-overview: Agile Manifesto, Agile principles and Agile Methodologies
 
Agile Methodology in Software Development
Agile Methodology in Software DevelopmentAgile Methodology in Software Development
Agile Methodology in Software Development
 
Agile Process Introduction
Agile Process IntroductionAgile Process Introduction
Agile Process Introduction
 
What Is A Sprint Planning Meeting
What Is A Sprint Planning MeetingWhat Is A Sprint Planning Meeting
What Is A Sprint Planning Meeting
 
Agile Scrum Methodology
Agile Scrum MethodologyAgile Scrum Methodology
Agile Scrum Methodology
 
Agile Methodology
Agile MethodologyAgile Methodology
Agile Methodology
 
2017 Scrum by Picture
2017 Scrum by Picture2017 Scrum by Picture
2017 Scrum by Picture
 
Agile Kanban
Agile KanbanAgile Kanban
Agile Kanban
 
The Values and Principles of Agile Software Development
The Values and Principles of Agile Software DevelopmentThe Values and Principles of Agile Software Development
The Values and Principles of Agile Software Development
 
Agile Overview
Agile OverviewAgile Overview
Agile Overview
 
Scrum
ScrumScrum
Scrum
 
Introduction to LeSS - Large Scale Scrum
Introduction to LeSS - Large Scale ScrumIntroduction to LeSS - Large Scale Scrum
Introduction to LeSS - Large Scale Scrum
 
What Is Agile Scrum
What Is Agile ScrumWhat Is Agile Scrum
What Is Agile Scrum
 

Destacado

Data Analytics Practice at Paxcel
Data Analytics Practice at PaxcelData Analytics Practice at Paxcel
Data Analytics Practice at Paxcel
Pushpinder Singh
 
Agile stories, estimating and planning
Agile stories, estimating and planningAgile stories, estimating and planning
Agile stories, estimating and planning
Dimitri Ponomareff
 

Destacado (17)

The 5 Levels Planning in Agile
The 5 Levels Planning in AgileThe 5 Levels Planning in Agile
The 5 Levels Planning in Agile
 
Agile Testing Framework - The Art of Automated Testing
Agile Testing Framework - The Art of Automated TestingAgile Testing Framework - The Art of Automated Testing
Agile Testing Framework - The Art of Automated Testing
 
Why Does Agile Work?
Why Does Agile Work?Why Does Agile Work?
Why Does Agile Work?
 
Apache Hivemall @ Apache BigData '17, Miami
Apache Hivemall @ Apache BigData '17, MiamiApache Hivemall @ Apache BigData '17, Miami
Apache Hivemall @ Apache BigData '17, Miami
 
Data Analytics Practice at Paxcel
Data Analytics Practice at PaxcelData Analytics Practice at Paxcel
Data Analytics Practice at Paxcel
 
SQL, NoSQL, BigData in Data Architecture
SQL, NoSQL, BigData in Data ArchitectureSQL, NoSQL, BigData in Data Architecture
SQL, NoSQL, BigData in Data Architecture
 
Hadoop bigdata overview
Hadoop bigdata overviewHadoop bigdata overview
Hadoop bigdata overview
 
Bio bigdata
Bio bigdata Bio bigdata
Bio bigdata
 
Jubatus: Realtime deep analytics for BIgData@Rakuten Technology Conference 2012
Jubatus: Realtime deep analytics for BIgData@Rakuten Technology Conference 2012Jubatus: Realtime deep analytics for BIgData@Rakuten Technology Conference 2012
Jubatus: Realtime deep analytics for BIgData@Rakuten Technology Conference 2012
 
Understanding and Working with Agile Culture - PMI-SOC
Understanding and Working with Agile Culture - PMI-SOCUnderstanding and Working with Agile Culture - PMI-SOC
Understanding and Working with Agile Culture - PMI-SOC
 
Agile stories, estimating and planning
Agile stories, estimating and planningAgile stories, estimating and planning
Agile stories, estimating and planning
 
Stories, Backlog & Mapping
Stories, Backlog & MappingStories, Backlog & Mapping
Stories, Backlog & Mapping
 
Faster Cheaper Better the Agile / Lean Way
Faster Cheaper Better the Agile / Lean WayFaster Cheaper Better the Agile / Lean Way
Faster Cheaper Better the Agile / Lean Way
 
Planning, scaling and flowing within your agile organization
Planning, scaling and flowing within your agile organizationPlanning, scaling and flowing within your agile organization
Planning, scaling and flowing within your agile organization
 
Leading the agile organization
Leading the agile organizationLeading the agile organization
Leading the agile organization
 
BDaas- BigData as a service
BDaas- BigData as a service  BDaas- BigData as a service
BDaas- BigData as a service
 
Agile Project Management - An introduction to Agile and the new PMI-ACP
Agile Project Management - An introduction to Agile and the new PMI-ACPAgile Project Management - An introduction to Agile and the new PMI-ACP
Agile Project Management - An introduction to Agile and the new PMI-ACP
 

Similar a Introducing Agile Scrum XP and Kanban

Agile Truths and Misconceptions
Agile Truths and MisconceptionsAgile Truths and Misconceptions
Agile Truths and Misconceptions
Richard Cheng
 
Agile and its impact to Project Management 022218.pptx
Agile and its impact to Project Management 022218.pptxAgile and its impact to Project Management 022218.pptx
Agile and its impact to Project Management 022218.pptx
PerumalPitchandi
 
HOT TOPIC REPORT DIVYA
HOT TOPIC REPORT DIVYAHOT TOPIC REPORT DIVYA
HOT TOPIC REPORT DIVYA
Divya Tadi
 
Flavours of agile software engineering
Flavours of agile software engineeringFlavours of agile software engineering
Flavours of agile software engineering
Zeeshan Masood S
 
Business Need And Current Situation Essay
Business Need And Current Situation EssayBusiness Need And Current Situation Essay
Business Need And Current Situation Essay
Jill Lyons
 

Similar a Introducing Agile Scrum XP and Kanban (20)

SE18_Lec 05_Agile Software Development
SE18_Lec 05_Agile Software DevelopmentSE18_Lec 05_Agile Software Development
SE18_Lec 05_Agile Software Development
 
Scrum 18 months later
Scrum 18 months laterScrum 18 months later
Scrum 18 months later
 
SE_Lec 04_Agile Software Development
SE_Lec 04_Agile Software DevelopmentSE_Lec 04_Agile Software Development
SE_Lec 04_Agile Software Development
 
Agile Software Development Overview
Agile Software Development OverviewAgile Software Development Overview
Agile Software Development Overview
 
Agile Truths and Misconceptions
Agile Truths and MisconceptionsAgile Truths and Misconceptions
Agile Truths and Misconceptions
 
Agile and its impact to Project Management 022218.pptx
Agile and its impact to Project Management 022218.pptxAgile and its impact to Project Management 022218.pptx
Agile and its impact to Project Management 022218.pptx
 
HOT TOPIC REPORT DIVYA
HOT TOPIC REPORT DIVYAHOT TOPIC REPORT DIVYA
HOT TOPIC REPORT DIVYA
 
Agile Project Management training by manohar prasad
Agile Project Management training by manohar prasadAgile Project Management training by manohar prasad
Agile Project Management training by manohar prasad
 
Agile Fundamentals for Project Managers.pdf
Agile Fundamentals for Project Managers.pdfAgile Fundamentals for Project Managers.pdf
Agile Fundamentals for Project Managers.pdf
 
Introduction to Agile & scrum
Introduction to Agile & scrumIntroduction to Agile & scrum
Introduction to Agile & scrum
 
Presentation: "Agile methodologies for Project Management - SCRUM" by Varty K...
Presentation: "Agile methodologies for Project Management - SCRUM" by Varty K...Presentation: "Agile methodologies for Project Management - SCRUM" by Varty K...
Presentation: "Agile methodologies for Project Management - SCRUM" by Varty K...
 
Flavours of agile software engineering
Flavours of agile software engineeringFlavours of agile software engineering
Flavours of agile software engineering
 
Flavours of agile software engineering
Flavours of agile software engineeringFlavours of agile software engineering
Flavours of agile software engineering
 
Business Need And Current Situation Essay
Business Need And Current Situation EssayBusiness Need And Current Situation Essay
Business Need And Current Situation Essay
 
May-MH-TrailblazerEvent
May-MH-TrailblazerEventMay-MH-TrailblazerEvent
May-MH-TrailblazerEvent
 
Professional Project Manager Should Be Proficient in Agile
Professional Project Manager Should Be Proficient in AgileProfessional Project Manager Should Be Proficient in Agile
Professional Project Manager Should Be Proficient in Agile
 
Introduction to Agile
Introduction to AgileIntroduction to Agile
Introduction to Agile
 
Product Management Primer
Product Management PrimerProduct Management Primer
Product Management Primer
 
A littlebook about agile
A littlebook about agileA littlebook about agile
A littlebook about agile
 
CampusSDN2017 - Jawdat: Product Management and Agile Development
CampusSDN2017 - Jawdat: Product Management and Agile DevelopmentCampusSDN2017 - Jawdat: Product Management and Agile Development
CampusSDN2017 - Jawdat: Product Management and Agile Development
 

Último

Ahmedabad Escort Service Ahmedabad Call Girl 0000000000
Ahmedabad Escort Service Ahmedabad Call Girl 0000000000Ahmedabad Escort Service Ahmedabad Call Girl 0000000000
Ahmedabad Escort Service Ahmedabad Call Girl 0000000000
mountabuangels4u
 
💕📲09602870969💓Girl Escort Services Udaipur Call Girls in Chittorgarh Haldighati
💕📲09602870969💓Girl Escort Services Udaipur Call Girls in Chittorgarh Haldighati💕📲09602870969💓Girl Escort Services Udaipur Call Girls in Chittorgarh Haldighati
💕📲09602870969💓Girl Escort Services Udaipur Call Girls in Chittorgarh Haldighati
Apsara Of India
 
sample sample sample sample sample sample
sample sample sample sample sample samplesample sample sample sample sample sample
sample sample sample sample sample sample
Casey Keith
 
sample sample sample sample sample sample
sample sample sample sample sample samplesample sample sample sample sample sample
sample sample sample sample sample sample
Casey Keith
 
🔥HOT🔥📲9602870969🔥Prostitute Service in Udaipur Call Girls in City Palace Lake...
🔥HOT🔥📲9602870969🔥Prostitute Service in Udaipur Call Girls in City Palace Lake...🔥HOT🔥📲9602870969🔥Prostitute Service in Udaipur Call Girls in City Palace Lake...
🔥HOT🔥📲9602870969🔥Prostitute Service in Udaipur Call Girls in City Palace Lake...
Apsara Of India
 

Último (20)

Call Girls Jaisalmer Just Call 8617370543 Top Class Call Girl Service Available
Call Girls Jaisalmer Just Call 8617370543 Top Class Call Girl Service AvailableCall Girls Jaisalmer Just Call 8617370543 Top Class Call Girl Service Available
Call Girls Jaisalmer Just Call 8617370543 Top Class Call Girl Service Available
 
❤Personal Contact Number Varanasi Call Girls 8617697112💦✅.
❤Personal Contact Number Varanasi Call Girls 8617697112💦✅.❤Personal Contact Number Varanasi Call Girls 8617697112💦✅.
❤Personal Contact Number Varanasi Call Girls 8617697112💦✅.
 
Hire 💕 8617697112 Champawat Call Girls Service Call Girls Agency
Hire 💕 8617697112 Champawat Call Girls Service Call Girls AgencyHire 💕 8617697112 Champawat Call Girls Service Call Girls Agency
Hire 💕 8617697112 Champawat Call Girls Service Call Girls Agency
 
Ahmedabad Escort Service Ahmedabad Call Girl 0000000000
Ahmedabad Escort Service Ahmedabad Call Girl 0000000000Ahmedabad Escort Service Ahmedabad Call Girl 0000000000
Ahmedabad Escort Service Ahmedabad Call Girl 0000000000
 
Genuine 8250077686 Hot and Beautiful 💕 Bhavnagar Escorts call Girls
Genuine 8250077686 Hot and Beautiful 💕 Bhavnagar Escorts call GirlsGenuine 8250077686 Hot and Beautiful 💕 Bhavnagar Escorts call Girls
Genuine 8250077686 Hot and Beautiful 💕 Bhavnagar Escorts call Girls
 
💕📲09602870969💓Girl Escort Services Udaipur Call Girls in Chittorgarh Haldighati
💕📲09602870969💓Girl Escort Services Udaipur Call Girls in Chittorgarh Haldighati💕📲09602870969💓Girl Escort Services Udaipur Call Girls in Chittorgarh Haldighati
💕📲09602870969💓Girl Escort Services Udaipur Call Girls in Chittorgarh Haldighati
 
Andheri East Call Girls 🥰 8617370543 Service Offer VIP Hot Model
Andheri East Call Girls 🥰 8617370543 Service Offer VIP Hot ModelAndheri East Call Girls 🥰 8617370543 Service Offer VIP Hot Model
Andheri East Call Girls 🥰 8617370543 Service Offer VIP Hot Model
 
Genuine 8250077686 Hot and Beautiful 💕 Chennai Escorts call Girls
Genuine 8250077686 Hot and Beautiful 💕 Chennai Escorts call GirlsGenuine 8250077686 Hot and Beautiful 💕 Chennai Escorts call Girls
Genuine 8250077686 Hot and Beautiful 💕 Chennai Escorts call Girls
 
Ooty call girls 📞 8617697112 At Low Cost Cash Payment Booking
Ooty call girls 📞 8617697112 At Low Cost Cash Payment BookingOoty call girls 📞 8617697112 At Low Cost Cash Payment Booking
Ooty call girls 📞 8617697112 At Low Cost Cash Payment Booking
 
Jhargram call girls 📞 8617697112 At Low Cost Cash Payment Booking
Jhargram call girls 📞 8617697112 At Low Cost Cash Payment BookingJhargram call girls 📞 8617697112 At Low Cost Cash Payment Booking
Jhargram call girls 📞 8617697112 At Low Cost Cash Payment Booking
 
sample sample sample sample sample sample
sample sample sample sample sample samplesample sample sample sample sample sample
sample sample sample sample sample sample
 
WhatsApp Chat: 📞 8617697112 Hire Call Girls Cooch Behar For a Sensual Sex Exp...
WhatsApp Chat: 📞 8617697112 Hire Call Girls Cooch Behar For a Sensual Sex Exp...WhatsApp Chat: 📞 8617697112 Hire Call Girls Cooch Behar For a Sensual Sex Exp...
WhatsApp Chat: 📞 8617697112 Hire Call Girls Cooch Behar For a Sensual Sex Exp...
 
sample sample sample sample sample sample
sample sample sample sample sample samplesample sample sample sample sample sample
sample sample sample sample sample sample
 
Andheri Call Girls 🥰 8617370543 Service Offer VIP Hot Model
Andheri Call Girls 🥰 8617370543 Service Offer VIP Hot ModelAndheri Call Girls 🥰 8617370543 Service Offer VIP Hot Model
Andheri Call Girls 🥰 8617370543 Service Offer VIP Hot Model
 
Hire 💕 8617697112 Reckong Peo Call Girls Service Call Girls Agency
Hire 💕 8617697112 Reckong Peo Call Girls Service Call Girls AgencyHire 💕 8617697112 Reckong Peo Call Girls Service Call Girls Agency
Hire 💕 8617697112 Reckong Peo Call Girls Service Call Girls Agency
 
Siliguri Call Girls 8250077686 Service Offer VIP Hot Model
Siliguri Call Girls 8250077686 Service Offer VIP Hot ModelSiliguri Call Girls 8250077686 Service Offer VIP Hot Model
Siliguri Call Girls 8250077686 Service Offer VIP Hot Model
 
Mathura Call Girls 8250077686 Service Offer VIP Hot Model
Mathura Call Girls 8250077686 Service Offer VIP Hot ModelMathura Call Girls 8250077686 Service Offer VIP Hot Model
Mathura Call Girls 8250077686 Service Offer VIP Hot Model
 
🔥HOT🔥📲9602870969🔥Prostitute Service in Udaipur Call Girls in City Palace Lake...
🔥HOT🔥📲9602870969🔥Prostitute Service in Udaipur Call Girls in City Palace Lake...🔥HOT🔥📲9602870969🔥Prostitute Service in Udaipur Call Girls in City Palace Lake...
🔥HOT🔥📲9602870969🔥Prostitute Service in Udaipur Call Girls in City Palace Lake...
 
WhatsApp Chat: 📞 8617697112 Suri Call Girls available for hotel room package
WhatsApp Chat: 📞 8617697112 Suri Call Girls available for hotel room packageWhatsApp Chat: 📞 8617697112 Suri Call Girls available for hotel room package
WhatsApp Chat: 📞 8617697112 Suri Call Girls available for hotel room package
 
Hire 💕 8617697112 Chamba Call Girls Service Call Girls Agency
Hire 💕 8617697112 Chamba Call Girls Service Call Girls AgencyHire 💕 8617697112 Chamba Call Girls Service Call Girls Agency
Hire 💕 8617697112 Chamba Call Girls Service Call Girls Agency
 

Introducing Agile Scrum XP and Kanban

  • 1. Introducing Agile methodologies Scrum, XP and Kanban Kanban Board www.torak.com
  • 2. About Dimitri Ponomareff Dimitri Ponomareff (www.linkedin.com/in/dimka5) is a Coach. Whether it's a sports team, software products or entire organizations, Dimitri has that ability to relate and energize people. He is consistently recognized as a very passionate and successful change agent, with an overwhelming capacity to motivate and mobilize teams on their path to continuous improvements. He is a master facilitator, as well as a captivating speaker with consistent, positive feedback regarding his ability to engage an audience. www.torak.com As a certified Coach, Project Manager and Facilitator of "The 7 Habits of Highly Effective People", Dimitri brings a full spectrum of knowledge in his delivery of methodologies. Through teaching by example, he is able to build teams of people who understand where to focus their work to generate the most value. He has coached and provided tailor-made services and training for a multitude of organizations. The short list includes, American Express, Charles Schwab, Bank of America, Morgan Stanley, Choice Hotels International, JDA Software, LifeLock, First Solar, Mayo Clinic and Phoenix Children's Hospital. Dimitri enjoys his work, and does everything to ensure he shares his knowledge with others who seek it.
  • 3. Agile Overview ● Agile Manifesto ● Lean software development principles ● Flavors of Agile and timeline ● Prescriptive vs. Adaptive ● Sequential vs. Overlapping ● Envision / Explore cycles ● PDCA www.torak.com
  • 4. The Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Source: www.agilemanifesto.org www.torak.com
  • 5. 12 Principles of Agile Software 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4. Business people and developers must work together daily throughout the project. 5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 7. Working software is the primary measure of progress. 8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9. Continuous attention to technical excellence and good design enhances agility. 10. Simplicity the art of maximizing the amount of work not done--is essential. 11. The best architectures, requirements, and designs emerge from self-organizing teams. 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Source: www.agilemanifesto.org www.torak.com
  • 6. Lean software development principles 1. Eliminate waste 2. Amplify learning 3. Decide as late as possible 4. Deliver as fast as possible 5. Empower the team 6. Build integrity in 7. See the whole www.torak.com
  • 7. Flavors of Agile Dynamic System Development Method (DSDM) Dane Faulkner Extreme Programming (XP) Kent Beck Feature Driven Development (FDD) Jeff DeLuca Scrum Ken Schwaber Lean Software Development Mary Poppendieck and Tom Poppendieck Adaptive Software Development (ASD) Jim Highsmith Crystal Clear Allistair Cockburn Behavior driven development (BDD) www.torak.com
  • 8. Agile Timeline 1970 1980 1990 2000 Waterfall Spiral, RAD, RUP Scrum, XP Predictive: phases, documentation-centric, functional handoffs, get it right the first time Iterative: process framework, phases, tool driven, artifact heavy Adaptive: iterative, self-organizing teams, value driven, transparent www.torak.com
  • 9. Prescriptive vs. Adaptive 120+ 13 9 6 0 RUP XP Scrum Kanban Do Whatever More Prescriptive More Adaptive (roles, activities & artifacts) Source: Kanban and Scrum, making the most of both. Henrik Kniberg & Mattias Skarin www.torak.com
  • 10. Prescriptive vs. Adaptive Waterfall Predictive Process The plan creates cost and schedule estimates Constraints Estimates Scope (requirements) Cost Time Plan Driven Agile Adaptive Process The vision creates feature estimates Cost Time Scope (features) Value/Vision Driven www.torak.com
  • 11. Sequential vs. Overlapping development Requirements Design Code Test Source: “The New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986. Rather than doing all of one thing at a time... Agile teams do a little of everything all the time. www.torak.com
  • 13. Envision / Explore cycles Constant User Interactions www.torak.com
  • 14. PDCA - Plan, Do, Check, Act ACT PLAN DO PDCA Cycle CHECK Continuous Improvements www.torak.com
  • 15. Agile Methodologies ●Scrum ●XP - Extreme Programming ●Kanban www.torak.com
  • 16. Origins ... Scrum ● 1986, Hirotaka Takeuchi and Ikujiro Nonaka described a new approach to commercial product development "holistic or rugby approach" ● 1991, DeGrace and Stahl first referred to this as the scrum approach. Ken Schwaber used such an approach at his company, Advanced Development Methods, and Jeff Sutherland, with John Scumniotales and Jeff McKenna, developed a similar approach at Easel Corporation, and were the first to refer to it using the single word Scrum. ● 1995, Sutherland and Schwaber jointly presented a paper describing the Scrum methodology ● 2001, Ken Schwaber teamed up with Mike Beedle to describe the method in the book "Agile Software Development with Scrum". XP - Extreme Programming ● created by Kent Beck during his work on the Chrysler Comprehensive Compensation System (C3) payroll project, who worked with Don Wells, Ron Jeffries, Martin Fowler and Chet Hendrickson ● takes software development "best practices" to extreme levels Kanban for development ● Japanese for "signboard" ● Taiichi Onho developed 1940/1950 kanbans to control production between processes and to implement Just n Time (JIT) manufacturing at Toyota manufacturing plants in Japan. ● 2003, David J. Anderson formulated the Kanban Method as an approach to incremental, evolutionary process and systems change for organizations www.torak.com
  • 17. Scrum Product Backlog (prioritized) Sprint Backlog Sprint Planning Sprint Retrospective Sprint Review Daily Scrum Product Increment Sprint Task Board Sprint Burndown Scrum Master Product Owner Team Stakeholders Users Roles www.torak.com
  • 18. Scrum ● focus on delivering the highest business value in the shortest time ● allows to rapidly and repeatedly inspect actual working software ● the business sets the priorities & teams self-organize to determine the best way to deliver the work ● every sprint (1-4 weeks) anyone can see real working software and decide to release it as is, or continue to enhance it for another sprint www.torak.com
  • 19. Scrum 1. Roles ● Product Owner ● Scrum Master ● Development Team 2. Ceremonies ● Daily Scrum ● Sprint Planning ● Sprint Review ● Sprint Retrospective 3. Artifacts ● Product backlog, sprint backlog, user stories ● Burn-down chart ● Work increment www.torak.com
  • 20. XP - eXtreme Programming ● improve software quality and responsiveness to changing customer requirements ● frequent releases in short development cycles ● improve productivity and regular checkpoints with the customer ● paired programming www.torak.com
  • 21. XP - eXtreme Programming www.torak.com
  • 23. Kanban - 3 basic principles 1. Start with what you do now ● Kanban does not prescribe a specific set of roles or process steps 2. Agree to pursue incremental, evolutionary change ● continuous small changes that stick vs. sweeping changes that fail due to resistance and fear in the organization 3. Respect the current process, roles, responsibilities & titles ● gain support, reduce fear/resistance to change and experience the benefits as a team Kanban Board www.torak.com
  • 24. Kanban - 5 Core Properties 1. Visualize the workflow ● Kanban literally means "signboard" or "billboard" 2. Limit Work In Process (WIP) ● use a pull system - establish and respect your ideal capacity 3. Manage Flow ● monitor, measure and report the flow of work through each state 4. Make Process Policies Explicit ● describe the process accurately in order to improve it 5. Improve Collaboratively ● using models & the scientific method (empirical) to implement continuous, incremental and evolutionary changes Kanban Board www.torak.com
  • 26. Kanban: Start 1 a b to do in process done Start with a simple task board with 3 columns: to do, in process and done. Each card represent a work item in the current scope. Names can be associated with the cards. The key is to setup an easy way to visualize the work, and create an area for social interactions. c www.torak.com
  • 27. Kanban: Start 2 a b to do in process done Start with a simple task board with 3 columns: to do, in process and done. Each card represent a work item in the current scope. Names can be associated with the cards. The key is to setup an easy way to visualize the work, and create an area for social interactions. b a to do in process done A problem with such a simplistic board, is the lack of rules and the concept of time- boxing. A typical problem is accumulating too much work in progress (WIP). Kanban is more than just adding work items on a board, it's also applying a PULL process. a b a b a c c c a c www.torak.com
  • 28. Kanban: Start 3 a b to do in process done Start with a simple task board with 3 columns: to do, in process and done. Each card represent a work item in the current scope. Names can be associated with the cards. The key is to setup an easy way to visualize the work, and create an area for social interactions. b a to do in process done A problem with such a simplistic board, is the lack of rules and the concept of time- boxing. A typical problem is accumulating too much work in progress (WIP). Kanban is more than just adding work items on a board, it's also applying a PULL process. a b a b a c c c a to do in process done To truly embrace Kanban, we must regulate the volume of cards on the board. This can easily be accomplished by identifying clear thresholds associated to better defined stages of work (columns). Another improvement is to set a multi-tasking limit per user (2) and using late binding of tasks to owners. Note that not all team members must have 2 tasks with their names, this is a maximum of 2. b c a ready 2 5 a c c www.torak.com
  • 29. Kanban: Mechanics to do in process done b c a ready 2 5 a c to do in process done b c a ready 2 5 a c to do in process done b c a ready 2 5 a c a 1. Team member A completes a card and moves it to the "done" column. 2. Team member A pulls a new card from the "ready" column and starts working on it by placing it in the "in process" column. 3. The team responds to the pull event and selects the next priority card by moving it to the "ready" column. www.torak.com
  • 30. Scrumban: Flow to do in process done b c ready 2 5 a c b to do specify done b c ready 2 3 a c b execute 2 Now that we have established our team capacity and we have a pull system, we can streamline the ideal flow. www.torak.com
  • 31. Kanban: Flow to do in process done b c ready 2 5 a c b to do specify done b c ready 2 3 a c b execute 2 Now that we have established our team capacity and we have a pull system, we can streamline the ideal flow. a backlog specify done b ready 2 3 a c b complete execute 3 c 8 www.torak.com
  • 32. Highlights from each ... Scrum ● ceremonies (daily scrum, review and retrospective) ● time-boxed work using sprints ● burn-down charts XP - eXtreme Programming ● best practices ○ coding (standards, collective code ownership, simple design, metaphor) ○ continuous integration ○ test driven development (unit tests, automated testing, acceptance testing) ■ When a Bug is found tests are created before the bug is addressed (a bug is not an error in logic, it is a test you forgot to write) Kanban for development ● visual board ● pull system ● JIT backlog/work ● continuous flow www.torak.com
  • 34. Scaled Agile Framework - Big Picture www.torak.com
  • 35. Resources ● http://www.extremeprogramming.org/ ● http://xprogramming.com ● http://finance.groups.yahoo.com/group/kanbandev/ ● Takeuchi, Hirotaka; Nonaka, Ikujiro. "The New New Product Development Game". Harvard Business Review. ● DeGrace, Peter; Stahl, Leslie Hulet (1990-10-01). Wicked problems, righteous solutions. Prentice Hall. ● Kanban: Successful Evolutionary Change for Your Technology Business by David J. Anderson ● Agile Software Development with Scrum by Ken Schwaber and Mike Beedle ● Mary Poppendieck, Tom Poppendieck (2003), "Lean Software Development: An Agile Toolkit" www.torak.com
  • 36. Agile Coaching, Staffing and Training. Learn more at www.torak.com Learn more at www.AgileTestingFramework.com
  • 38. This presentation was inspired by the work of many people and we have done our very best to attribute all authors of texts and images, and recognize any copyrights. If you think that anything in this presentation should be changed, added or removed, please contact us. http://creativecommons.org/licenses/by-nc-nd/3.0/ www.torak.com