The document discusses Agile principles and methodologies. It begins by listing the 12 principles behind the Agile Manifesto, which focus on customer satisfaction, welcoming changing requirements, frequent delivery of working software, collaboration between business and development teams, self-organizing teams, face-to-face communication, working software as a measure of progress, sustainable development, technical excellence, simplicity, and continuous improvement. It then provides an overview of common Agile methodologies like Scrum, XP, Kanban, SAFe, and Lean. The document is authored by an Agile trainer and coach with experience in Federal and commercial Agile transformations.

1. Agile Patterns and
Anti-Patterns
Are we being Agile?
August 13, 2015

2. • Agile trainer and coach
• Member of PMI, Scrum Alliance,
Agile Alliance, Agile Leadership
Network
• CST, CSM, CSPO, CSP, PMI-ACP,
PMP
• Founder & executive committee
member of Agile Delivery for
Agencies, Programs, and Teams
(ADAPT)
• Experience in Federal and
commercial Agile transformations
Richard Cheng
richard.cheng@excella.com
@RichardKCheng

3. What is Agile?

5. 1. "Our highest priority is to satisfy the customer through early and continuous delivery of valuable
software.”
2. "Welcome changing requirements, even late in development. Agile processes harness change for
the customer's competitive advantage.”
3. "Deliver working software frequently, from a couple of weeks to a couple of months, with a
preference to the shorter timescale.”
4. "Business people and developers must work together daily throughout the project.”
5. "Build projects around motivated individuals. Give them the environment and support they need,
and trust them to get the job done.”
6. "The most efficient and effective method of conveying information to and within a development team
is face-to-face conversation.”
7. "Working software is the primary measure of progress.”
8. "Agile processes promote sustainable development. The sponsors, developers, and users should
be able to maintain a constant pace indefinitely.”
9. "Continuous attention to technical excellence and good design enhances agility.”
10. "Simplicity--the art of maximizing the amount of work not done--is essential.”
11. "The best architectures, requirements, and designs emerge from self-organizing teams.”
12. "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its
behavior accordingly."
Principles Behind the Agile Manifesto:

6. 1. "Nossa maior prioridade é satisfazer o cliente através da entrega contínua e adiantada de software
com valor agregado. ”
2. "Mudanças nos requisitos são bem-vindas, mesmo tardiamente no desenvolvimento. Processos
ágeis tiram vantagem das mudanças visando vantagem competitiva para o cliente. ”
3. "Entregar frequentemente software funcionando, de poucas semanas a poucos meses, com
preferência à menor escala de tempo. ”
4. "Pessoas de negócio e desenvolvedores devem trabalhar diariamente em conjunto por todo o
projeto. ”
5. "Construa projetos em torno de indivíduos motivados. Dê a eles o ambiente e o suporte necessário
e confie neles para fazer o trabalho. ”
6. "O método mais eficiente e eficaz de transmitir informações para e entre uma equipe de
desenvolvimento é através de conversa face a face. ”
7. "Software funcionando é a medida primária de progresso. ”
8. "Os processos ágeis promovem desenvolvimento sustentável. Os patrocinadores, desenvolvedores
e usuários devem ser capazes de manter um ritmo constante indefinidamente. ”
9. "Contínua atenção à excelência técnica e bom design aumenta a agilidade. ”
10. "Simplicidade--a arte de maximizar a quantidade de trabalho não realizado--é essencial. ”
11. "As melhores arquiteturas, requisitos e designs emergem de equipes auto-organizáveis. ”
12. "Em intervalos regulares, a equipe reflete sobre como se tornar mais eficaz e então refina e ajusta
seu comportamento de acordo. "
Princípios por trás do Manifesto Ágil

7. Patterns and
Anti-Patterns

8. Agile
Scrum – Iterative method used by most teams
XP – The software engineering practices
Kanban – Often used in operations
Lean – Concepts used for organizational Agile
Agile Methodologies

9. 1. For each scenario, identify if:
– The team is making decisions guided by Agile
principles or
– The team is making decisions counter to Agile
principles
2. If the team is making decisions guided by Agile
principles, identify which principles
3. If the team is making decisions counter to Agile
principles, identify which principles conflict with the
decisions
Instructions

10. 1. Before each release, the team always seems to find themselves
behind on their work. To account for this, the team puts in many
extra hours in the weeks leading up to the release.
Antes de cada lançamento, a equipe sempre parece encontrar-se para
trás em seu trabalho. Para explicar isso, a equipe coloca em muitas
horas extras nas semanas que antecederam o lançamento.
2. The distributed team (some people in US, some people overseas)
has setup video skype accounts so everyone can use video skype
for phone calls and virtual video conference calls.
A equipe distribuída (algumas pessoas nos Brasil, algumas pessoas
no exterior) tem configuração de contas de vídeo do Skype para que
todos possam usar o vídeo do Skype para chamadas telefônicas e
chamadas de vídeo conferência virtuais.
Scenarios

