Be Right Back, Uninstalling

Full Version: Structured Software Development & Planning Question
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Srs career-related question here, so I'm making my own thread for it.

My company is trying to develop a more structured method to how we plan and execute software development, as well as test the software we've written. Currently, each of the individual developers kinda does our own thing, and we share a common codebase but there's a lot of duplicated effort and non-interchangeability due to the method we use. That's bad.

I've been tasked with assisting in developing a new method that all of us can follow (ideally - for me - including some sort of source control, but I doubt that'll actually happen), and I'm curious if any of you can describe what your companies do.

I know we've got a number of people working either in IT or straight up Software development, so I'd really appreciate this turning into some sort of discussion on the topic.
Uggh UML.
UML is what my school is teaching for software engineering.
yeah, wish my work had some of that...

I ran into a enterprise wide change this morning that was causing easily duplicated script sheets for controlled meds to spit out every time a provider ordered the medication.  I sent out a blast "This change happened, it's fucked up, was this intentional?"  to which my supervisors replied, "What change?"  Now they're trying to figure out who fucked up the prod server for an entire region. 

I don't get paid enough.
(02-11-2013, 01:51 PM)at0m link Wrote: [ -> ]... I'm curious if any of you can describe what your companies do ...

LAWL

Seriously though, my company is a federal contractor so pretty much every contract has it's own method. The Agile method is pretty popular right now, but I don't think that's really what you're looking for.

Both my current project and my old project primarily use code repositories and change management. My old project was more formal with a Change Control Board (CCB) that had to approve all production changes (both to code and to the environment) and all code/scripts/documentation was stored in Git. The new project primarily only uses TeamForge which has built in CM features to share final releases and documentation, but I'm not sure what the developers use though since there is actually a separate development team on this project.