kanban for beginners - agileee 2011

49
Kanban Quiz for Beginners. 看板 Agileee 2011 Mark Weber, Robert Wiechmann | Kiev, 2011-09-24

Upload: robert-wiechmann

Post on 13-May-2015

6.268 views

Category:

Business


1 download

DESCRIPTION

http://www.agileee.com

TRANSCRIPT

Page 1: Kanban for Beginners - AgileEE 2011

Kanban Quiz

for Beginners

看板

Agileee 2011

Mark Weber Robert Wiechmann | Kiev 2011-09-24

Kanban Quiz

for Winners

看板 Agileee 2011

Mark Weber Robert Wiechmann | Kiev 2011-09-24

Rules of the Game 3 game level 15 questions

5 audience joker

看板

Where does Kanban come from

Wolga

Lada

Toyota

Mercedes

Where does Kanban come from

bull Is originally from the automotive industry - Toyota Production System (TPS)

bull All we know about Kanban is an inspiration from the manufacturing

bull It is also well known in the software development since 2003 (inspired by the book from David J Anderson)

What does the term Kanban mean

Signal Card

Red Card

Chinese Car Brand

Ukraine National Dish

What does the term Kanban mean

bull In Japanese the word Kan means signal and ban means cardldquo

bull The card is a signal to trigger actions which is reflected by bdquoSignal Cardldquo

In what kind of management culture do you use Kaizen

Mean Management

Clean Management

Team Management

Lean Management

In what kind of management culture do you use Kaizen

bull Kaizen is Japanese for improvementldquo or change for the better refers to philosophy or practices that focus upon continuous improvement

bull Lean Management is a bundle of principles

bull bring expertise and responsibility together

bull work self-organized

bull eliminate ldquowasterdquo

bull harmonize processes and

bull attempt for continuous improvement (Kaizen)

What is not a principle of Kanban

Visualization

Transparency

Quality

Control

Audiance

Joker

What are Kanban principles

bull visualize the workflow

bull limit Work in Progress (WIP)

and

bull pull value through the system

bull try to enhance throughput

bull quality is included

bull use a sorted Backlog

ldquoCongratulations You really got talent Go to the next levelrdquo

Is it true that everything is allowed in Kanban to constantly

improve the work

Yes No

What is allowed in Kanban

bull Kanban leaves almost everything open you can do whatever is needed

bull Kanban supports the team to find the best solution by

bull continuously monitoring the work to improve the process

What kind of stream identifies all steps to develop a

prodcuct

Mega Stream

Media Stream

Value Stream

Live Stream

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 2: Kanban for Beginners - AgileEE 2011

Kanban Quiz

for Winners

看板 Agileee 2011

Mark Weber Robert Wiechmann | Kiev 2011-09-24

Rules of the Game 3 game level 15 questions

5 audience joker

看板

Where does Kanban come from

Wolga

Lada

Toyota

Mercedes

Where does Kanban come from

bull Is originally from the automotive industry - Toyota Production System (TPS)

bull All we know about Kanban is an inspiration from the manufacturing

bull It is also well known in the software development since 2003 (inspired by the book from David J Anderson)

What does the term Kanban mean

Signal Card

Red Card

Chinese Car Brand

Ukraine National Dish

What does the term Kanban mean

bull In Japanese the word Kan means signal and ban means cardldquo

bull The card is a signal to trigger actions which is reflected by bdquoSignal Cardldquo

In what kind of management culture do you use Kaizen

Mean Management

Clean Management

Team Management

Lean Management

In what kind of management culture do you use Kaizen

bull Kaizen is Japanese for improvementldquo or change for the better refers to philosophy or practices that focus upon continuous improvement

bull Lean Management is a bundle of principles

bull bring expertise and responsibility together

bull work self-organized

bull eliminate ldquowasterdquo

bull harmonize processes and

bull attempt for continuous improvement (Kaizen)

What is not a principle of Kanban

