Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
PROJECTS KILL AGILE
DEVELOPMENT
CHRIS HOWE-JONES
@AGILE_GEEK
11TH AUGUST
PROJECTS KILL AGILE-DEVELOPMENT
sometimes
OR
Why Feature Teams SUCK!
WHY?
CONSTRAINTS
Limited budget - especially fixed price
Limited resources
Limited timescales
WHAT?
BEHAVIOUR
Focus on:
functionality teams formed for life of project
team members fungible
architecture/design 'third class'...
"I don't have to live with it"
Everyone is responsible, no one is accountable
monoliths rule Cost over value - what's the ...
PRODUCT TEAMS
ALIGN TO PRODUCT/PLATFORM/COMPONENT
Promotes:
Code ownership Non functional requirements
Architecture matters "Live with i...
Interfaces to other products
Burn down tech debt
HOW TO AVOID…
"Throw it over the wall" syndrome Isolationism
1 Dimensional teams "Over gilding"
PRODUCT DELIVERY
Product Owner Separate backlog Build in feedback
Feed 'projects' into 'feature funnel'
Services (even in same team)
Shared vision across products
Treat channels as customers
Treat other teams as customers
'T s...
CREDITS
Email: chris.howejones@gmail.com
Twitter: @agile_geek
Github: github.com/chrishowejones
Presentation:
github.com/c...
Upcoming SlideShare
Loading in …5
×

Projects kill agile development

523 views

Published on

Presentation given to Agile NE 11th August 2015.

Published in: Software
  • Be the first to comment

Projects kill agile development

  1. 1. PROJECTS KILL AGILE DEVELOPMENT CHRIS HOWE-JONES @AGILE_GEEK 11TH AUGUST
  2. 2. PROJECTS KILL AGILE-DEVELOPMENT
  3. 3. sometimes OR Why Feature Teams SUCK!
  4. 4. WHY?
  5. 5. CONSTRAINTS Limited budget - especially fixed price Limited resources Limited timescales
  6. 6. WHAT?
  7. 7. BEHAVIOUR Focus on: functionality teams formed for life of project team members fungible architecture/design 'third class' citizen
  8. 8. "I don't have to live with it" Everyone is responsible, no one is accountable monoliths rule Cost over value - what's the depreciation Multiple teams - one code base
  9. 9. PRODUCT TEAMS
  10. 10. ALIGN TO PRODUCT/PLATFORM/COMPONENT Promotes: Code ownership Non functional requirements Architecture matters "Live with it"
  11. 11. Interfaces to other products Burn down tech debt
  12. 12. HOW TO AVOID… "Throw it over the wall" syndrome Isolationism 1 Dimensional teams "Over gilding"
  13. 13. PRODUCT DELIVERY Product Owner Separate backlog Build in feedback Feed 'projects' into 'feature funnel'
  14. 14. Services (even in same team) Shared vision across products Treat channels as customers Treat other teams as customers 'T shaped people (not 'resources') Set percentage of 'technical payback' (or one week in 7)
  15. 15. CREDITS Email: chris.howejones@gmail.com Twitter: @agile_geek Github: github.com/chrishowejones Presentation: github.com/chrishowejones/presentations Blog: chrishowejones.wordpress.com

×