Slide 1

Slide 1 text

Enterprise Agile Valores das metodologias ágeis Programa Mindsets | setembro 2018

Slide 2

Slide 2 text

why AGILE?

Slide 3

Slide 3 text

new approach for new challenges

Slide 4

Slide 4 text

instead avoid changes, promote pivot it

Slide 5

Slide 5 text

imagine a waterfall approach for small plantation. preparing the garden TOMATOES BEANS ORANGE time 1 week

Slide 6

Slide 6 text

adding fertilizer time TOMATOES BEANS ORANGE 1 week 2 weeks

Slide 7

Slide 7 text

adding seeds time TOMATOES BEANS ORANGE 1 week 2 weeks 3 weeks

Slide 8

Slide 8 text

agile approach. preparing the garden time TOMATOES BEANS ORANGE 1 week

Slide 9

Slide 9 text

adding fertilizer time TOMATOES BEANS ORANGE 1 week

Slide 10

Slide 10 text

adding seeds time TOMATOES BEANS ORANGE 1 week

Slide 11

Slide 11 text

comparing time time READY FOR GROWING WHAT IF BEAN IS WORTHING? agile waterfall READY FOR GROWING ROOM FOR PIVOTING 1 week 2 weeks 3 weeks mvp

Slide 12

Slide 12 text

AGILE MANIFESTO Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan

Slide 13

Slide 13 text

common problems BAD REQUIREMENTS UNREALISTIC DEADLINES CHANGING PRIORITIES LACK OF COMMUNICATION QUALITY ASSURANCE PM RUNNING SEVERAL PROJECS LACK OF VISION

Slide 14

Slide 14 text

before DIGITAL TRANSFORMATION

Slide 15

Slide 15 text

do BUSINESS TRANSFORMATION

Slide 16

Slide 16 text

understand your CULTURE, the way to get job done

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

control competence collaboration cultivation SCHNEIDER

Slide 19

Slide 19 text

each CULTURE needs an adaptive enterprise agile FRAMEWORK

Slide 20

Slide 20 text

SCRUM LEAN KANBAN XP LESS SAFE DAD lightweight approaches fuller approaches AGILE

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

LEAN STARTUP ideas code data build learn measure minimum viable product aka MVP “version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort” Eric Ries, LEAN STARTUP

Slide 23

Slide 23 text

KANBAN beginning design the map workflow processes new estimate done control

Slide 24

Slide 24 text

define roles, move to SCRUM

Slide 25

Slide 25 text

SCRUM foundation all-in-once self organized team SCRUM MASTER PRODUCT OWNER DELIVERY TEAM SMALL TEAM 7 coach the framework foster control manager vision backlog delivery interface developers testers ux cultivation colaboration

Slide 26

Slide 26 text

SCRUM backlog PRODUCT OWNER direct contact to the client USER STORIES user language prioritization dev translation PRODUCT BACKLOG dev language READY TO USE ready definition 1 to 2 weeks sprint As do when . + acceptance criteria

Slide 27

Slide 27 text

DELIVERY TEAM SCRUM estimations estimate the durations of tasks (max 1/day) PRODUCT BACKLOG allocation together with PO: sprint planning SPRINT PLANNING POKER T-SHIRT SIZES BUCKET SYSTEM RETROSP ECTIVE

Slide 28

Slide 28 text

SCRUM board backlog to-do doing done

Slide 29

Slide 29 text

LARGE SCALE SCRUM aka LESS competence multiples teams at same scrum 2 to 8 teams PO/product and PO/area unique sprint across teams 2 sprint planning: ready and ship/plan

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

https://less.works/less/framework/index.html

Slide 32

Slide 32 text

DISCIPLINED AGILE DELIVERY aka DAD cultivation created by IBM Rational architecture view at the beginning primary roles: stakeholders, PO, team member, team lead, architecture owner BoK model (best practices)

Slide 33

Slide 33 text

http://www.disciplinedagiledelivery.com

Slide 34

Slide 34 text

EXTREMING PROGRAMING aka XP cultivation competence technical approach small releases acceptance tests test driven design (tdd) refactoring pair programing

Slide 35

Slide 35 text

SCALED AGILE FRAMEWORK aka SAFE control template to build agile to scale PORTFOLIO VALUE STREAM PROGRAM TEAM portfolio of projects product value stream, why people use our product? epics creation projects coordination delivery STRATEGY SPRINT OF SPRINTS: ART SCRUM, SCRUMXP & KANBAN

Slide 36

Slide 36 text

https://www.scaledagileframework.com

Slide 37

Slide 37 text

SPOTIFY APPROACH aka SQUADS unbundle your product into small auto-sufficient parts, squads and tribes put them together to share experiences, chapters and guilds cultivation collaboration

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

PLAYLIST SQUAD PLAYER SQUAD MENU SQUAD DEFAULT SQUAD product owner agile coach tester dev designer

Slide 40

Slide 40 text

product owner agile coach tester dev designer product owner agile coach tester dev designer product owner agile coach tester dev designer squad

Slide 41

Slide 41 text

tribe product owner agile coach tester dev designer product owner agile coach tester dev designer product owner agile coach tester dev designer

Slide 42

Slide 42 text

chapter product owner agile coach tester dev designer product owner agile coach tester dev designer product owner agile coach tester dev designer

Slide 43

Slide 43 text

guilds product owner agile coach tester dev designer product owner agile coach tester dev designer product owner agile coach tester dev designer

Slide 44

Slide 44 text

https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/

Slide 45

Slide 45 text

No content

Slide 46

Slide 46 text

“before scale it, nail it”

Slide 47

Slide 47 text

No content