MathJax

Monday, June 26, 2006

Software manager's checklist

Execution
  • Do you have your customer's requirements?
  • Do you have a n approved budget?
  • Do you have an approved roadmap?
  • Do you avhe an approved schedule?
  • Are you delivering the product on time?
  • Do you hire developers in a timely fashion?
  • Is your team capable of dealing wiht change?
  • Are you capable of keeping your team focused and resisting change?
  • Do your customers encounter a lot of quality issues with released products?
  • Do you and your team measure how well you do your work on a regular basis to find ways to improve?
Communication
  • Does your team understand your company's strategy?
  • Does your team understand engineering's roadmap?
  • Does your team understand why the roadmap meets the goals of the strategy?
  • Do you have regular communication meetings and e-mail with your team?
  • Are people on y our team willing to tell you bad news?
  • Do you hear information about your team from your team before you hear it from others?
  • Do members of your team communicate with each other and the rest of the company in a respectful manner?
  • Do you provide information to your boss before he or she has to ask for it?
  • Do other people in the company know what your team is doing and accomplishing?
  • Do you communicate in a positive fashion?
Empowerment
  • Does your team develop and buy into their schedules?
  • Do you avoid micromanagement?
  • Do you delagate tasks and let your reports proceed without interference?
  • Do you make it clear what your employees are accountable for?
  • Do you provide leadership opportunities for your employees?
  • Does your team have a sense of urgency in addressing issues?
  • Do you set cleawr roles and responsibilities for your employees?
  • Do all the members in your team know what they need to accomplish each week before they can go home fo the weekend?
  • Do your developers consider your organization a positive work environment?
Things to juggle
  • Resources
  • features
  • Dates
  • Quality
Caveats
  • If you remove too many features, you won't have a competitive product.
  • If you add too many features, you won't make your dates.
  • If you scrimp on quality, you'll get a bad reputation.
  • If you wait until the product is prefect, you'll miss the market window.
  • If you make your engineers work extra hours all the time, they'll burn out.
  • If you add too many resources , you can run out of money.
  • If you slip the schedule, you make it hard for the sales team to sell and you might miss a market window.