Top Banner
Agile adj 1. quick in movement; nimble 2. mentally quick or acute
79

Agile explained

Jan 23, 2018

Download

Technology

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Agile explained

Agileadj

1. quick in movement; nimble

2. mentally quick or acute

Page 2: Agile explained

Figaroplanomaníaco, cinéfilo,cinófilo,articulista, palestrante,agilista escifimaníaco (ok, essa eu inventei…)

Page 3: Agile explained

Problems with traditional software

development

photo by Jule_Berlin

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 4: Agile explained

Traditional

Phased development

Anticipated results

Up-front design

picture by jasonb42882 Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 5: Agile explained

Requirements Not Clear

Fear to go to the next phase

Analysis paralysis

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 6: Agile explained

Requirements Change

Change gets more and more expensive

Customers don’t get what they want

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 7: Agile explained

Project Takes Too Long

32% of projects delivered successfully

Long duration defers revenue

(Source: Standish Report 2009)

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 8: Agile explained

No Time for Testing

Quality assurance gets crunched

Late integration means late failures

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 9: Agile explained

Time Wasted on Junk

52% of requirements implemented

64% of functionality rarely used

(Source: Standish Report 2003)

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 10: Agile explained

Poor Progress Visibility

% Task complete not sufficient

Average overrun 43%

(Source: Standish Report 2003)

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 11: Agile explained

Agile software

development

Page 12: Agile explained

12

Page 13: Agile explained
Page 14: Agile explained

14

Page 15: Agile explained

15

Page 16: Agile explained

16

Page 17: Agile explained

17

Page 18: Agile explained

18

Page 19: Agile explained

19

Page 20: Agile explained

20

Page 21: Agile explained

21

Page 22: Agile explained

22

Page 23: Agile explained

23

Page 24: Agile explained

24

Page 25: Agile explained

25

Page 26: Agile explained

26

Page 27: Agile explained

Values

Scrum

KanbanXP

Crystal

FDD

Principles

Seu Processo…

Page 28: Agile explained

Design Thinking

viability

feasibility desirability

Page 29: Agile explained

Lean Startup

ideas

product data

measure

Page 30: Agile explained

Kanban

Page 31: Agile explained

Scrum

picture by Kiwi Flickr

Page 32: Agile explained

The Gurus

Ken Schwaber

Jeff Sutherland

Mike Beedle

Mike Cohn

Page 33: Agile explained

The Goal of Scrum

Manage Complexity, Unpredictability and Change

through Visibility, Inspection and Adaptation

picture by OnTask

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 34: Agile explained

Scrum Roles

picture by exfordy

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 35: Agile explained

Product Owner

Owner of project vision Represents the customer

picture by Official Star Wars Blog Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 36: Agile explained

The Team

Small (5–9 people)

Colocated - Cross-functional

Self-organized - Full-time picture by ewen and donabel

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 37: Agile explained

Scrum Master

Servant leader

Team protector

Troubleshooter

Scrum guide

picture by Orange Beard

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 38: Agile explained

Scrum Process

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 39: Agile explained

Product Backlog

Express value

Defer decisions

picture by juhansoninAppelo, Jurgen, The Zen of Scrum, Slideshare.

Page 40: Agile explained

Product Backlog

Owned by Product Owner

High-level requirements

Expressed as business value

Not complete, nor perfect

Expected to change & evolve

Limited view into the future

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 41: Agile explained

Sprints

Steady pull of business value

Inspect and Adapt picture by kelsey e.

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 42: Agile explained

Sprint Planning

Face-to-face communication

Small reversible steps

User’s perspective

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 43: Agile explained

Sprint Backlog

Breakdown of business value into

assignable tasks

picture by oskay

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 44: Agile explained

Daily Scrum

The heartbeat of Scrum picture by Hamed Saber

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 45: Agile explained

Task Board picture by Mountain Goat Software

Sprint

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 46: Agile explained

Sprint Burn Down

