Agile Methods and Tools

(1)

IMP³rove

European Innovation Management Academy

Agile Methods and Tools

Hanna Kim

(2)

2

10/53140d

www.improve-innovation.eu; IMP³rove is a registered trademark

Agenda



Welcome and introduction



Differences between linear and agile project management



Agile methodologies: Scrum



Agile methodologies: Lean start-up



Agile methodologies: Kanban



Further information and research

(3)

3

10/53140d

(4)

4

10/53140d

Welcome and introduction

We will put you on mute to

enhance the audio quality

You are welcome to engage

throughout the whole session

• You can type in your

questions via the online

chat (right box at the bottom)

Please address the question

to “Everyone” or to “Hanna

Kim” (right box at the bottom)

• You can „raise your hand“

(5)

5

10/53140d

Differences between linear

and agile project

(6)

6

10/53140d

Overview

Optimization of project delivery yields accelerating

qualities

Source: IMP³rove – European Innovation Management Academy 2019

How to enhance development

processes?

Waterfall-type processes:

Agile processes:

Project development – two key process prototypes:

Description:

• Process in which progress

is seen as a steady

downwards flow, where

each phase must be

completed fully before the

next phase can begin

Advantages:

• Easy to understand and

use

• Manageable due to

deliverables in each

phase

• Good for small projects

with clear requirements

Disadvantages:

• High amounts of risk and

uncertainty

• Difficult to go back and

change closed stages

• Limited for long-term

projects and when

flexibility is required

Description:

• Set of principles under

which requirements and

solutions evolve through

the collaborative effort of

self-organizing

cross-functional teams

Advantages:

• Rapid and continuous

outcome

• Constant interaction

• Regular adaptation to

changing circumstances

(even in late phases)

Disadvantages:

• It’s difficult to assess the

effort required at the

beginning

• May appear hard to

document status of

progress in overall

process if final outcome is

not clear

(7)

7

10/53140d

Beyond the hype: Agile methods deliver value

1. Productivity was measured as a function of process productivity, effort and schedule Source: QSM Associates, Inc., The Money Pit (Standish Group), A.T. Kearney

Faster to market

Increase in

productivity

Better quality

Reduced cost

…37% faster to

market than average

…experience 16%

increase in team’s

productivity

1 …75% less defects

than industry average

…72% cheaper than

traditional waterfall

development projects

Key benefits

Agile projects are…

Key drivers:

up to 20% reduced cost

through optimized meetings

10-12% lower cost for

analysis & design activities

8% less cost for project

(8)

8

10/51450d

Best practices and common pitfalls applying agile methods

to consulting projects

Source: A.T. Kearney

• Time-box of 2 weeks for a sprint is recommended,

however, this depends on the project and should be

decided jointly in the team

• Limit daily stand-up meetings to 15 minutes and

enforce adherence to ensure efficiency

• Conduct daily stand-ups in person, not remotely

to allow better team interaction

• Actually stand during daily stand-up meetings to

increase attention

• Ask client to participate in joint sprint reviews for

continuous feedback, new ideas and alignment

• Take sprint retrospectives seriously and focus on

constructive feedback and team improvement

• Agile delivery team size should be between 3 to 9

members, excluding project owner and agile mentor

Common pitfalls

• Don’t impose every agile project management

element on your project: Pick and implement the

elements you feel apply best to your project

• You don’t need an official certificate to use agile

methods in your project

–

Informing yourself about the principles, elements

and general procedures of agile probably will

already be sufficient to support your team in an

agile project setting

–

Learning through practical experience is preferable

to taking a course

• Don’t force your team to apply agile methods:

Everybody in the team should be willing to adopt

agile methodology

• Ensure that roles of the project owner, agile

mentor and delivery team are clearly assigned

and that everyone understands his/her role, tasks

and responsibilities

Best practices

(9)

9

10/53140d

(10)

10

10/53140d

Scrum is not a ‘software development standard’ – it’s a

light-weight agile framework

Overview

Sprint

Daily

Scrum

Agile

Development

Team

Scrum

Master

Increment

Product

Backlog

Product

Owner

Customer

Sprint Backlog

1

2

3

4 Benefits of Scrum

• Higher productivity

• Better-quality products

• Reduced time to market

• Improved stakeholder satisfaction

• Better team dynamics

(11)

11

10/53140d

Key responsibilities

Success factors

Scrum requires 3 key roles: Product Owner

Source: Scrum alliance, A.T. Kearney

Dos:

• Manage different stakeholders

• Work closely with development team

• Involve users to test

Don’ts:

• Exert command and control

• Push too hard for more scope of sprint

Nickname: “Customer’s darling”

Product Owner

• Responsible for the successful

execution of the project

• Ensures close alignment with clients

and other key stakeholders

• Maintains project backlog: prioritizes

and refines items according to changing

client needs and progress of the project

(12)

12

10/53140d

Key responsibilities

Success factors

Scrum requires 3 key roles: Scrum Master

Dos:

• Facilitate meetings and team as “servant

leader”

• Raise impediments proactively

• Protect sprint

Don’ts:

• Stay completely away from content

Nickname: “The Coach”

Scrum Master

• Ensures that agile methodology is

