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.
Small Hyper-Productive Teams<br />MikalaiAlimenkou<br />http://xpinjection.com<br />
Myth 1: Large <br />project requires <br />large team<br />
Speed is important!<br />20 x 1 = 4 x 5 = 2 x 10<br />
Transparency helps<br />to avoid wastes<br />
Right motivation improves productivity <br />
Myth 2: Large <br />teams help to <br />save money…<br />
You pay with quality<br />
You can save on managers!<br />=<br />
Less time spend on meetings<br />
Best people don’t waste their time<br />
How to build great team?<br />
Hire right people<br />
Start with pair programming<br />
Much code review between team members<br />
Reduce amount of “process” work<br />
Maximize face to face communication<br />
Remove impediments<br />
What if it is really<br />large project?<br />
Use small functional teams<br />
@xpinjection<br />http://xpinjection.com<br />mikalai.alimenkou@xpinjection.com<br />
Upcoming SlideShare
Loading in …5
×

Small Hyper-Productive Teams

3,699 views

Published on

Presentation from PechaKucha part of IT-Jam conference (Odessa, August 2011) about building of small hyper-productive teams and managing them to drive projects to success.

Published in: Technology
  • Be the first to comment

Small Hyper-Productive Teams

  1. 1. Small Hyper-Productive Teams<br />MikalaiAlimenkou<br />http://xpinjection.com<br />
  2. 2. Myth 1: Large <br />project requires <br />large team<br />
  3. 3. Speed is important!<br />20 x 1 = 4 x 5 = 2 x 10<br />
  4. 4. Transparency helps<br />to avoid wastes<br />
  5. 5. Right motivation improves productivity <br />
  6. 6. Myth 2: Large <br />teams help to <br />save money…<br />
  7. 7. You pay with quality<br />
  8. 8. You can save on managers!<br />=<br />
  9. 9. Less time spend on meetings<br />
  10. 10. Best people don’t waste their time<br />
  11. 11. How to build great team?<br />
  12. 12. Hire right people<br />
  13. 13. Start with pair programming<br />
  14. 14. Much code review between team members<br />
  15. 15. Reduce amount of “process” work<br />
  16. 16. Maximize face to face communication<br />
  17. 17. Remove impediments<br />
  18. 18. What if it is really<br />large project?<br />
  19. 19. Use small functional teams<br />
  20. 20. @xpinjection<br />http://xpinjection.com<br />mikalai.alimenkou@xpinjection.com<br />

×