Your SlideShare is downloading. ×
Principles for Successful Software Management
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Principles for Successful Software Management

5,572
views

Published on

Keynote to ACCU Conference 2009. …

Keynote to ACCU Conference 2009.
Outlines 9 Principles for Successful Management of Software Development.
This is not about Project Management, its more important than that.

Published in: Business, Technology

1 Comment
24 Likes
Statistics
Notes
  • very useful presentation i am indebted to you for efforts so plz forward to salman_saad92@yahoo.com so that i can share with needy friends for upcoming papers thank you
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
5,572
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
1
Likes
24
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. 9 Principles for Successful Software Management allan kelly (c) Allan Kelly, 2009 http://www.allankelly.net http://blog.allankelly.net allan@allankelly.net 1
  • 2. Allan Kelly  Long time ACCU contributor  Author: Changing Software Development, 2008  I help companies do software development better  Process, Practice  Agile Methods  Product Management  Training, Coaching, Managing 2
  • 3. Q: What is the secret of successful software development? A: Someone has to give a damn (Someone who actually understands development) Companies appoint managers to be that person 3
  • 4. Why are managers important?  Bad management destroys projects  Bad management theory destroys companies  Done badly management is worse than nothing 4
  • 5. Fred Brooks said “Some readers have found it curious that The Mythical Man Month devotes most of the essays to the managerial aspects of software engineering, rather than the many technical issues. This bias ... sprang from [my] conviction that the quality of the people on a project, and their organization and management, are much more important factors in the success than are the tools they use or the technical approaches they take.” Frederick P. Brooks, The Mythical Man Month 1995 5
  • 6. Managers before Coders  Managers start architecture by deciding:  How many developers?  Which roles will be staffed? DBA? Tester?  Which technologies? Managers are  Conway’s Law architects  Architecture is a copy of organization  So does software architecture mean anything?  Architect the organization not the code  Create an environment for developers to do good work 6
  • 7. 0. You need a management philosophy  Managers make thousands of small decisions every day. Need:  Consistency  Drive towards target  Make them quickly  You need a  Philosophy  A value system  Here help you  towards better software management 7
  • 8. 1. Know your Customer  Name your customer  A customer (singular: individual, organization)  A market (many customers)  What is the problem you are trying to solve?  Understand the problem  Understand it in depth  Identify the core 20%  Less is more  Solve it completely 8
  • 9. Know your Customer: It is a full time job  Developers don’t know best  Use a:  Product Manager: software vendor  Business Analyst: bespoke/internal development  Get out there  Talk to customers  What are they trying to do?  Know your competitors 9
  • 10. Know your Customer: Prioritisation 1  Always too much work 2  Seek out the most valuable 3  Absolute prioritisation 4 5 MoSCoW rules 6 Business: Pay your 7 taxes 8 9 10
  • 11. 2. Features - Resources - Time Product Owner needs to Resources Features make (People) these trade offs Scope creep Fixed in (run backwards) the short run (Brooks Law) Time Dynamics of Software Development, Jim Time boxed McCarthy, 1995
  • 12. Managing the FRT triangle Do not overfill - ends in a tears  Business voice is more important than ever  Project Management role is changing 12
  • 13. Philip Crosby 3. Quality is Free 1980 >  Poor quality costs:  Testing Cost of  Disruption doing it  Meetings - Arguments right  Rework  Unhappy customers And it makes for happier  No excuse for people  Gold plating • People like doing good  Reusable code work  Fancy code • Doing shoddy work makes them unhappy 13
  • 14. Intermission Q: How much time would you save if....  You had no bugs to fix?  You only had 20% as many features to implement? $ Bugs are expensive Simple really to fix So don’t Just say No to Bugs write them 14
  • 15. 4. Management by Routine  Simplify management  Make it routine  People like routine  Makes life predictable  Ifyou can’t keep to a routine you have a problem  Fix that problem 15
  • 16. 5. Stay Connected  Problem: The Gap between workers and managers  Go see the problem yourself, speak to the people who do the work  Gemba: the place of truth (work)  Genchi / Gembutsu: go see for yourself Mind  Trust your people the  They know the answers  (If not why did you hire them?) Gap  (Why do you still employ them?) 16
  • 17. 6. Risk Management by doing  Profit is the return to risk  Remove the risk, remove the profit  Inaction carries risk too  Competitors win sales  Staff do their own thing  Solution: Fail  Fail fast  Fail cheap  Learn from failure  Roll back 17
  • 18. 7. Continuous Improvement  Not just a cliché - it means something!  Not a project, a way of life  Repeated incremental improvements What have you improved this week? 18
  • 19. Continuous improvement in 3 domains Work to Java, C++, Unix, TCP/IP, …. improve Solution in each domain Application Process Oil production, banking, RUP, Scrum, …. media, … How we do things around here
  • 20. Improvement Learn from what you do Act on it Continuous Keep doing it Again and again (Not a project, not a fad, not a one off) Knowledge = Learning + Action 20
  • 21. 8. Trust & Honesty Trust & Honesty are the basis of power .... without them all is lost Leadership Command and Control is how things get done Authority Just an illusion Organization gives Managers LEGITIMACY • to ask questions • to put things in order 21
  • 22. Fall (and rise?) of Trust  Trust breakdown all too common  Developers <-> Manager  IT <-> Business  Rebuild trust  Quality: No more bugs  Routine: Regular releases, regular reports  Prioritisation: Respond  Restore trust to opens doors  New options become possible 22
  • 23. 9. It’s the People, Stupid  Peopleare not plug compatible  Good people  Build or buy?  Steady growth  Individuals & Teams 23
  • 24. Finally... Manager are not Aliens  Have you asked your manager:  What are their concerns?  What are the problems they see? Or did you  What are they doing to achieve it? just  What is their philosophy? assume  Talk to your managers you know?  Listen to what they say 24
  • 25. Successful management 0. Need a management philosophy 1. Know your customer 2. Features - Resources -Time 3. Quality is free 4. Management by Routine 5. Stay Connected 6. Risk Management by doing 7. Continuous improvement 8. Trust & Honesty 9. It’s the People, Stupid 25
  • 26. Thank you! (c) Allan Kelly, 2009 allan kelly http://www.allankelly.net http://blog.allankelly.net 26