Post on 13-Jul-2020
Manage a project portfoliopeople processes tools
Who am I?
Michele Orselli
CTO@Ideato @_orso_mo@ideato.it
we love open source
from idea...
to product!
sofware projects are challenging
sofware projects are challenging
Who’s first? How much time project X needs? When project Y will end?Are we on time?Are we on budget?
sofware projects are challenging
How can we manage a project portfolio?
our journey
1) early days2) growing 3) today4) tomorrow
foundations: agile manifesto
xp: pair programming
xp tdd
xp: YAGNI
foundations: extreme programming
If integration testing is important, then we'll integrate and test several times a day (continuous integration).
our journey
1) early days2) growing 3) today4) tomorrow
the early days
new projectsalmost no support/maintenance
the early days
devsops
no UX / Design
scenario
a new project lifecycle
us
scenario
scenario usus
ideabusiness
objectives
usus
usus
usususususususProduct Backlog
iteration meeting
usususususususProduct Backlog
iteration meeting
usususus Product Backlog
ususus Prioritization
iteration meeting
usususus Product Backlog
ususus Planning
Iteration 1
ususus
Iteration
iteration based flow
pair A Iteration 1 Iteration 2 Iteration n...
release release release
planning planning planning
a new project lifecycle
Velocity:120 pts total20 pts closed--> 6 iterations
Burndown chartIteration x
ususus
a new project lifecycle
Leave room for:
Iteration x
ususus
Bugs b
Emergencies e
what about 2 projects?
pair A Iteration 1 Iteration 2 Iteration n...
pair B Iteration 1 Iteration 2 Iteration n...
every day: stand up meetings
Rules:
- 10/15 minutes- yesterday- tomorrow- roadblock
hitting max capacity
pair A Iteration 1 Iteration 2 Iteration n...
pair B Iteration 1 Iteration 2 Iteration n...
Iteration 1
hitting max capacity
pair A Iteration 1 Iteration 2 Iteration n...
pair B Iteration 1 Iteration 2 Iteration n...
Iteration 1
Iteration 2
context switch kills productivity
time to market
pair A I 1 I 1 I 2 I 2 I 3 I 3 I 4 I 4
pair B I 1 I 1I 2 I 2I 3 I 3I 4 I 4
* *
**
bottlenecks
devsops
no UX / Design
our journey
1) early days2) growing 3) today4) tomorrow
old & new
new incoming projects“old” projects in maintenance
old & new
Rules:
- no 100% pair- no iteration- fifo
er
pair A Iteration 1 Iteration 2 Iteration n...
pair B Iteration 1 Iteration 2 Iteration n...
ER t t t t t t ...
er
iteration based project planning doesn’t change
Emergency room prj task pts
a task 1 2
b task 2 1
c task 3 0.5
c task 4 3
d task 5 5
a task 6 1
our journey
1) early days2) growing 3) today4) tomorrow
what we learned
context switch is bad iterations: performance +, react -er (flow): performance -, react +
split team
devs
ops
ux
devs
trello
kanban board
todo (10) working (4) qa (2) deploy (2) done
1 backlog per project
usususususususProject A
usususususususProject D
usususususususProject B
usususususususProject C
1 backlog per project
id status User Stories / Task Pts Details
3455 Task 1 0.5
3466 User Story 1 1
3243 Task 2 2
6545 Task 3 3
6578 Task 4 1
7654 User Story 2 1
1234 User Story 3 5
4325 0.5
weekly planning
week # id Project Task Pts Effort
21 3455 A 14
21 3466 A
21 3243 A
21 6545 C task: go live with new homepage 0.5
21 6578 C
20 8978 B Task I 1 20
20 7654 B User Story 1 0.5
20 1234 C Task 3
20 4325 A Task 2
weekly planning
week # id Project Task Pts Effort
21 3455 A 14
21 3466 A
21 3243 A
21 6545 C task: go live with new homepage 0.5
21 6578 C
20 8978 B Task I 1 20
20 7654 B User Story 1 0.5
20 1234 C Task 3
20 4325 A Task 2
weekly planning
week # id Project Task Pts Effort
21 3455 A 14
21 3466 A
21 3243 A
21 6545 C task: go live with new homepage 0.5
21 6578 C
20 8978 B Task I 1 20
20 7654 B User Story 1 0.5
20 1234 C Task 3
20 4325 A Task 2
kanban board
todo (10) working (4) qa (2) deploy (2) done
8978
7654
1234
4325
3049
4343
kanban board
todo (10) working (4) qa (2) deploy (2) done
8978
7654
1234
4325
3049
4343
kanban board
todo (10) working (4) qa (2) deploy (2) done
8978
7654
1234
4325
3049
4343
kanban board
todo (10) working (4) qa (2) deploy (2) done
8978
7654
1234
4325
3049
4343
kanban board
todo (10) working (4) qa (2) deploy (2) done
8978
7654
1234
4325
3049
4343
kanban board
todo (10) working (4) qa (2) deploy (2) done
8978
7654
1234
4325
3049
4343
weekly planning
week # id Project Task Pts Effort
21 3455 A 14
21 3466 A
21 3243 A
21 6545 C task: go live with new homepage 0.5
21 6578 C
21 1234 C Task 3
20 8978 B Task I 1 20
20 7654 B User Story 1 0.5
20 4325 A Task 2
long term planning: allocate time
project/week
w 20 w 21 w 22 w 23 w 24 w 25
prj A 0 0 10 10 0
prj B 5 5 5 5 0
prj C 0 0 5 0 0
prj D 10 5 5 0 5
tot pts 15 10 25 15 5
kanban board
todo (10) working (4) qa (2) deploy (2) done
30494343
7654
1234
4325
long term planning
project/week
w 20 w 21 w 22 w 23 w 24 w 25
prj A 0 0 10 10 0
prj B 5 5 5 5 0
prj C 0 0 5 0 0
prj D 10 5 5 0 5
tot pts 15 10 25 15 5
our journey
1) early days2) growing 3) today4) tomorrow
tomorrow
trello is not enoughdata duplication across systems
Wrap up
wrap up
Wrap up
flow based work is quite flexible
Wrap up
x functional teams FTW!
Wrap up
beware context switch
Wrap up
things will change
Wrap up
try / experiment
that’s all folks!
Thank you!@_orso_ mo@ideato.it
that’s all folks!
Creditslightbuld http://www.flickr.com/photos/ful1toproduct: http://www.flickr.com/photos/ahmad-amirul/3243817815/equilibrist: http://www.flickr.com/photos/taniacataldo/5399392184/agile: http://blog.twg.ca/2009/04/selling-agile-are-estimates-the-new-spec/pair: http://www.flickr.com/photos/provoost/2246718091/net: http://www.flickr.com/photos/saintbob/165829023/xkcd condiments: http://www.cosc.canterbury.ac.nz/csfieldguide/student/_images/SE-xkcd-the-general-problem.pngpair: http://www.flickr.com/photos/improveit/1470213987context switch: http://www.personalkanban.com/pk/expert/context-switching-why-limit-your-wip-iver: http://www.flickr.com/photos/markcoggins/483973612/all icons: http://commons.wikimedia.org/wiki/Category:People_icons