Visualization

Transparency

Quality

Control

Audiance

Joker

What are Kanban principles

bull visualize the workflow

bull limit Work in Progress (WIP)

and

bull pull value through the system

bull try to enhance throughput

bull quality is included

bull use a sorted Backlog

ldquoCongratulations You really got talent Go to the next levelrdquo

Is it true that everything is allowed in Kanban to constantly

improve the work

Yes No

What is allowed in Kanban

bull Kanban leaves almost everything open you can do whatever is needed

bull Kanban supports the team to find the best solution by

bull continuously monitoring the work to improve the process

What kind of stream identifies all steps to develop a

prodcuct

Mega Stream

Media Stream

Value Stream

Live Stream

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 3: Kanban for Beginners - AgileEE 2011

Rules of the Game 3 game level 15 questions

5 audience joker

看板

Where does Kanban come from

Wolga

Lada

Toyota

Mercedes

Where does Kanban come from

bull Is originally from the automotive industry - Toyota Production System (TPS)

bull All we know about Kanban is an inspiration from the manufacturing

bull It is also well known in the software development since 2003 (inspired by the book from David J Anderson)

What does the term Kanban mean

Signal Card

Red Card

Chinese Car Brand

Ukraine National Dish

What does the term Kanban mean

bull In Japanese the word Kan means signal and ban means cardldquo

bull The card is a signal to trigger actions which is reflected by bdquoSignal Cardldquo

In what kind of management culture do you use Kaizen

Mean Management

Clean Management

Team Management

Lean Management

In what kind of management culture do you use Kaizen

bull Kaizen is Japanese for improvementldquo or change for the better refers to philosophy or practices that focus upon continuous improvement

bull Lean Management is a bundle of principles

bull bring expertise and responsibility together

bull work self-organized

bull eliminate ldquowasterdquo

bull harmonize processes and

bull attempt for continuous improvement (Kaizen)

What is not a principle of Kanban

Visualization

Transparency

Quality

Control

Audiance

Joker

What are Kanban principles

bull visualize the workflow

bull limit Work in Progress (WIP)

and

bull pull value through the system

bull try to enhance throughput

bull quality is included

bull use a sorted Backlog

ldquoCongratulations You really got talent Go to the next levelrdquo

Is it true that everything is allowed in Kanban to constantly

improve the work

Yes No

What is allowed in Kanban

bull Kanban leaves almost everything open you can do whatever is needed

bull Kanban supports the team to find the best solution by

bull continuously monitoring the work to improve the process

What kind of stream identifies all steps to develop a

prodcuct

Mega Stream

Media Stream

Value Stream

Live Stream

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 4: Kanban for Beginners - AgileEE 2011

Where does Kanban come from

Wolga

Lada

Toyota

Mercedes

Where does Kanban come from

bull Is originally from the automotive industry - Toyota Production System (TPS)

bull All we know about Kanban is an inspiration from the manufacturing

bull It is also well known in the software development since 2003 (inspired by the book from David J Anderson)

What does the term Kanban mean

Signal Card

Red Card

Chinese Car Brand

Ukraine National Dish

What does the term Kanban mean

bull In Japanese the word Kan means signal and ban means cardldquo

bull The card is a signal to trigger actions which is reflected by bdquoSignal Cardldquo

In what kind of management culture do you use Kaizen

Mean Management

Clean Management

Team Management

Lean Management

In what kind of management culture do you use Kaizen

bull Kaizen is Japanese for improvementldquo or change for the better refers to philosophy or practices that focus upon continuous improvement

bull Lean Management is a bundle of principles

bull bring expertise and responsibility together

bull work self-organized

bull eliminate ldquowasterdquo

bull harmonize processes and

bull attempt for continuous improvement (Kaizen)

What is not a principle of Kanban

Visualization

Transparency

Quality

Control

Audiance

Joker

What are Kanban principles

bull visualize the workflow

bull limit Work in Progress (WIP)

