“Como Escalar Práticas Ágeis em Equipes de Desenvolvimento Médias e Grandes”

®
IBM Software Group
© 2013 IBM Corporation
Como Escalar Práticas Ágeis em Equipes
de Desenvolvimento Médias e Grandes
Andrea Rodacki
arodacki@br.ibm.com
Siga-me no Twitter e LinkedIn (arodacki)

IBM Software Group | Rational software
Innovation for a smarter planet
A Fábula dos Lenhadores
2
https://www.ibm.com/developerworks/community/blogs/rationalbrasil/entry/a_f_c3_a1bula_dos_lenhadores10?lang=em

Base do Desenvolvimento de Software
3
Pessoas
Processos
Ferramentas

What is agile?
Agile is a highly collaborative,
evolutionary, quality focused
approach to software
development.

Innovation for a smarter planet 5
Agile values
Working
Software
Working
Software
Individuals
Interactions
Individuals
Interactions
Customer
Collaboration
Customer
Collaboration
Source: www.agilemanifesto.org
Comprehensive
Documentation
Comprehensive
Documentation
Processes
and Tools
Processes
and Tools
Following
a Plan
Following
a Plan
Contract
Negotiation
Contract
Negotiation
overWe value
While there is value in the items on the right, we value
the items on the left more.
Responding
to Change
Responding
to Change

Waterfall X Agile
6

Why Agile Rocks (1/2)
Speed to market
Agile lets you get your concept to your users as quickly as possible. During every
sprint an agile project delivers something of value. At any point, you may determine you
want to launch what has been delivered and start building a user base or testing your
hypothesis.
Flexible
Agile is based on accommodating change. Software projects consistently change. As a
product comes to life or the market expands, you should be able to react and update the
product accordingly. Agile also realizes that great ideas are bound to come mid-project
and being locked into a scope doesn’t let you take advantage of these realizations.
Risk Management
Incremental releases means that the product can be used early in the process by
stakeholders and users. This lets you identify issues and feature deficits early in the
process. Being adaptable to change means it isn’t a problem to change the scope
midway through the project, something that would be impossible in a waterfall style
project.
7

Why Agile Rocks (2/2)
Cost Control
Unlike a fixed budget project, agile is flexible with regard to scope. More often than not,
our clients realize features they originally requested are no longer necessary. This allows
them to launch sooner and pay less. Agile isn’t about paying a lot with uncertainty, it’s
about paying for only what you need. Need to stick within a budget? No problem! We can
rearrange the product backlog so that critical new features are implemented at the
expense of less important features, not your budget.
Quality
Agile integrates testing throughout the process. Consistently delivering tested software
means higher overall quality and less time spent on QAing the full application.
Right Product
Incremental releases let you test your product early and often. Even if you don’t release it
to the public, it’s much easier to locate flaws and things that can be improved when
you have an actual product to play with vs a series of designs.
Transparency
Agile lets you see, feel and use a project consistently throughout the project. You don’t
see things in compartmentalized silos; you see how things work together.
8

Os Diversos “Sabores” Ágeis
9

Agile Umbrella
10
LEAN
Agile Modeling (AM) Unified Process (UP)
Agile Data (AD)

Is it enough?
It works for small, collocated teams, but does it work for bigger,
geographically distributed teams?
Does it work for outsourcing scenarios?
Does it work in highly regulated or complex business domains (e.g.,
financial, medical, air traffic control, ..)?
Does it work for enterprise aware organizations?
Does it cover the entire delivery lifecycle?
12

13
Agile
Scaling
Model
(ASM)
Core Agile Development
Focus is on construction
Goal is to develop a high-quality system in an evolutionary,
collaborative, and self-organizing manner
Value-driven lifecycle with regular production of working
software
Small, co-located team developing straightforward software
Disciplined Agile Delivery
Extends agile development to address full system lifecycle
Risk and value-driven lifecycle
Self organization within an appropriate governance
framework
Small, co-located team delivering a straightforward solution
Agility at Scale
Disciplined agile delivery and one or more scaling factors
applies

Agile Scaling Model (ASM) – simplified view
14
Core Agile
Development
Disciplined Agile
Delivery
Agility at Scale
Core Agile Development
Value driven lifecycle
Self organizing teams
Focus on construction
Disciplined Agile Delivery
Risk + value driven lifecycle
Self organizing within appropriate
governance framework
Full delivery lifecycle
Agility at Scale
DAD when one or more scaling factors apply:
Large team size
Geographic distribution
Regulatory compliance
Domain complexity
Organization distribution
Technical complexity
Organizational complexity
Enterprise discipline

