This document summarizes an agile project using Scrum methodology to develop a system to integrate and manage natural gas pipelines over multiple sprints. The project used feature teams composed of a Scrum Master, architect, tester, and four developers. Each two-week sprint included daily stand-ups, metrics tracking, code reviews, and releases at the end of each sprint. Kanban boards were used to visualize the workflow from product backlog to development to testing and release. Future improvements proposed included building a business knowledge base, reducing story/feature sizes, limiting work-in-progress, and reducing architectural and infrastructure complexity.

1. Agile Trends 2016
Show me your board!
abril/2016

2. Contexto

3. *Fonte: Statista.com, julho de 2015
4.000.000de apps nas stores
*
Cliente Projeto Times
EUA Líder setor
Óleo & Gás
67
2013 Sprint 0
1 Solution Team
(BRA/EUA)
Mil Km de
pipelines
Sistema para integrar
pipelines e gerenciar o
transporte de gás natural.
1 Support Team
(EUA)
6 Dev Teams
(BRA)
70 pessoas

4. ● Scrum
● Feature Team
● Sprints sincronizados
● Composição
o 1 SM
o 1 Arq
o 1 Tester
o 4 Devs
Dev Teams

5. Timebox e
Ritos

6. Sprint 1 Sprint 2
ETE
R
E
L
E
A
S
E
Sprint 3 Sprint 4
ETE
R
E
L
E
A
S
E
2 semanas
1 mês

7. Daily

8. Métricas Bug Root Cause &
Code Review Findings

9. Value
Stream

10. Product
Backlog
Discovery
Solution
Design
Development Tests
PO
Acceptance
Analysis Release
Value Stream
• Epics,
features
• Detalhamento
negócio
• Priorização
• Arch Design
• User stories
• Unit Test
• Specflow (code)
• Implentação
• Incremental Test
• Desk check
• QA
• TP
• Exp
• UAT• Acceptance Criteria
• Tech Analysis
• Test Plan,
Specflows (feature)
• Go live
Solution Team Dev Teams

11. Boards

12. Product
Backlog
Discovery Solution
Design
Prioritize for
Analysis
Ready for
Developme
nt
In
Development
Awaiting
Test
In Tests In PO
Acceptance
In Analysis Awaiting
Production
In Production
Story Board

15. Product
Backlog
Discovery Solution
Design
Prioritize for
Analysis
Ready for
Developme
nt
In
Development
Awaiting
Test
In Tests In PO
Acceptance
In Analysis Awaiting
Production
In Production
Task
Board

17. Métricas

24. Improvement
Propostas futuras
Construir business knowledge base
Diminuir o lote (user stories)
Limitar WIP
Diminuir complexidade arquitetural e de infra

25. Product Success
rodrigosilvap@gmail.com
https://br.linkedin.com/in/rodrigosilvap
Obrigado!