and

bull pull value through the system

bull try to enhance throughput

bull quality is included

bull use a sorted Backlog

ldquoCongratulations You really got talent Go to the next levelrdquo

Is it true that everything is allowed in Kanban to constantly

improve the work

Yes No

What is allowed in Kanban

bull Kanban leaves almost everything open you can do whatever is needed

bull Kanban supports the team to find the best solution by

bull continuously monitoring the work to improve the process

What kind of stream identifies all steps to develop a

prodcuct

Mega Stream

Media Stream

Value Stream

Live Stream

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 5: Kanban for Beginners - AgileEE 2011

Where does Kanban come from

bull Is originally from the automotive industry - Toyota Production System (TPS)

bull All we know about Kanban is an inspiration from the manufacturing

bull It is also well known in the software development since 2003 (inspired by the book from David J Anderson)

What does the term Kanban mean

Signal Card

Red Card

Chinese Car Brand

Ukraine National Dish

What does the term Kanban mean

bull In Japanese the word Kan means signal and ban means cardldquo

bull The card is a signal to trigger actions which is reflected by bdquoSignal Cardldquo

In what kind of management culture do you use Kaizen

Mean Management

Clean Management

Team Management

Lean Management

In what kind of management culture do you use Kaizen

bull Kaizen is Japanese for improvementldquo or change for the better refers to philosophy or practices that focus upon continuous improvement

bull Lean Management is a bundle of principles

bull bring expertise and responsibility together

bull work self-organized

bull eliminate ldquowasterdquo

bull harmonize processes and

bull attempt for continuous improvement (Kaizen)

What is not a principle of Kanban

Visualization

Transparency

Quality

Control

Audiance

Joker

What are Kanban principles

bull visualize the workflow

bull limit Work in Progress (WIP)

and

bull pull value through the system

bull try to enhance throughput

bull quality is included

bull use a sorted Backlog

ldquoCongratulations You really got talent Go to the next levelrdquo

Is it true that everything is allowed in Kanban to constantly

improve the work

Yes No

What is allowed in Kanban

bull Kanban leaves almost everything open you can do whatever is needed

bull Kanban supports the team to find the best solution by

bull continuously monitoring the work to improve the process

What kind of stream identifies all steps to develop a

prodcuct

Mega Stream

Media Stream

Value Stream

Live Stream

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 6: Kanban for Beginners - AgileEE 2011

What does the term Kanban mean

Signal Card

Red Card

Chinese Car Brand

Ukraine National Dish

What does the term Kanban mean

bull In Japanese the word Kan means signal and ban means cardldquo

bull The card is a signal to trigger actions which is reflected by bdquoSignal Cardldquo

In what kind of management culture do you use Kaizen

Mean Management

Clean Management

Team Management

Lean Management

In what kind of management culture do you use Kaizen

bull Kaizen is Japanese for improvementldquo or change for the better refers to philosophy or practices that focus upon continuous improvement

bull Lean Management is a bundle of principles

bull bring expertise and responsibility together

bull work self-organized

bull eliminate ldquowasterdquo

bull harmonize processes and

bull attempt for continuous improvement (Kaizen)

What is not a principle of Kanban

Visualization

Transparency

Quality

Control

Audiance

Joker

What are Kanban principles

bull visualize the workflow

bull limit Work in Progress (WIP)

and

bull pull value through the system

bull try to enhance throughput

bull quality is included

bull use a sorted Backlog

ldquoCongratulations You really got talent Go to the next levelrdquo

Is it true that everything is allowed in Kanban to constantly

improve the work

Yes No

What is allowed in Kanban

bull Kanban leaves almost everything open you can do whatever is needed

bull Kanban supports the team to find the best solution by

bull continuously monitoring the work to improve the process

What kind of stream identifies all steps to develop a

prodcuct

Mega Stream

Media Stream

Value Stream

Live Stream

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 7: Kanban for Beginners - AgileEE 2011

