Slide 1

Slide 1 text

Xanpan A team centric agile method story Pronounce it Zan pan

Slide 2

Slide 2 text

@yot88 Who am I yoan thirion Technicalagile coach https://yoan-thirion.com

Slide 3

Slide 3 text

@yot88 Allan kelly Agile coach Software engineer

Slide 4

Slide 4 text

What limitations have you already lived or observed with Kanban or Scrum ?

Slide 5

Slide 5 text

#nomagicmethod #nomagicframework

Slide 6

Slide 6 text

@yot88 What is xanpan? A process for agile teams Team at the heart Principles practices

Slide 7

Slide 7 text

@yot88 XP scrum lean kanban Product management xanpan pragmatism

Slide 8

Slide 8 text

@yot88 PRINCIPLES Work in iterations Team-centric Work to improve Flow Quality is free (invest in quality) Visualize

Slide 9

Slide 9 text

@yot88 Work in iterations 2 weeks iterations from mid-week to mid-week releasable product at the end of each iteration continuous integration -> continuous deployment Deadlines help to focus : limit wip

Slide 10

Slide 10 text

@yot88 Planning -3 players Product Owner played by a product manager, or a BA The creators Software engineers, Testers, UX, UI,… The facilitator Dedicated or not Product ownership is considered a practice rather than a role.

Slide 11

Slide 11 text

@yot88 Planning -artefacts vertical slices of business functionality from multiple projects or products Blue cards Tasks related to blue cards Bugs White cards Red cards Planning board Planning poker

Slide 12

Slide 12 text

@yot88 Planning Meeting

Slide 13

Slide 13 text

@yot88 Retrospective “Teams may also hold a retrospective as part of the iteration end routine, although not all teams hold retrospectives, and even those who do may not hold them at every iteration.” Formal or not (dialogue)

Slide 14

Slide 14 text

@yot88 Work in routine Event Frequency Iteration Every 2 weeks –10 working days Stand-up meeting Everyday -Maximum 15 Minutes Iteration review meeting End of every iteration 20 minutes at end of Iteration Retrospective event End of every iteration Formal retrospective End of every iteration (new teams) (60-90 minutes) every second (mature teams) Informal retrospective Every second iteration (30mins) for mature teams Demo At least every iteration which does not release Release Minimum quarterly high-performing teams will release many times during Iteration Sanitize the board & count the points

Slide 15

Slide 15 text

@yot88 Plan beyond the iteration The quarterly plan looks at most 12 weeks into the future Roadmap looks at the next quarter Iteration plan : output of the next two weeks More certainty Filled to approximately the capacity of each iteration : WIP limit for iterations

Slide 16

Slide 16 text

@yot88 Plan beyond the iteration Quarter & Roadmap are only horizons planning != scheduling Plan = looking into the future to learn about what might happen : perhaps preparefor it with Design thinking for example

Slide 17

Slide 17 text

@yot88 where is the Kanban part in it ?

Slide 18

Slide 18 text

@yot88 Kanban-style flow Xanpanallows both planned and unplanned work Commitment Work can flow from iteration to iteration Blue cards must bring value (Small stories regularly don’t)

Slide 19

Slide 19 text

Team-centric the team may be working on more than one product or project at a time.

Slide 20

Slide 20 text

@yot88 visualise Sprint backlog Stock of unplanned work Work For today

Slide 21

Slide 21 text

@yot88 visualise State of the team and their work See to learn

Slide 22

Slide 22 text

Quality is free All successful software needs rework how easy is the rework? Low quality makes rework harder, and therefore slower. High quality makes rework easier, and therefore faster.

Slide 23

Slide 23 text

Poor quality Rework destroys flow stories and tasks can’t truly be considered ‘done’ hidden work is flowing between iterations Metrics are destroyed Inordinate amounts of time prioritizing, reporting, doing rework instead of delivering value inordinate amounts of money on testing resources and cycles

Slide 24

Slide 24 text

How to define quality of a software product ? Defects Maintainability

Slide 25

Slide 25 text

@yot88 How to build quality in ?

Slide 26

Slide 26 text

@yot88 Technical practices some of Test-Driven Development (Unit, ATDD) Refactoring Frequent builds Continuous Integration Source code control Code reviews Pair programming Static analysis Coding Standards

Slide 27

Slide 27 text

@yot88 "create your own process, don’t follow someone else’s prescription.” – Allan Kelly

Slide 28

Slide 28 text

@yot88

Slide 29

Slide 29 text

@yot88 Just do it : action over words Keep or drop Identify a practice, tool, technique, whatever from somewhere else. Decide what it would mean to your team: what would you do differently? Set a time frame Make the change at the end of the period : check

Slide 30

Slide 30 text

@yot88 experiment more

Slide 31

Slide 31 text

@yot88 https://www.linkedin.com/posts/maurostrione_scrum-agile-devops-activity-6650103984235298819-Zb5a

Slide 32

Slide 32 text

@yot88 “xanpan is the kind of stuff that should emerge from every agile teams when not constrained by some “agile” dogms.”

Slide 33

Slide 33 text

https://agnosticagile.org/

Slide 34

Slide 34 text

What could you try to implement in the near days to solve the limitations you observed ?

Slide 35

Slide 35 text

@yot88 ANY QUESTION ? REMARKS ? OPEN YOUR MIC

Slide 36

Slide 36 text

@yot88 PLEASE GIVE YOUR FEEDBACK #CONTINUOUSIMPROVEMENT https://roti.express/r/mdfvjy

Slide 37

Slide 37 text

@yot88 ressources

Slide 38

Slide 38 text

@yot88 thank you yoan thirion Technicalagile coach https://yoan-thirion.com