17
DESIGNING AGILE innovating the agile team 1

Designing Agile: Innovating the Agile Team

Embed Size (px)

Citation preview

Page 1: Designing Agile: Innovating the Agile Team

DESIGNING AGILEinnovating the agile team

1

Page 2: Designing Agile: Innovating the Agile Team

Innovation is the application of disruptive thinking.

2

Page 3: Designing Agile: Innovating the Agile Team

3

ThoughtWorks Agile

ThoughtWorks agileVS

Page 4: Designing Agile: Innovating the Agile Team

4

inception

business analyst

quality analyststandard project template

being on-site 4x10s

5x8sdesigns upfront web software

cst modeldelivery mode

consulting mode

account meetings

continuous delivery

devops

offshore

nearshore

stories

roadmaps

feature mapsvertical slicing

qa as a step

ambitious missions

disruption pairingretrospectives

ipms estimation velocity lean process

value stream mapkanban

story wall

wip limitsstand ups

team celebrations mingle/jira/trello onboarding pair rotation

story splitting epics features trunk based development

feature toggling team lunch lunch and learns swimlanes

mob code review360 feedbackproject managercycle time

Page 5: Designing Agile: Innovating the Agile Team

And that’s just a small sample…

5

Page 6: Designing Agile: Innovating the Agile Team

Just like you design your software to your customers, you should design your

processes to your team

6

Page 7: Designing Agile: Innovating the Agile Team

It’s difficult. There’s no silver bullet. We have to evolve our teams over time as

we find new information.

7

Page 8: Designing Agile: Innovating the Agile Team

We have some best practices that are created by tribal knowledge.

8

Page 9: Designing Agile: Innovating the Agile Team

Tribal knowledge is biased.

9

Page 10: Designing Agile: Innovating the Agile Team

The best way to fight tribal knowledge bias is to have an outsider perspective.

10

Page 11: Designing Agile: Innovating the Agile Team

Approach what we do as a beginner. But leverage your experience to

challenge.

11

Page 12: Designing Agile: Innovating the Agile Team

12

inception

business analyst

quality analyststandard project template

being on-site 4x10s

5x8sdesigns upfront web software

cst modeldelivery mode

consulting mode

account meetings

continuous delivery

devops

offshore

nearshore

stories

roadmaps

feature mapsvertical slicingambitious missions

disruption pairingretrospectives

ipms estimation velocity lean process

value stream mapkanban

story wall

wip limitsstand ups

team celebrations mingle/jira/trello onboarding pair rotation

story splitting epics features trunk based development

feature toggling team lunch lunch and learns swimlanes

mob code review360 feedbackproject managercycle time

qa as a step

Page 13: Designing Agile: Innovating the Agile Team

13

ipms

estimation

qa as a step

Page 14: Designing Agile: Innovating the Agile Team

14

inception

business analyst

quality analyststandard project template

being on-site 4x10s

5x8sdesigns upfront web software

cst modeldelivery mode

consulting mode

account meetings

continuous delivery

devops

offshore

nearshore

stories

roadmaps

feature mapsvertical slicing

enterprise software

ambitious missions

disruption pairingretrospectives

ipms estimation velocity lean process

value stream mapkanban

story wall

wip limitsstand ups

team celebrations mingle/jira/trello onboarding pair rotation

story splitting epics features trunk based development

feature toggling team lunch lunch and learns swimlanes

mob code review360 feedbackproject managercycle time

Page 15: Designing Agile: Innovating the Agile Team

15

value stream map

360 feedback

cycle time

Page 16: Designing Agile: Innovating the Agile Team

16

Antoine de Saint-Exupéry

PERFECTION IS ACHIEVED NOT WHEN THERE IS NOTHING

MORE TO ADD, BUT RATHER WHEN THERE IS NOTHING

MORE TO TAKE AWAY

Page 17: Designing Agile: Innovating the Agile Team

what are you doing on your project?

DESIGN YOUR AGILE