11. 1. Before each release, the team always seems to
find themselves behind on their work. To account
for this, the team puts in many extra hours in the
weeks leading up to the release.
{Antes de cada lançamento, a equipe sempre parece
encontrar-se para trás em seu trabalho. Para
explicar isso, a equipe coloca em muitas horas
extras nas semanas que antecederam o lançamento.
2. The distributed team (some people in US, some
people overseas) has setup video skype
accounts so everyone can use video skype for
phone calls and virtual video conference calls.
Scenarios

12. Burndown / Burnup Charts

13. • Outcomes of Fixed Date / Fixed Scope projects:
– Waterfall
1. Delivered _____ and working ________
2. “Delivered” _____ … with ______
3. Cannot deliver on time, ______
– Scrum
1. Delivered _____ and working ________
2. The _____ items are _______ by the requested date and
working _______
• Be cautious of sacrificing quality to meet dates
Fixed Date / Fixed Scope

14. 0
200
400
600
800
1000
1200
1400
1/1/2011
2/1/2011
3/1/2011
4/1/2011
5/1/2011
6/1/2011
7/1/2011
8/1/2011
9/1/2011
10/1/2011
11/1/2011
12/1/2011
1/1/2012
Work Remaining
Work Remaining
Deadline Missed?
Project Due Date

15. 1. Before each release, the team always seems to find
themselves behind on their work. To account for this,
the team puts in many extra hours in the weeks
leading up to the release.
2. The distributed team (some people in US, some
people overseas) has setup video skype accounts so
everyone can use video skype for phone calls and
virtual video conference calls.
A equipe distribuída (algumas pessoas nos Brasil,
algumas pessoas no exterior) tem configuração de
contas de vídeo do Skype para que todos possam usar o
vídeo do Skype para chamadas telefônicas e chamadas
de vídeo conferência virtuais.
Scenarios

16. Scrum Overview
Product Vision
Roadmap
Day
Sprint…
…
…
Plan
Day
Day
Daily Scrum
Review
Retro
Sprint
Plan
Review
Retro
Idea
Initiation Release
Plan
Release Release
Plan
Plan
Time

17. 1. For each scenario, identify if:
– The team is making decisions guided by Agile principles
or
– The team is making decisions counter to Agile principles
2. If the team is making decisions guided by Agile principles,
identify which principles
3. If the team is making decisions counter to Agile principles,
identify which principles conflict with the decisions
4. Additionally, if the team is making decisions counter to Agile
principles, discuss a solution that is more aligned with Agile
principles.
Instructions

18. 3. The team is not completing all the work they thought they would
complete each iteration. The team has decided to get more work
done, they will go from 2 week iterations to 4 week iterations.
A equipa não está a concluir todo o trabalho que eles pensavam que
iria completar cada iteração. A equipe decidiu realizar mais trabalho,
eles vão a partir de 2 iterações semana a quatro semanas iterações.
4. The Product Owner has a high value change that she wants to
make weeks prior to the release. The team has decided that
though it’s breaking the agreed scope of the release, they will work
with the Product Owner to identify options for getting this change
into the release.
O Product Owner tem uma mudança de alto valor que ela quer fazer
semanas antes do lançamento. A equipe decidiu que, embora ele está
quebrando o escopo acordado do lançamento, eles vão trabalhar com
o Product Owner para identificar opções para obter esta mudança
para o lançamento.
Scenarios

19. 3. The team is not completing all the work they thought they
would complete each iteration. The team has decided to get
more work done, they will go from 2 week iterations to 4
week iterations.
A equipa não está a concluir todo o trabalho que eles
pensavam que iria completar cada iteração. A equipe decidiu
realizar mais trabalho, eles vão a partir de 2 iterações semana
a quatro semanas iterações.
4. The Product Owner has a high value change that she wants
to make weeks prior to the release. The team has decided
that though it’s breaking the agreed scope of the release,
they will work with the Product Owner to identify options for
getting this change into the release.
Scenarios

20. Product Backlog Refinement
PBI
PBI
PBI
PBI
Add
Split
Reorder
Remove
High priority
for
next Sprint
Granularity
Fine
Coarse
Product Backlog
Reorder

21. Definition of Done
Definition of Done for the PBI
Security
Testing
Browser
Tested
Stress
Testing
Acceptance
Criteria
Definition of Done for the Sprint
Definition of Done for the
Release
Unit Tested
Stakeholder
Review

22. Definition of Done
Definition of Done for the PBI
Definition of Done for the Sprint
Definition of Done for the Release
Security
Testing
Browser
Tested
Stress
Testing
Acceptance
Criteria
Unit Tested
Stakeholder
Review

23. 3. The team is not completing all the work they thought they
would complete each iteration. The team has decided to get
more work done, they will go from 2 week iterations to 4
week iterations.
4. The Product Owner has a high value change that she wants
to make weeks prior to the release. The team has decided
that though it’s breaking the agreed scope of the release,
they will work with the Product Owner to identify options for
getting this change into the release.
O Product Owner tem uma mudança de alto valor que ela quer fazer
semanas antes do lançamento. A equipe decidiu que, embora ele está
quebrando o escopo acordado do lançamento, eles vão trabalhar com o
Product Owner para identificar opções para obter esta mudança para o
lançamento.
Scenarios

24. 5. The developer has decided that instead taking extra tome to make
his code reusable when he first writes it, he decides to make the
code meet the immediate functional needs. If the code is re-used
later, then someone can update it to be re-usable.
O desenvolvedor decidiu que, em vez de tomar tomo extra para fazer
seu código reutilizável quando ele escreve, ele decide fazer o código
de atender às necessidades funcionais imediatas. Se o código for
reutilizada depois, então alguém pode atualizá-lo para ser reutilizável.
5. Business people are busy with their work and have decided to only
meet with their development team once every other week to review
the work.
Executivos que estão ocupados com o seu trabalho e decidiram
reunir apenas com sua equipe de desenvolvimento, uma vez a cada
duas semanas para rever o trabalho.
Scenarios

25. 5. The developer has decided that instead taking extra tome to
make his code reusable when he first writes it, he decides to
make the code meet the immediate functional needs. If the
code is re-used later, then someone can update it to be re-
usable.
O desenvolvedor decidiu que, em vez de tomar tomo extra para
fazer seu código reutilizável quando ele escreve, ele decide
fazer o código de atender às necessidades funcionais
imediatas. Se o código for reutilizada depois, então alguém
pode atualizá-lo para ser reutilizável.
6. Business people are busy with their work and have decided
to only meet with their development team once every other
week to review the work.
Scenarios

26. 5. The developer has decided that instead taking
extra tome to make his code reusable when he
first writes it, he decides to make the code meet
the immediate functional needs. If the code is re-
used later, then someone can update it to be re-
usable.
6. Business people are busy with their work and
have decided to only meet with their development
team once every other week to review the work.
Executivos que estão ocupados com o seu trabalho e
decidiram reunir apenas com sua equipe de desenvolvimento,
uma vez a cada duas semanas para rever o trabalho.
Scenarios

27. 7. The Program Manager has decided that rather
than disappoint the customer with incomplete
software demos, the Program Manager wants to
wait until final delivery to show the product to the
customers.
8. A small startup company is starting their software
workflow process. They have decided to use
enterprise architects to create all of the
structures, a data modeler to create all of the
data models, a senior software manager to
create all of the code designs, and the team to
write the coding details.
Scenarios

28. 7. The Program Manager has decided that rather
than disappoint the customer with incomplete
software demos, the Program Manager wants to
wait until final delivery to show the product to the
customers.
8. A small startup company is starting their software
workflow process. They have decided to use
enterprise architects to create all of the
structures, a data modeler to create all of the
data models, a senior software manager to
create all of the code designs, and the team to
write the coding details.
Scenarios

29. 7. The Program Manager has decided that rather
than disappoint the customer with incomplete
software demos, the Program Manager wants to
wait until final delivery to show the product to the
customers.
8. A small startup company is starting their software
workflow process. They have decided to use
enterprise architects to create all of the
structures, a data modeler to create all of the
data models, a senior software manager to
create all of the code designs, and the team to
write the coding details.
Scenarios

30. What is Agile?

32. 1. "Our highest priority is to satisfy the customer through early and continuous delivery of valuable
software.”
2. "Welcome changing requirements, even late in development. Agile processes harness change for
the customer's competitive advantage.”
3. "Deliver working software frequently, from a couple of weeks to a couple of months, with a
preference to the shorter timescale.”
4. "Business people and developers must work together daily throughout the project.”
5. "Build projects around motivated individuals. Give them the environment and support they need,
and trust them to get the job done.”
6. "The most efficient and effective method of conveying information to and within a development team
is face-to-face conversation.”
7. "Working software is the primary measure of progress.”
8. "Agile processes promote sustainable development. The sponsors, developers, and users should
be able to maintain a constant pace indefinitely.”
9. "Continuous attention to technical excellence and good design enhances agility.”
10. "Simplicity--the art of maximizing the amount of work not done--is essential.”
11. "The best architectures, requirements, and designs emerge from self-organizing teams.”
12. "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its
behavior accordingly."
Principles Behind the Agile Manifesto:

33. Agile Methodologies
Agile
Scrum
XP
Kanban
SAFe
DSDMLean

34. • Agile trainer and coach
• Member of PMI, Scrum Alliance,
Agile Alliance, Agile Leadership
Network
• CST, CSM, CSPO, CSP, PMI-ACP,
PMP
• Founder & executive committee
member of Agile Discovery for
Agencies, Programs, and Teams
(ADAPT)
• Deep expertise in Federal and
commercial Agile transformations
Richard Cheng
richard.cheng@excella.com
@RichardKCheng