Agile Basics for Software Development ( Agnostic Framework )

1. DevOps - Agile
Use a picture. It's worth a thousand words.
Tess Flanders
Miguel Rodrigues
miguel.rodrigues.devops@gmail.co
m

2. Traditional – Workflow to Add Value
Idea
( Product or Service) Team
Owner
Formal Specifications Delivery
Expected Time
t
Expected
time
Formal
Spec. Expected
time
Require
ments t
0
Require
ments t
1

3. Traditional – Workflow – Why it is not the best
aproach
Idea
( Product or Service) Team
Owner
Formal Specifications
Project
Work Delivery
Expected Time
t
Expected
time
Formal
Spec. Expected
time
Require
ments t
0
Require
ments t
1
Idea
may
change
Long
and
costly
Unverified team
Mistakes
Unclear
Specs
Absent from day2day
decisions and problems

4. Agile – Workflow – BackLog – Formal
Specifications
Idea
( Product or Service)
Team(part) Owner
Enlarged Team
User Story
1
..
.User Story
N
Idea
( Product or Service)
BackLog
Formal Specifications
xxxx
t
Require
ments t
0
User Story
1
..
.
User Story
N

5. Agile – Workflow – Sprint – Project Work
Team Owne
r
Enlarged Team
User Story
1
..
.User Story
N
BackLog
Sprint 1
Team Owne
r
Enlarged Team
Sprint 2
Team Owne
r
Enlarged Team
Sprint N
..
.
User Story
1
User Story
M..
.
User Story
M+1
User Story
K..
.
User Story
M+1
User Story
K..
.
Project
Work
xx
New User Story

6. Agile – Workflow – Sprint – Incremental Add
Value
Sprint 1 Sprint 2 Sprint N
User Story
1
User Story
M..
.
User Story
M+1
User Story
K..
.
User Story
M+1
User Story
K..
.
t
User Story
Z
Sprint M
Require
ments t
1

7. Agile – Workflow – Relax Time – Delivery
Team Owne
r
Enlarged Team
Sprint 1
Team Owne
r
Enlarged Team
Sprint K
User Story
1
User Story
M..
.
User Story
M+1
User Story
K..
.
..
.
Has Owner is inside the
Team and aproves
The user Story Delivery
all the User Stories are delivered
at the end of each sprint

8. Q&A
Miguel Rodrigues
miguel.rodrigues.devops@gmail.co
m