What does the term Kanban mean

bull In Japanese the word Kan means signal and ban means cardldquo

bull The card is a signal to trigger actions which is reflected by bdquoSignal Cardldquo

In what kind of management culture do you use Kaizen

Mean Management

Clean Management

Team Management

Lean Management

In what kind of management culture do you use Kaizen

bull Kaizen is Japanese for improvementldquo or change for the better refers to philosophy or practices that focus upon continuous improvement

bull Lean Management is a bundle of principles

bull bring expertise and responsibility together

bull work self-organized

bull eliminate ldquowasterdquo

bull harmonize processes and

bull attempt for continuous improvement (Kaizen)

What is not a principle of Kanban

Visualization

Transparency

Quality

Control

Audiance

Joker

What are Kanban principles

bull visualize the workflow

bull limit Work in Progress (WIP)

and

bull pull value through the system

bull try to enhance throughput

bull quality is included

bull use a sorted Backlog

ldquoCongratulations You really got talent Go to the next levelrdquo

Is it true that everything is allowed in Kanban to constantly

improve the work

Yes No

What is allowed in Kanban

bull Kanban leaves almost everything open you can do whatever is needed

bull Kanban supports the team to find the best solution by

bull continuously monitoring the work to improve the process

What kind of stream identifies all steps to develop a

prodcuct

Mega Stream

Media Stream

Value Stream

Live Stream

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 8: Kanban for Beginners - AgileEE 2011

In what kind of management culture do you use Kaizen

Mean Management

Clean Management

Team Management

Lean Management

In what kind of management culture do you use Kaizen

bull Kaizen is Japanese for improvementldquo or change for the better refers to philosophy or practices that focus upon continuous improvement

bull Lean Management is a bundle of principles

bull bring expertise and responsibility together

bull work self-organized

bull eliminate ldquowasterdquo

bull harmonize processes and

bull attempt for continuous improvement (Kaizen)

What is not a principle of Kanban

Visualization

Transparency

Quality

Control

Audiance

Joker

What are Kanban principles

bull visualize the workflow

bull limit Work in Progress (WIP)

and

bull pull value through the system

bull try to enhance throughput

bull quality is included

bull use a sorted Backlog

ldquoCongratulations You really got talent Go to the next levelrdquo

Is it true that everything is allowed in Kanban to constantly

improve the work

Yes No

What is allowed in Kanban

bull Kanban leaves almost everything open you can do whatever is needed

bull Kanban supports the team to find the best solution by

bull continuously monitoring the work to improve the process

What kind of stream identifies all steps to develop a

prodcuct

Mega Stream

Media Stream

Value Stream

Live Stream

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 9: Kanban for Beginners - AgileEE 2011

In what kind of management culture do you use Kaizen

bull Kaizen is Japanese for improvementldquo or change for the better refers to philosophy or practices that focus upon continuous improvement

bull Lean Management is a bundle of principles

bull bring expertise and responsibility together

bull work self-organized

bull eliminate ldquowasterdquo

bull harmonize processes and

bull attempt for continuous improvement (Kaizen)

What is not a principle of Kanban

Visualization

Transparency

Quality

Control

Audiance

Joker

What are Kanban principles

bull visualize the workflow

bull limit Work in Progress (WIP)

and

bull pull value through the system

bull try to enhance throughput

bull quality is included

bull use a sorted Backlog

ldquoCongratulations You really got talent Go to the next levelrdquo

Is it true that everything is allowed in Kanban to constantly

improve the work

Yes No

What is allowed in Kanban

bull Kanban leaves almost everything open you can do whatever is needed

bull Kanban supports the team to find the best solution by

bull continuously monitoring the work to improve the process

What kind of stream identifies all steps to develop a

prodcuct

Mega Stream

Media Stream

Value Stream

Live Stream

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 10: Kanban for Beginners - AgileEE 2011

What is not a principle of Kanban

Visualization

Transparency