What is disciplined agile delivery?
15
“The Disciplined Agile Delivery (DAD) process
framework is a people-first, learning-oriented
hybrid agile approach to IT solution delivery. It
has a risk-value life cycle, is goal-driven, and is
enterprise aware.”
DAD is NOT prescriptive nor a “one size
fits all” approach

Agile e Lean
16
• Agile – Entregue VALOR
– Uma abordagem que foca em entregar elementos de valor para o
cliente
– Evite tudo que não traz valor
– Descrença em planos detalhados logo no início do projeto
• Lean – Evite DESPERDÍCIO
– Inicialmente, uma iniciativa gerencial para agilizar
a produção
– Elimine todos os desperdícios
– Inventário reduzido
http://www.rallydev.com/community/agile-blog/agile-and-lean-software-development---oxymoron

Disciplined Agile Delivery (DAD): A Hybrid
Framework
Unified Process
(UP)
Extreme
Programming (XP)
Scrum
Agile
Modeling
Disciplined Agile
Delivery (DAD)
DAD is a hybrid process framework adopt best practices
and philosophies from several methodologies

DAD & AM, UP, AD
Agile Modeling (AM)
DAD models its documentation practices after requirements envisioning,
architecture envisioning, iteration modeling, continuous documentation, and just-in-
time (JIT) model storming.
Unified Process (UP)
DAD adopts several governance strategies from UP: having lightweight
milestones and explicit phases and focusing on the importance of proving out the
architecture in the early iterations and reducing all types of risk early in the life
cycle.
Agile Data (AD)
DAD adopts several agile database practices from AD: database refactoring,
database test-in, and agile data modeling. It is also an important source of
agile enterprise strategies, such as how agile teams can work effectively with
enterprise architects and enterprise data administrators.
18

DAD e Extreme Programming
19
DAD XP
Abordagem gerencial Técnicas de engenharia
Foco no ciclo de vida e nos
objetivos
Foco nas práticas
Inclui princípios do XP
(CI, refactoring, TDD, collective ownership)
Primeira abordagem ágil a ganhar
espaço
Abrange todo o ciclo de vida Foco na construção

DAD e Kanban
20
DAD Kanban
Agrega práticas de diversos
processos ágeis
Poucos
princípios/objetivos/práticas
Fala especificamente de
governança
Depende de governança adequada
a Kanban
Framework de processo específico
para desenvolvimento de software
Abordagem evolutiva de melhoria
de processos
Práticas definidas Kaizen
DAD adopts two critical concepts from Kanban:
limiting work in progress and visualizing work.

DAD e SCRUM
21
DAD Scrum
Ciclo de vida completo Focado em construção
Enterprise aware No vácuo
Arquitetura como mitigadora de
riscos
Arquitetura emergente
Implantação evolutiva Implantação monolítica
(mais ou menos...)
? Evangelistas revolucionários

The Scrum construction lifecycle
Operate in
Production?
Enterprise
Disciplines?
Project
Selection?

The Disciplined Agile Delivery (DAD) life cycle
Operate in
Production
Enterprise
Disciplines
Project
Selection

Agile Scaling Factors
Checklist of issues that you should consider and will affect
significantly your project
Not every project team faces all of these scaling factors, nor do
they face each scaling factor to the same extent
These issues add complexity to your situation and you must find
strategies to overcome these challenges

Agile scaling factors
Domain Complexity
Straight
-forward
Intricate,
emerging
Compliance requirement
Low risk Critical,
audited
Team size
Under 10
developers
1000’s of
developers
Co-located
Geographical distribution
Global
Enterprise discipline
Project
focus
Enterprise
focus
Technical complexity
Homogenous
Heterogeneous,
legacy
Organization distribution
(outsourcing, partnerships)
Collaborative Contractual
Disciplined
Agile
Delivery
Flexible Rigid
Organizational complexity

How IBM saved $300 million by going agile
“Who Says Elephants Can’t Dance” is the title of former IBM CEO Lou Gerstner’s
book on IBM’s dramatic transformation in the 1990s.
Sure, everyone used to think of IBM as the “elephant” (large and powerful, but also
sluggish and slow) of the computing industry.
But as software gained a larger share of IBM’s focus, the business became much
more agile, capable of growing along with the expanding ecosystems of the Internet
and worldwide commerce.
I think the SWG move to agile methods makes a nice addendum to that ongoing
success story!
Gina Poole
VP of Marketing, IBM Rational
26ASSITA AO VIDEO EM http://bit.ly/IBM-agile-legendado

