When defining your Software Development Process (SDP) where should you start?
First of all, if you can, don't define it. But most of the times you'll have to (to introduce your company's specifics and to allow for easier alignment of large teams).
So where should you start? From scratch?
No, it is suggested that you find whatever the industry states regarding the processes you are interested in and build upon it, using these standards as Reference Documents.
E.g.: If you're working for space, does it make sense to build your own SDP from scratch? Absolutely not. Above all, companies working on such mature markets will have to comply to standards, and some of those standards are related to software development, so you should start using them.
It'll save you time getting certifications, being certified by suppliers that might want to check how do you develop software (and perform other types of activities such as project management) before hiring you, etc.
So, you should definitely start by reading, understanding and using things like:
- ECSS (ESA standards), NASA-SEL (NASA standards): http://silvaonsoftware.blogspot.pt/2016/05/the-beauty-of-standards-and-more.html
For life cycles you have ISO 12207: http://silvaonsoftware.blogspot.pt/2016/04/standard-isoiec-12207-systems-and.html
For tailoring you have CMU/SEI-94-TR-024 and more: http://silvaonsoftware.blogspot.pt/2016/05/tailoring-in-your-sdp.html
For terminology you have also additional standards: http://silvaonsoftware.blogspot.pt/2016/05/standards-terminology-standards.html
So, for all reasons in the world you'll be doing... REUSE.
