Your SlideShare is downloading. ×
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Death by Project (and the simple choice)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Death by Project (and the simple choice)

4,716

Published on

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

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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

×