Configuration Baseline

Joshua Robinson's picture

I'm the Configuration Manager for a large enterprise project. I was added to the team after around 8 months worth of developement/staging had already taken place. We're working toward a short-term ATO, and PMO is looking to baseline our applications. My argument is that we're not ready to baseline, as we're still in developemnt. No configuation items are recorded in Remedy, the Change Managemnet process isn't fleshed out (as that is also my tasking), and we have no historical records that I can find for how are architecture came to this point. Simply, here, this is version one, and now start documenting from this point forward.  Am I worng in my push-back on this stance? Shouldn't I first work to identify the CIs and their historical changes (as best as I can documnet)? Further info: this system will be the subject of an offical audit, not just my configuration audit.

No answers yet.

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.