Afternoon guys (adjust greeting to accommodate your time zone),
I've been tasked with drafting some documents to facilitate in solidifying some processes for our team to work to. One of the documents is a 'project sign-off' from the perspective of development (i.e. to allow us to checklist component completion, testing completion and 'so on'). Another document is in fact to be a diagram of the complete development process, from the work coming in to the project being signed off.
Now, I'm not asking for a definitive answer for me to copy and paste, I intend to do my research and indeed have started (not to mention reaching into the depths of my own (limited) knowledge and wisdom (we all have plenty of ideas but our own not necessarily the best)). What I would like to ask is for some insight from professionals who actually already work from such documented processes.
What are the key factors which define the development process, the fundamentals?
Also, what is it you are required to assert prior to signing-off a project?
Each answer will probably simply just give a term to a topic which I will need to delve into myself, I know. For instance, creating a project/structuring, version control initial set up and the continuing practices for check-ins, different types of testing etc etc.
would be grateful for any insight, though I am aware this may well become a wiki/discussion, or something, I am prepared for that, so long as I can gather some wisdom of many.
Thanks.
PS I have done a search and 'new-tabbed' some of the 'related' questions prior to posting and will look into this myself also, but I do feel the question to be appropriate and not asked/answered in this instance as of yet.