understood and lived

• Supports, facilitates, coaches the

project owner and the delivery team on

agile methods

• Ensures agile process is understood

by key stakeholders

• Removes impediments to the team’s

progress

(13)

13

10/53140d

Key responsibilities

Success factors

Scrum requires 3 key roles: Development Team

Dos:

• Diverse team of 6 + max. 3 members

• Take decisions and be self-organized

• Be co-located and fully committed

Don’ts:

• Multiple part-time project commitments

Nickname: “The experts”

• Execution, development and delivery

of useable/presentable project

increments and the final project

deliverables

• Self-organized to deliver the increment

• Maintains the sprint backlog

(14)

14

10/53140d

Agile methodologies: Lean

Start-up

(15)

15

10/51450d

Lean Start-up methodology may help to increase

innovation process efficiency

Idea!

Articulate

Hypotheses

Test &

Measure

Build

Validated

Learning

Assess

Pivot

Persevere

Source: Eric Ries, “The Lean Start-up”; IMP³rove – European Innovation Management Academy, 2018

Lean start-up methodology

a

b

c

d

e

How to enhance development

processes?

Lean Start-up approach…

• …stresses rapid and iterative build-design

cycles.

• …uses customer development to test

hypothesis.

• …is based on agile development that

eliminates wasted time and resources by

developing the product iteratively and

incrementally.

• …favors experimentation over elaborate

planning, customer feedback over intuition,

and iterative design over traditional “big design

up front” development.

(16)

16

10/51450d

Product or service complexity are the critical determinants

in deciding if a company adapts the Lean Start-Up method

Operational

Risk

Product

Regulation

Component

Complexity

Products with a high degree of operational risk (e.g. nuclear power plant, jet engine) make it

less feasible to have ‘rough and ready’ products in the market as they could threaten

operational integrity or the safety of lives

Products with a stringent regulatory profile (e.g. pharmaceuticals, financial services) make it

less feasible to have very rapid experiments as stringent checks must be in place to ensure

regulations are not breached

Products that are systemically complex or have large component number (e.g. precision

engineering) make it less feasible for a build-design approach especially as development

moves beyond basic prototypes

Driver

Description

Sources: IMP³rove – European Innovation Management Academy, 2018

Drivers of lean start-up adaptation

How to enhance development

(17)

17

10/51450d

(18)

18

10/51450d

Kanban is strongly based on effective visualization of the

workflow

Benefits of Kanban

• Shorter cycle times can deliver features faster.

• Responsiveness to Change:

• When priorities change very frequently,

Kanban is ideal.

• Requires fewer organization / room set-up

changes to get started

• Reducing waste and removing activities that

don’t add value to the

team/department/organization

• Rapid feedback loops improve the chances of

more motivated, empowered and

higher-performing team members

Source: Collab.net; agilealliance.org

Values of Kanban

• Transparency

• Balance

• Collaboration

• Customer Focus

• Flow

• Leadership

• Understanding

• Agreement

• Respect

(19)

19

10/51450d

Kanban boards are frequently used to visualize progress in

a sprint

Completed

For review

In progress

Backlog

Task

8 Task

7 Task

6 Task

5 Task

4 Task

3 Task

2 Task

1

Use different colored sticky notes to visualize

responsible person

Person B

…

Person A

Phases should be tuned

to project

Example

(20)

20

10/51450d

Further information and

research

(21)

21

10/51450d

Selected sources related to agile project management and

templates available online

https://www.agilealliance.org/

https://resources.collab.net

https://docs.microsoft.com/en-

us/azure/devops/boards/work-items/guidance

(22)

22

10/53140d

(23)

23

10/53140d

Source: IMP³rove – European Innovation Management Academy, 2019

Any further

questions?

(24)

24

10/53140d

Please also check our online training calendar for up-coming training courses:

https://www.improve-innovation.eu/training-calendar/

If you are interested in organizing an in-house training, please contact us:

[email protected]

+49 211 1377 2305

Join us in one of our next training courses

Introduction to the Digital

Innovation Quotient

November 26-27, 2019 in Cluj

Napoca, Romania

Design Thinking for Better

Innovation Management

November 18—19, 2019 in Paris,

France

Action Plan Development

November 20-21, 2019 in

Dusseldorf, Germany

(25)

25

10/53140d

Thank you very much for your attention and –

have a nice weekend!

IMP³rove –

European Innovation Management

Academy EWIV

Dreischeibenhaus 1

D-40211 Düsseldorf

Germany

Tel: +49 (0)211 1377 0

Fax: +49 (0)211 1377 2999

[email protected]

www.improve-innovation.eu

About the IMP³rove – European

Innovation Management Academy

IMP³rove – European Innovation Management

Academy EWIV offers innovation management

support services to enterprises, consultants and

intermediaries.

It also provides financial actors, policy makers

and academia with consulting support and

technical assistance related to innovation and

innovation management. With its global network,

the IMP³rove Academy has set the European

standard for innovation management

assessment. The IMP³rove Academy emerged

from the European Commission's flagship

program “IMP³rove”.

It was supported by the European Commission's

Competitiveness and Innovation Framework

Programme and receives continued support by

Horizon2020.