agile and traditional management

36
Agile Methods Introduction Session Agile and Traditional Management Zuzi Sochova sochova.com @zuzuzka

Upload: zuzi-sochova

Post on 09-May-2015

1.153 views

Category:

Business


3 download

DESCRIPTION

Agile and Traditional Management - key differences - where we can use agile and why

TRANSCRIPT

Page 1: Agile and Traditional Management

Agile Methods

Introduction Session Agile and Traditional Management

Zuzi Sochova sochova.com @zuzuzka

Page 2: Agile and Traditional Management

What means Agile to you?

Page 3: Agile and Traditional Management

What means Agile to you?

Agile is

common sense

so don’t be disappointed

Page 4: Agile and Traditional Management

What means Agile to you?

Agile is philosophy based on people, collaboration and shared

values

Scrum, Kanban, XP,… are Processes

Page 5: Agile and Traditional Management

Different Agile Projects

Page 6: Agile and Traditional Management

Different Agile Projects

Using agile principles I’ve been: Organizing and coaching many SW teams

but as well

Leading department of 100 people Implementing HR strategy

Coaching the company business strategy Managing small startup company

Page 7: Agile and Traditional Management

Where Agile started?

Page 8: Agile and Traditional Management

Successful IT projects

The agile process is the universal remedy for software development project failure.

Software applications developed through the agile process have three times the success rate of the traditional

waterfall method and a much lower percentage of time and cost overruns.

according to the 2011 CHAOS Manifesto from the Standish Group.

Page 9: Agile and Traditional Management

Agile vs. Traditional Management

Page 10: Agile and Traditional Management

Agile ManifestoWe are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

Individuals and interactions

over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change

over following a plan

Page 11: Agile and Traditional Management

Why is Agile different?

Agile is about trust in people

while

Classical PM is often about how to control people

Page 12: Agile and Traditional Management

Why is Agile different?

Agile is good for

complex and empirical

environments

Page 13: Agile and Traditional Management

Why is Agile different?

Software development is not a predictable process. Building another house often is.

The predictable process needs a plan and control to stick to the plan and maybe adjust it a little bit when needed.

Empirical process needs good change management and creativity.

Page 14: Agile and Traditional Management

Agile Adoption

Page 15: Agile and Traditional Management

http://quotesbank.org

Agile is Change Management

Page 16: Agile and Traditional Management

http://photos3.flickr.com

Fundamental Difference

about the

View on People and Teams

Page 17: Agile and Traditional Management

http://www.questcorp.com

Learning and continuous feedback

Page 18: Agile and Traditional Management

http://www.zdn.cz

Experience your own way

Page 19: Agile and Traditional Management

Cooperation

Page 20: Agile and Traditional Management

http://larryhehn.com

Responsibility

Page 21: Agile and Traditional Management

http://theemptiness.info

Global priorities

Page 22: Agile and Traditional Management

http://abc.blesk.cz

Common Story

Page 23: Agile and Traditional Management

On-time, Fast, Flexible, Predictable

Page 24: Agile and Traditional Management

Agile and Lean Processes

used as process to any development

Page 25: Agile and Traditional Management

Agile and Lean Processes

Agile team follows an iterative process that is lightweight, highly collaborative, self

organizing, and quality focused.

Page 26: Agile and Traditional Management

Agile and Lean Processes

A lean process continuously strives to optimize value to the end

customer, while minimizing waste that may be measured in terms of

time, quality, and cost. 

Page 27: Agile and Traditional Management

Scrum Process - Basics

Page 28: Agile and Traditional Management

Work in Iterations

Page 29: Agile and Traditional Management

Team Collaboration

Page 30: Agile and Traditional Management

Communication and Self-organization

Page 31: Agile and Traditional Management

Scrum Process – Summary

Page 32: Agile and Traditional Management

Agile and PMBOK

PMBOK describes what should be done during the management of a project.

Agile methodologies describe how to do the things that should be done.

The approaches defined in the PMBOK® Guide—Fourth Edition and in agile are compatible. Agile can be

used together with the PMBOK® Guidehttp://www.pmi.org

Page 33: Agile and Traditional Management

Agile and PMI – Scrum exampleInitialization

• Same

Planning

• Scrum–like process, iterative functionality planning, adjust scope according to the customer feedback • how we communicate, organize team, roles

Execution

• Every iteration customer demo

Monitoring

• Retrospective, Sprint review

Closing

• Same • Acceptance every iteration

Page 34: Agile and Traditional Management

SummaryAgile principles are generally used to any complex empirical projects:

Incorporate change (process, product) Implement Short Iterations Endorse self-organization

 High collaboration Transparent Communication

Continuous Learning Quality Driven

Page 35: Agile and Traditional Management

Summary

Agile processes are used inside

project management

Page 36: Agile and Traditional Management

Zuzana Šochová, [email protected]

AGILE & SCRUM TRAINER, CONSULTANT AND COACH Personal web: http://sochova.com English blog: http://tulming.com Czech blog: http://soch.cz/blog Travel blog: http://asmat.eu Twitter: @zuzuzka