I could use a crash course on software project management. (Not that you need to provide this 'crash course' yourself).
If you can answer some of the questions below OR link me to some useful resources that can give me a good overview or pointers quickly and simply.
Here's the story, and here are my questions:
In this case I am the sole developer that will be providing solutions to this company, so I'd like to call myself a "solutions provider. But even though I will be working alone, I will still need to engage management to get their requirements and deliver a solution to them and do this as professionally as possible.
Here are some of my questions:
- Since there is only 1 developer, there is no need to 'overformalize' the process. But, what is the minimum level of 'formalization' you would recommend here? Obviously major meetings for the SDLC. II think a scope document should be prepared after Requirements Analysis. I think perhaps a time estimation sheet for each foreseeable module should be created, and then regular updates on how close we are to these estimates. What do you think? What else?
- I need to be able to get the Requirements from the client as accurately as possible and develop a scope document. I like to think I have enough experience to ask the right questions - but some tips or a template might be helpful.
- I will need to generate estimates on how long each step or module will take (what's a good estimation methadology? Any tips on time estimation?)
- Any (preferably freeware) software that might help with this? (not advanced stuff like Rational Rose)
- What would be a good job title for this role? I'm the only developer, providing software solutions to the company in-house. Would say software solutions architect? Software developer?
- Anything else you can think of that I might need?
Any feedback would be great.