Quality

Control

Audiance

Joker

What are Kanban principles

bull visualize the workflow

bull limit Work in Progress (WIP)

and

bull pull value through the system

bull try to enhance throughput

bull quality is included

bull use a sorted Backlog

ldquoCongratulations You really got talent Go to the next levelrdquo

Is it true that everything is allowed in Kanban to constantly

improve the work

Yes No

What is allowed in Kanban

bull Kanban leaves almost everything open you can do whatever is needed

bull Kanban supports the team to find the best solution by

bull continuously monitoring the work to improve the process

What kind of stream identifies all steps to develop a

prodcuct

Mega Stream

Media Stream

Value Stream

Live Stream

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 11: Kanban for Beginners - AgileEE 2011

What are Kanban principles

bull visualize the workflow

bull limit Work in Progress (WIP)

and

bull pull value through the system

bull try to enhance throughput

bull quality is included

bull use a sorted Backlog

ldquoCongratulations You really got talent Go to the next levelrdquo

Is it true that everything is allowed in Kanban to constantly

improve the work

Yes No

What is allowed in Kanban

bull Kanban leaves almost everything open you can do whatever is needed

bull Kanban supports the team to find the best solution by

bull continuously monitoring the work to improve the process

What kind of stream identifies all steps to develop a

prodcuct

Mega Stream

Media Stream

Value Stream

Live Stream

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 12: Kanban for Beginners - AgileEE 2011

ldquoCongratulations You really got talent Go to the next levelrdquo

Is it true that everything is allowed in Kanban to constantly

improve the work

Yes No

What is allowed in Kanban

bull Kanban leaves almost everything open you can do whatever is needed

bull Kanban supports the team to find the best solution by

bull continuously monitoring the work to improve the process

What kind of stream identifies all steps to develop a

prodcuct

Mega Stream

Media Stream

Value Stream

Live Stream

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 13: Kanban for Beginners - AgileEE 2011

Is it true that everything is allowed in Kanban to constantly

improve the work

Yes No

What is allowed in Kanban

bull Kanban leaves almost everything open you can do whatever is needed

bull Kanban supports the team to find the best solution by

bull continuously monitoring the work to improve the process

What kind of stream identifies all steps to develop a

prodcuct

Mega Stream

Media Stream

Value Stream

Live Stream

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 14: Kanban for Beginners - AgileEE 2011

What is allowed in Kanban

bull Kanban leaves almost everything open you can do whatever is needed

bull Kanban supports the team to find the best solution by

bull continuously monitoring the work to improve the process

What kind of stream identifies all steps to develop a

prodcuct

Mega Stream

Media Stream

Value Stream

Live Stream

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 15: Kanban for Beginners - AgileEE 2011

What kind of stream identifies all steps to develop a

prodcuct

Mega Stream

Media Stream

Value Stream

Live Stream

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 16: Kanban for Beginners - AgileEE 2011

What kind of stream identifies all steps to develop a

prodcuct

bull Value Stream identifies all steps in order to develop the wanted product

bull Makes visible how much time is spent on value adding vs non value adding (waste) work

bull The goal is to minimize the non value adding work or to prevent waste

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 17: Kanban for Beginners - AgileEE 2011

What is important for agile work with Kanban

Value Stream Example

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 18: Kanban for Beginners - AgileEE 2011

There are a number of known wastes in the software

development How many

5

8

9

7

Audiance

Joker

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 19: Kanban for Beginners - AgileEE 2011

7 wastes of software development

Mary and Tom Poppendieck translated the seven wastes of Lean into

bdquoThe 7 wastes of software developmentldquo

bull Delays eg waiting for something

bull Extra Features eg rising cost of complexity

bull Relearning eg writing a report vs talking to each other

bull Handoffs eg analyst to designer to developer to tester

bull Task Switching eg developer working on different topics

bull Partially Done Work eg un-tested un-documented un-deployed

