Share
Embed
Transcript
52 slides
-
About Johnny Graber •Software Engineer @ Swiss Medical Association •Twitter:
@j_graber •E-Mail: [email protected] •Blog: ImproveAndRepeat.com -
Agenda •Challenges of Agile Software Development •How Xanpan Helps •How
to Start with Xanpan -
Scrum is great, when •Your team is co-located •All have
the same goal •You control your environment •You work with professionals •Your team size is 7±2 Is this your project? Keep using Scrum! -
However, sometimes… •You don’t control your environment •Have to work
with whomever is available •Everyone has his own agenda •You work in different places (or time-zones) Sounds familiar? Then keep listening! -
The same is true when •You are a small team
•You are fully focused on your customers •You deploy multiple times a day •Quality is really important -
In a sprint •We focus on a goal •We pretend
nothing changes •We ignore new facts -
But •The world changes •Goals are moved around •There is
a lot to learn -
Unplanned work •Is considered bad •Will occur •Needs to be
handled •Often the highest priority (e.g. Bugs) -
Commitment •Great when you control your environment •Bad if you
don’t •Work on support issues • Changes in priority •Dysfunctional organisations -
Commit to a goal Follow the plan Unplanned work pops
up Unable to change Forbid changes Plan more -
Task size •Not all work fits in a sprint •Artificial
slices without business value •Work can’t span multiple sprints • Less important work as a fill-in -
Velocity •Is a negative metric •Good to point out problems
•Bad indicator of progress •Easily manipulated -
5 often occurring symptoms 1. We are unable to learn
while doing the work 2. Unplanned work pops up and can’t be handled 3. Commitment is impossible 4. We do artificial tasks with no business value 5. High velocity only creates little value -
Xanpan •Created by Allan Kelly •Shows how you can combine
different practices to one full methodology •Book: Leanpub.com/xanpan -
Xanpan uses •Extreme Programming for technical practices •Kanban for organisational
practices •Some unique ideas •Whatever works and seems appropriate -
“But above all, combine the parts of methods that work
for you.” – Allan Kelly -
Extreme Programming (XP) •Is intended to improve software quality •Puts
coding in the centre •Emphasizes teamwork -
Fine-scale feedback •Pair programming •Test-driven development (TDD) •Acceptance test-driven development
(ATDD) •Continuous integration •Refactoring •Small releases -
Shared understanding •Code reviews •Coding standards •Collective code ownership •Simple
design •System metaphor -
Kanban •Inspired by the Toyota Production System •Just in time
(JIT) delivery •Pull-principle: Work gets pulled, not pushed •Goal: reduce waist (lean manufacturing) -
Kanban and software development •Production is different from development •Repetitive
tasks should be done the same way •Build • Deploy •Value generating tasks should have a structure -
High level view on development 1. Identify the problem 2.
Find a solution 3. Implement the solution 4. Verify if the solution solves the problem (A)TDD -
Kanban rules 1. Visualise your work flow 2. Limit the
work in progress (WIP-Limit) 3. Continuously improve your system -
The Kanban board •Start with your current work flow •Columns
specify the steps in the work flow •Set WIP-Limits for the different steps •Pull the work horizontally through your board -
Flow •Cycle time: how long it takes to finish a
task •Optimise for capacity or speed https://www.flickr.com/photos/33581336@N02/6565898403 https://www.flickr.com/photos/johnny_graber/6097268715 -
Xanpan: Agile, but different •Work can span more than one
iteration •No personal commitment •Unplanned work is allowed and handled -
“Unless a team is actively working to improve software quality,
not only will Xanpan fail, but any attempts at Agile are also likely to fail.” – Allan Kelly -
Quality driven •Is free when you invest in it •Necessary
to go fast •XP-Practices to keep it up from the start • TDD •ATDD • Code Reviews -
How work is organised •All items have an absolute priority
order • PO can change it when necessary •Ballpark estimates until stories are split in tasks •Unplanned work & bugs get prioritised •Work is tracked on a Kanban board •Small iterations as pacemaker -
The team •Creates a releasable product in every iteration •Accepts
a certain amount of work •Average Velocity as guidance plus a bit more • No guarantee that it will be delivered •Work is done following the absolute priority order •Creates its own Kanban board -
Suggested colours for cards •Blue – stories with business value
•White – tasks (smallest practical work items) •Red – bugs •Yellow – unplanned work -
Different planning horizons •Iteration: 1/2/4 weeks •Quarterly plan: next 3
months •Only ballpark estimates •Roadmap: 1 – 2 years ahead •Only high-level • What could be •No estimates -
1. Planning meeting Agree on expected velocity Present candidate stories
Discuss & break down high. priority story into tasks More capacity? Order stories & tasks Yes No © Xanpan by Allan Kelly -
Present candidate stories Discuss & break down high. priority story
into tasks More capacity? Order … Yes No Following planning meetings Demo completed work Review work, count points Hold retrospective Agree on expected velocity based on prev. iterations © Xanpan by Allan Kelly -
Xanpan in action (as a developer) 1. Planning meeting: Split
stories, agree on work 2. You pick the top prioritised item 3. You implement the item 4. You put it in the ready queue of the next step downstream 5. Repeat at step 2 -
Xanpan in action (as product owner) 1. You pick a
set of candidate stories (quart. plan) 2. You address open questions with the business 3. You bring them to the planning meeting 4. You agree on the ordering of the items 5. You update your quarterly plan 6. Repeat at step 1 -
Bugs and unplanned work •They pop up, even when you
use Xanpan •Product Owner (and team) sets a priority •They get implemented when they reach the top •Drop everything only when current work is less important -
All comes together •When unforeseen things occur, you create a
task •Unplanned work gets prioritised and done when on top of the queue •No commitment to work, only agreement •Work can span two iterations (no artificial chunks) •Velocity only used for planning, optimise cycle time -
Start small •Define your goal and write it down •Start
with your daily routines or a pet project •Create a Kanban board •Limit your work in progress •Focus on value, not on the number of cards -
Add some Xanpan •Follow the card colour system •Identify which
tasks have value •Optimise your flow -
Plan ahead •What should be done in the next 3
months? •And what in the next year? •Write it down and include it in the backlog -
Read these books •“Xanpan” by Allan Kelly ISBN: 978-1-291-85273-8 •“Kanban”
by David J. Anderson ISBN: 978-0-984-52140-1 •“Extreme Programming Explained” by Kent Beck ISBN: 978-0-321-27865-4 -
Evaluate your goal •Did you reach it? •What have you
learned? •Was it a success? •What obstacles did you find? •Are you ready to implement it at work? -
Conclusion •In Xanpan you can use whatever works for you
•Quality is the driving force •Unplanned work is accepted •Work can overlap an iteration