picture by NibiruTech

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 47: Agile explained

Sprint Review

Satisfy Product Owner

Get feedback on product picture by oskay

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 48: Agile explained

Sprint Retrospective

Evolve the process

picture by kevindooley

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 49: Agile explained

Burn Up Chart

Scope keeps expanding

Pipeline gets fatter

Appelo, Jurgen, The Zen of Scrum, Slideshare.

Page 50: Agile explained

So, what should managers do to be Agile?

Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 51: Agile explained

Management is about human beings. Its task is to

make people capable of joint performance […]. This is what

organization is all about, and it is the reason that management is the critical, determining factor.

Management: Revised Edition, 2008

Peter F. Drucker

9 Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 52: Agile explained

Management is too important to be left to the

managers.

10 Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 53: Agile explained

Manage like a gardener

Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 54: Agile explained

Man

agem

ent

3.0

11 Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 55: Agile explained

People are the most important parts of an organization and

managers must do all they can to keep people active, creative, and

motivated.

20 Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 56: Agile explained

10 Intrinsic DesiresCuriosity The need to think

Honor Being loyal to a group

Acceptance The need for approval

Mastery / Competence The need to feel capable

Power The need for influence of will

Freedom / Independence / Autonomy Being an individual

Relatedness / Social Contact The need for friends

Order Or stable environments

Goal / Idealism / Purpose The need for purpose

Status The need for social standing

21 Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 57: Agile explained

1. Put the motivator cards in order, from unimportant to important

2.(You may leave out any cards you don’t want to use.)

Exercise: Moving Motivators

22 Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 58: Agile explained

3. Consider an important change in your work (for example, becoming a more Agile organization)

4. Move cards up when the change is positive for that

motivator; move them down when the change is negative

Exercise: Moving Motivators

positive change

negative change 23 Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 59: Agile explained

Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 60: Agile explained

Teams can self-organize, and this requires empowerment,

authorization, and trust from management.

25 Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 61: Agile explained

1. Tell: make decision as the manager

2. Sell: convince people about decision

3. Consult: get input from team before decision

4. Agree: make decision together with team

5. Advise: influence decision made by the team

6. Inquire: ask feedback after decision by team

7. Delegate: no influence, let team work it out

The Seven Levels of Authority

Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 62: Agile explained

Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 63: Agile explained

Self-organization can lead to anything, and it’s therefore necessary to protect people

and shared resources…

…and to give people a clear purpose and defined goals. 28 Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 64: Agile explained

Teams cannot achieve their goals if team

members aren’t capable enough, and

managers must

therefore contribute to the development of

competence. 33 Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 65: Agile explained

Support emerging creativity. 2012 Jurgen Appelo, taken at Cisco SystemsNorway, Oslo Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 66: Agile explained

Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 67: Agile explained

Many teams operate within the context of a complex organization, and thus it is important to consider structures that enhance communication.

36 Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 68: Agile explained

Informal structures.

2012 Elliott Brown, Creative Commons 2.0, http://www.flickr.com/photos/ell-r-brown/4436513664Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 69: Agile explained

Value units

System administrators

GUI designers

Project Mgt Office

Community of Practice

Center of Excellence

Human Resources

...

Delivering value to others

Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 70: Agile explained

People, teams, and organizations need to

improve continuously to defer failure for as long

as possible.

39 Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 71: Agile explained

Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 72: Agile explained

The Management 3.0 model

Six organizational views based on complexity thinking

Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 73: Agile explained

86

Cool….but where can I use Agile?

Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 74: Agile explained

Process Complexity (M)

Agile projects

Chaotic projects

Structured projects

Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 75: Agile explained

88Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 76: Agile explained

89Appelo, Jurgen, Management 3.0 in 50 minutes, Slideshare.

Page 77: Agile explained

90

Page 78: Agile explained

picture by -bast-

Q & A

Page 79: Agile explained

@lfigaro

pt.slideshare.net/luisffigaro

linkedin.com/in/lfigaro

[email protected]