bull Defects eg bug occure after release

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 20: Kanban for Beginners - AgileEE 2011

What fits perfect for working with Kanban

Move batches of tickets Focus on a single ticket

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 21: Kanban for Beginners - AgileEE 2011

What fits perfect for working with Kanban

bull Ideal in Kanban is to have the focus on one ticket

bull That is pulled as fast as possible from left (open) to right (done)

bull The activities or single steps should be value adding activities

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 22: Kanban for Beginners - AgileEE 2011

What would you do in the following case

Audiance

Joker

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 23: Kanban for Beginners - AgileEE 2011

Please take a look at the board The Product Owner wants to bring story bdquoEldquo to the

Kanban board because bdquoEldquo is more important than bdquoCldquo or bdquoDldquo What can he do

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 24: Kanban for Beginners - AgileEE 2011

Product Owner Team

Priority

Flow

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 25: Kanban for Beginners - AgileEE 2011

ldquoCongratulations You earned the SHU level by learning

the fundamentals Go onrdquo

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 26: Kanban for Beginners - AgileEE 2011

ldquoJoin Europes biggest business network We are looking for yourdquo

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 27: Kanban for Beginners - AgileEE 2011

What is the main difference between Kanban

and Scrum

Number of Columns

Limited Work in Progress Size of Cards

Prioritization

Audiance

Joker

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 28: Kanban for Beginners - AgileEE 2011

What is the main difference to Scrum

bull In Kanban you have to limit the work in progress

bull In Scrum you have protected timeboxed itereations

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 29: Kanban for Beginners - AgileEE 2011

What are the most often used metrics in Kanban

Name 2 of them

Cycle Time

Throughput

Hammer Time

Lead Time

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 30: Kanban for Beginners - AgileEE 2011

What are the most often used metrics in Kanban

Lead time

bull starts when the request is made and ends once delivered

bull is what the customer orand stakeholder sees

Cycle time

bull Time from starting to work on a ticket until it is done

Lead time

Ticket

Created Ticket

Live

Cycle time

Start Work

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 31: Kanban for Beginners - AgileEE 2011

What are the most often used metrics in Kanban

Throughput

bull is reported as a rate of valued work that was delivered in a given time period

bull it is used as an indicator of how well the system (team organisation) is performing and to demonstrate continuous improvement

bull allows planning of next milestonesstepscapabilities

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 32: Kanban for Beginners - AgileEE 2011

What does Scrum amp Kanban have in common They are

Agile

Self Organized

Focused

Planned on MS Project

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 33: Kanban for Beginners - AgileEE 2011

What does Scrum amp Kanban have in common

bull Focus ndash parallel work is reduced (WIP) timeboxes

bull Inspect amp Adapt ndash Constant Improvement (Kaikaku Kaizen)

bull Self Organization

bull Faster time to market

bull Expectation Management ndash Planning (Backlog Input Queue Cycle Time Throughput)

bull Satisfied Customer ndash early constant involvement of customers

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 34: Kanban for Beginners - AgileEE 2011

ldquoReally well done You are one the way to break with

tradition Now you received the HA level Go to the final levelrdquo

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 35: Kanban for Beginners - AgileEE 2011

Match the Kanban method to the following topics

There are several options

Teams in conservative cultures

Teams with a lot of specialisation Teams in regulated environments

Service Teams

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 36: Kanban for Beginners - AgileEE 2011

Kanban fits to a lot of topics

bull Kanban can be applied by everyone

bull Kanban enforces that the right work is being done in the right time rather than who is doing it

bull Participants apply to the systemworkflow in the most efficient manner

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 37: Kanban for Beginners - AgileEE 2011

Prioritize the following Classes of Services

in the correct order

Refactoring

Due Date

Standard

Expedite

1 2 3 4

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 38: Kanban for Beginners - AgileEE 2011

Classes of Services in Kanban

bull Service Level Agreements (SLA) are a part of a service contract where the level of services is formally defined

