After reading E-myth Revisited, I realize that I can do a better job at making my company less reliant upon me… I spend a tremendous amount of time answering silly questions (silly to me, but necessary for my developers to get the job done).
I need to write a set of operating manuals for what to do in certain situations…
For instance:
- How to make a build
- How to write test cases
- How to report status
- How to fix a bug
- How to handle support question A, B, C, etc…
- What to do when you are stalled
- What to do when the power goes out (really, I need to do this)
- etc…
What are some useful, generic operating manuals that you can think of, for a software development company?And please, if you have some good, short, online versions that you know of, please post them. I would much rather use a starter manual and modify it for my needs, than start from scratch.
What about a wiki – at least then other people can start to contribute.
Otherwise they are just going to rely on you for the manuals