Esclarecendo alguns mitos sobre Ágil
27
Equipes ágeis escrevem documentação
Equipes ágeis fazem modelagem
Equipes ágeis (e não só gerentes) planejam tanto quanto equipes tradicionais
(just-in-time) ou mais
Projetos ágeis são mais previsíveis do que projetos tradicionais
Ágil escala
Ágil não é moda, nem revolução do proletariado
Ágil pode trabalhar com projetos de preço fixo
Ágil está sendo usado “criativamente”

Conclusion
There is more to agile than software development
Disciplined Agile Delivery (DAD) is a hybrid process framework adopt context-
driven practices and philosophies from several methodologies
Full lifecycle
Includes supporting practices
Focused on solutions, not just software
Self organizing with appropriate governance
First step to scaling agile is to have a viable delivery process

www.iset.srv.br/iset/curso_agil.html
80 horas (sábados: 9h às 12h e 13h às 18h)
Início 3/ago - Fim 19/out
Módulos:
O Desenvolvimento Ágil – 24 horas/aulas
Desenvolvendo Software com IBM Rational Team Concert – 8 horas/aulas
Iniciando um Projeto Ágil com IBM Rational Team Concert – 24 horas/aulas
Simular um Projeto Ágil no IBM Rational Team Concert – 24 horas/aulas
Material oficial IBM
Prova de Certificação IBM/Prometric
"Test 53: Rational Team Concert V3"
incluída no valor do curso
CURSO
DESENVOLVIMENTO ÁGIL E COLABORATIVO
COM CERTIFICAÇÃO IBM RATIONAL TEAM CONCERT
29

Siga-me no Twitter e LinkedIn (arodacki)

Referências (1/2)
Canal IBM Rational Brasil no YouTube bit.ly/RationalBrasil-YouTube
Canal Plafaforma Jazz no YouTube bit.ly/PlataformaJazz-YouTube
Blog da Rational Brasil - O Mundo depende de software ibm.co/blogRationalBrasil
Grupo Rational Brasil no LinkedIn http://www.linkedin.com/groups/Rational-Brasil-
3679473?trk=myg_ugrp_ovr
Livro Agile for Dummies http://www-01.ibm.com/software/rational/agile/
DAD – Discipline Agile Delivery
Pagina principal http://disciplinedagiledelivery.wordpress.com/introduction-to-dad/
Blog
https://www.ibm.com/developerworks/mydeveloperworks/blogs/ambler/entry/disciplined_a
gile_delivery_dad_lifecycle14?lang=en
Paper
http://public.dhe.ibm.com/common/ssi/ecm/en/raw14261usen/RAW14261USEN.PDF
Process Templates for use with Rational Team Concert http://www-
01.ibm.com/support/docview.wss?uid=swg24028581
Certificações http://disciplinedagileconsortium.org/directory
31

Referências (2/2)
Rational Team Concert
Conheça a Solução Rational Team Concert:
http://www.youtube.com/watch?v=dg9e4mk6nGs
Rational Team Concert e Plataforma Jazz https://jazz.net/products/rational-team-concert/
Vídeo de Instalação do RTC http://www.youtube.com/watch?v=VNJUi6PYSIQ
Webcast Replay (em português): Desenvolvimento Ágil e Rational Team Concert
https://www.ibm.com/developerworks/mydeveloperworks/blogs/rationalbrasil/entry/webcas
t_replay_desenvolvimento__c3_a1gil_e_rational_team_concert3?lang=en ou
http://www.youtube.com/watch?v=tJZvDPqocpw
SCRUM no RTC http://www.ibm.com/developerworks/rational/library/scrum-methods-
rational-team-concert-v4-1/ e http://www.ibm.com/developerworks/rational/library/scrum-
methods-rational-team-concert-v4-2/
Recursos Técnicos http://www.ibm.com/developerworks/rational/products/rtc/
Sandboxes: Try now in a web-based trial environment
https://jazz.net/products/sandbox/
32

“Como Escalar Práticas Ágeis em Equipes de Desenvolvimento Médias e Grandes”

“Como Escalar Práticas Ágeis em Equipes de Desenvolvimento Médias e Grandes”

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à “Como Escalar Práticas Ágeis em Equipes de Desenvolvimento Médias e Grandes”

Similaire à “Como Escalar Práticas Ágeis em Equipes de Desenvolvimento Médias e Grandes” (20)

Dernier

Dernier (20)

“Como Escalar Práticas Ágeis em Equipes de Desenvolvimento Médias e Grandes”