0
Death by  project (and the simple choice) Steve  Greene,  salesforce.com
Most IT and operations organizations organize work by project
makes sense.  right?
Afterall that’s what we deliver. projects. projects. projects. and, more projects.
but, wait a minute.  our customers think our projects take way too long
cost too much
and don’t meet their needs
And, our staff is scattered, over-worked, and under-appreciated
nice.
could there be a better way?
let’s take a look
The Project Based Model
People Projects Here’s what we start with
Project Based Model <ul><li>Project teams are created upon project initiation </li></ul><ul><li>Projects are staffed with ...
this is what we get
People Projects Project Based Model
hmm.  that looks confusing and sorta painful
Project Based Model Results <ul><li>Context switching is high </li></ul><ul><li>Individuals prioritize projects rather tha...
let’s look at another way
The Team Based Model
a simpler model
Team Based Model <ul><li>Work flows through self-organized, cross-functional teams </li></ul><ul><li>Teams have dedicated ...
Self-organized Scrum Teams (x-functional dedicated) Projects Prioritized Backlogs Shared Services
Team Based Model Benefits <ul><li>Consistent and sustainable pace </li></ul><ul><li>Less context switching </li></ul><ul><...
feels good.  works.
Think about it.
 
Upcoming SlideShare
Loading in...5
×

Death by Project (and the simple choice)

4,740

Published on

Published in: Business, Technology
2 Comments
8 Likes
Statistics
Notes
No Downloads
Views
Total Views
4,740
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
294
Comments
2
Likes
8
Embeds 0
No embeds

No notes for slide

Transcript of "Death by Project (and the simple choice)"

  1. 1. Death by project (and the simple choice) Steve Greene, salesforce.com
  2. 2. Most IT and operations organizations organize work by project
  3. 3. makes sense. right?
  4. 4. Afterall that’s what we deliver. projects. projects. projects. and, more projects.
  5. 5. but, wait a minute. our customers think our projects take way too long
  6. 6. cost too much
  7. 7. and don’t meet their needs
  8. 8. And, our staff is scattered, over-worked, and under-appreciated
  9. 9. nice.
  10. 10. could there be a better way?
  11. 11. let’s take a look
  12. 12. The Project Based Model
  13. 13. People Projects Here’s what we start with
  14. 14. Project Based Model <ul><li>Project teams are created upon project initiation </li></ul><ul><li>Projects are staffed with available resources </li></ul><ul><li>Team members work on many projects in parallel that are managed through many teams </li></ul><ul><li>Team members are assigned work by project managers </li></ul><ul><li>Requires heavy-weight centralized Project Management and coordination </li></ul><ul><li>Teams disband upon completion of project </li></ul>
  15. 15. this is what we get
  16. 16. People Projects Project Based Model
  17. 17. hmm. that looks confusing and sorta painful
  18. 18. Project Based Model Results <ul><li>Context switching is high </li></ul><ul><li>Individuals prioritize projects rather than teams </li></ul><ul><li>Disrupted and inconsistent flow </li></ul><ul><li>Inconsistent and unsustainable pace </li></ul><ul><li>Little visibility or transparency </li></ul><ul><li>Less predictable </li></ul><ul><li>Complex resource management </li></ul><ul><li>Complex Octopus team structure </li></ul>
  19. 19. let’s look at another way
  20. 20. The Team Based Model
  21. 21. a simpler model
  22. 22. Team Based Model <ul><li>Work flows through self-organized, cross-functional teams </li></ul><ul><li>Teams have dedicated / persistent resources (virtually everything they need to deliver) </li></ul><ul><li>Teams own a specific domain of work (multiple projects + more) </li></ul><ul><li>Project work is prioritized on a backlog </li></ul><ul><li>Team members work together each day on only the top priority work until it’s done </li></ul><ul><li>All team members have the same priorities </li></ul><ul><li>Simple team structure </li></ul><ul><li>Teams persist over time </li></ul>
  23. 23. Self-organized Scrum Teams (x-functional dedicated) Projects Prioritized Backlogs Shared Services
  24. 24. Team Based Model Benefits <ul><li>Consistent and sustainable pace </li></ul><ul><li>Less context switching </li></ul><ul><li>Faster “time-to-deliver” for high priority work </li></ul><ul><li>More predictable </li></ul><ul><li>Greater visibility </li></ul><ul><li>Greater throughput </li></ul><ul><li>Light-weight project management required </li></ul><ul><li>Happier customers </li></ul><ul><li>Happier teams </li></ul>
  25. 25. feels good. works.
  26. 26. Think about it.
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×