bull The classes of service are used to visualize different levels severities

bull Expedite - eg bug on live platform

bull Due Date - eg marketing campaign

bull Standard - eg user story

bull Refactoring ndash eg cleaning up code base

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 39: Kanban for Beginners - AgileEE 2011

What would you do in the following case

Audiance

Joker

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 40: Kanban for Beginners - AgileEE 2011

The QA has a problem with one ticket After tester 1 recognized a problem with the

ticket which he couldnacutet fix by himself he asked tester 2 for help They have been

trying to solve the issue for hours but without any result The 3 green cards in the

progress column are already finished by the developers What should they do next

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 41: Kanban for Beginners - AgileEE 2011

Please describe the characteristics of the following

Kanban boards correctly

Final

Question

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 42: Kanban for Beginners - AgileEE 2011

ldquoYES you did it With the RI level you are now able to

find new ways on your ownrdquo

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 43: Kanban for Beginners - AgileEE 2011

Thank you

for your

kind

attention

Mark Weber

markweberxingcom

Robert Wiechmann

robertwiechmannxingcom

The professional network

wwwxingcom

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 44: Kanban for Beginners - AgileEE 2011

Interesting Read

Terms

bull Kaikaku is about making fundamental and radical changes to a production system unlike

Kaizen which is focused on incremental minor changes

bull Shu-Ha-Ri is a Japanese martial art concept and describes the stages of learning to mastery

Links

bull Leand Kanban University httpwwwleankanbanuniversitycomresources

bull Limited WIP Society httpwwwlimitedwipsocietyorg

bull Kanban 101 httpwwwkanban101com

bull Lean Alliance Group httpswwwxingcomnetleanalliance

bull 7 wastes of Software Development httpagiledzonecomarticlesseven-wastes-software

bull Value Stream Mapping httpenwikipediaorgwikiValue_stream_mapping

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements

Page 45: Kanban for Beginners - AgileEE 2011

Disclaimer

This presentation was produced in September 2011 by XING AG (the Company) solely for use as an information source for potential business partners and is strictly

confidential It has been made available to you solely for your own information and may not be copied distributed or otherwise made available to any other person by any

recipient This presentation is not an offer for sale of securities in the United States The distribution of this presentation to you does not constitute an offer or invitation to

subscribe for or purchase any shares of the XING AG and neither this presentation nor anything contained herein shall form the basis of or be relied on in connection with any

offer or commitment whatsoeverThe facts and information contained herein are as up-to-date as is reasonably possible and are subject to revision in the future Neither the

Company nor any of its subsidiaries any directors officers employees advisors nor any other person makes any representation or warranty express or implied as to and no

reliance should be placed on the accuracy or completeness of the information contained in this presentation Neither the Company nor any of its subsidiaries any directors

officers employees advisors or any other person shall have any liability whatsoever for any loss arising directly or indirectly from any use of this presentation The same

applies to information contained in other material made available at the presentationWhile all reasonable care has been taken to ensure the facts stated herein are accurate

and that the opinions contained herein are fair and reasonable this document is selective in nature and is intended to provide an introduction to and overview of the business

of the Company Where any information and statistics are quoted from any external source such information or statistics should not be interpreted as having been adopted or

endorsed by the Company as being accurateThis presentation contains forward-looking statements relating to the business financial performance and results of the Company

andor the industry in which the Company operates These statements are generally identified by words such as believes expects predicts intends projects plans

estimates aims foresees anticipates targets and similar expressions The forward-looking statements including but not limited to assumptions opinions and views of

the Company or information from third party sources contained in this presentation are based on current plans estimates assumptions and projections and involve

uncertainties and risks Various factors could cause actual future results performance or events to differ materially from those described in these statements The Company

does not represent or guarantee that the assumptions underlying such forward-looking statements are free from errors nor do they accept any responsibility for the future

accuracy of the opinions expressed in this presentation No obligation is assumed to update any forward-looking statements