We are ramping up our internal software practices community for IT developers. The question in the title recently came up and I thought, "why not share it with the larger IT crowd?". What does it take to write really outstanding guidance that not only helps close the gaps on current projects but goes so far as to answer questions they didn't know they had?
As we've gone through and looked at the software developement lifecycle (SDLC), we discovered that developers have nagivated each phase doing the best they can. Often they have documented processes and tips along the way. Most often they rely upon their learnings from previous projects and apply those to the next one. We hope to leverage each lessons in growing process and reference, as well as samples in order accelerate our software application processes internally.
That doesn't mean we don't buy or configure software. Instead we understand that there is a challenge in creating truly amazing software that not only performs at the edge of the envelope, but also makes the customer say wow!
With that in mind, this outline is being shared with each team member building guidance on mobile device specific or client-server technologies.
- Development installation
- Source code management
- Naming conventions
- Support (build for supportability)
- Help build
- Best practices
- Code samples
- Communities (developers)
- Help scripts
- Monitoring wire-up
- Communities (users)
As we work with a specific capability or technology, we fill in the gaps and identify our next work. Although to the outsider this may appear simple enough to just fill int he blanks; it is not. When looking at large enterprises (100k+) with hundreds of developers and increasing development languages, technologies and platforms to deploy to, it becomes complex quickly.
Good thing those developers have been doing this work already. We just need to throw it to paper and place some governance around it.
Our story continues. How is your story going?