Manage a project portfolio
people
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 ...
sofware projects are challenging
How can we manage a project
portfolio?
our journey
1) early days
2) growing
3) today
4) 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 (c...
our journey
1) early days
2) growing
3) today
4) tomorrow
the early days
new projects
almost no support/maintenance
the early days
devs
ops
no UX / Design
scenario
a new project lifecycle
us
scenario
scenario usus
idea
business
objectives
usus
usus
ususususususus
Product Backl...
iteration meeting
ususususususus
Product 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 total
20 pts closed
--> 6 iterations
Burndown chart
Iteration 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...
hitting max capacity
pair A Iteration 1 Iteration 2 Iteration n...
pair B Iteration 1 Iteration 2 Iteration n...
Iteration...
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
devs
ops
no UX / Design
our journey
1) early days
2) growing
3) today
4) 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...
our journey
1) early days
2) growing
3) today
4) 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
ususususususus
Project A
ususususususus
Project D
ususususususus
Project B
ususususususus
Project 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 Tas...
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 homepa...
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 homepa...
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 homepa...
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 homepa...
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 ...
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 ...
our journey
1) early days
2) growing
3) today
4) tomorrow
tomorrow
trello is not enough
data 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!
Credits
lightbuld http://www.flickr.com/photos/ful1to
product: http://www.flickr.com/photos/ahmad-amirul...
Upcoming SlideShare
Loading in …5
×

Manage a project portfolio

756 views

Published on

How Ideato manages a project portfolio

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
756
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
6
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Manage a project portfolio

  1. 1. Manage a project portfolio people processes tools
  2. 2. Who am I? Michele Orselli CTO@Ideato @_orso_ mo@ideato.it
  3. 3. we love open source
  4. 4. from idea...
  5. 5. to product!
  6. 6. sofware projects are challenging
  7. 7. 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?
  8. 8. sofware projects are challenging How can we manage a project portfolio?
  9. 9. our journey 1) early days 2) growing 3) today 4) tomorrow
  10. 10. foundations: agile manifesto
  11. 11. xp: pair programming
  12. 12. xp tdd
  13. 13. xp: YAGNI
  14. 14. foundations: extreme programming If integration testing is important, then we'll integrate and test several times a day (continuous integration).
  15. 15. our journey 1) early days 2) growing 3) today 4) tomorrow
  16. 16. the early days new projects almost no support/maintenance
  17. 17. the early days devs ops no UX / Design
  18. 18. scenario a new project lifecycle us scenario scenario usus idea business objectives usus usus ususususususus Product Backlog
  19. 19. iteration meeting ususususususus Product Backlog
  20. 20. iteration meeting usususus Product Backlog ususus Prioritization
  21. 21. iteration meeting usususus Product Backlog ususus Planning Iteration 1 ususus Iteration
  22. 22. iteration based flow pair A Iteration 1 Iteration 2 Iteration n... release release release planning planning planning
  23. 23. a new project lifecycle Velocity: 120 pts total 20 pts closed --> 6 iterations Burndown chart Iteration x ususus
  24. 24. a new project lifecycle Leave room for: Iteration x ususus Bugs b Emergencies e
  25. 25. what about 2 projects? pair A Iteration 1 Iteration 2 Iteration n... pair B Iteration 1 Iteration 2 Iteration n...
  26. 26. every day: stand up meetings Rules: - 10/15 minutes - yesterday - tomorrow - roadblock
  27. 27. hitting max capacity pair A Iteration 1 Iteration 2 Iteration n... pair B Iteration 1 Iteration 2 Iteration n... Iteration 1
  28. 28. hitting max capacity pair A Iteration 1 Iteration 2 Iteration n... pair B Iteration 1 Iteration 2 Iteration n... Iteration 1 Iteration 2
  29. 29. context switch kills productivity
  30. 30. 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 * * **
  31. 31. bottlenecks devs ops no UX / Design
  32. 32. our journey 1) early days 2) growing 3) today 4) tomorrow
  33. 33. old & new new incoming projects “old” projects in maintenance
  34. 34. old & new Rules: - no 100% pair - no iteration - fifo
  35. 35. er pair A Iteration 1 Iteration 2 Iteration n... pair B Iteration 1 Iteration 2 Iteration n... ER t t t t t t ...
  36. 36. 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
  37. 37. our journey 1) early days 2) growing 3) today 4) tomorrow
  38. 38. what we learned context switch is bad iterations: performance +, react - er (flow): performance -, react +
  39. 39. split team devs ops ux devs
  40. 40. trello
  41. 41. kanban board todo (10) working (4) qa (2) deploy (2) done
  42. 42. 1 backlog per project ususususususus Project A ususususususus Project D ususususususus Project B ususususususus Project C
  43. 43. 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
  44. 44. 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
  45. 45. 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
  46. 46. 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
  47. 47. kanban board todo (10) working (4) qa (2) deploy (2) done 8978 7654 1234 4325 3049 4343
  48. 48. kanban board todo (10) working (4) qa (2) deploy (2) done 8978 7654 1234 4325 3049 4343
  49. 49. kanban board todo (10) working (4) qa (2) deploy (2) done 8978 7654 1234 4325 3049 4343
  50. 50. kanban board todo (10) working (4) qa (2) deploy (2) done 8978 7654 1234 4325 3049 4343
  51. 51. kanban board todo (10) working (4) qa (2) deploy (2) done 8978 7654 1234 4325 3049 4343
  52. 52. kanban board todo (10) working (4) qa (2) deploy (2) done 8978 7654 1234 4325 3049 4343
  53. 53. 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
  54. 54. 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
  55. 55. kanban board todo (10) working (4) qa (2) deploy (2) done 30494343 7654 1234 4325
  56. 56. 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
  57. 57. our journey 1) early days 2) growing 3) today 4) tomorrow
  58. 58. tomorrow trello is not enough data duplication across systems
  59. 59. Wrap up wrap up
  60. 60. Wrap up flow based work is quite flexible
  61. 61. Wrap up x functional teams FTW!
  62. 62. Wrap up beware context switch
  63. 63. Wrap up things will change
  64. 64. Wrap up try / experiment
  65. 65. that’s all folks! Thank you! @_orso_ mo@ideato.it
  66. 66. that’s all folks! Credits lightbuld http://www.flickr.com/photos/ful1to product: 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.png pair: http://www.flickr.com/photos/improveit/1470213987 context switch: http://www.personalkanban.com/pk/expert/context-switching-why-limit-your-wip-iv er: http://www.flickr.com/photos/markcoggins/483973612/ all icons: http://commons.wikimedia.org/wiki/Category:People_icons

×