In this brief talk we analyse different type of leadership styles and focusing on authoritarian (fear & pressure) style we analyse its effects on a software development team and on the project dynamics & delivery.

1. WHY WE CARRY WATERMELONS
?

2. GREEN OUTSIDE, RED INSIDE

3. LEADERSHIP STYLES

4. If the job isn't highly technical, the leader need not be
competent, but can lead by fear
LESSONS FROM A TASK
ORIENTED STYLE

5. BY-PRODUCTS
BLAME

6. BY-PRODUCTS
SILOS

7. BY-PRODUCTS
OVER MANAGEMENT

8. PATTERNS

9. THE GOOD NEWS…

10. Task-oriented leaders tend to overestimate their own accomplishments.
LESSONS FROM A TASK
ORIENTED STYLE

11. When the work is complex, no leader can be absolutely sure that
plans won't gang aft agley
LESSONS FROM A TASK
ORIENTED STYLE

12. BUG FIXING…

13. Very little work we do is really so important that it justifies
sacrificing the future possibilities of the people doing the work
If you are a leader, the people are your work.
There is no other work worth doing
LESSONS FROM A TASK
ORIENTED STYLE

14. Writing code is a social activity, you write code not for machines
but for other people.
Software == People
LESSONS FROM A PEOPLE
ORIENTED STYLE

15. TEAM
Volleyball example:
• you will never hear
“Tua”
• you always will hear
“Mia”

16. • GERALD M. WEINBERG
BECOMING A TECHNICAL TEAM LEADER : AN ORGANIC
PROBLEM-SOLVING APPROACH
• BARRY O'REILLY
WHY WE CARRY WATERMELONS?
• BRUCE F. WEBSTER
THE WETWARE CRISIS: THE THERMOCLINE OF TRUTH
REFERENCES

17. • Grazie!
THANK YOU