I have been assigned as CM on an OTA project or Other Than Authority Project, very similar to IR&D or prototype. I have written a cm plan based on a department cm plan and modified for the project. But after discussion with the project lead today, and answered responses to a review of drafted CM plan. They want little to no CM support, not even recording or archiving their CDRLs. They would much rather rely on each area to draft, review, and provide CDRLs to customer early on, plus they are using Sharepoint as well to allow customer to review their CDRLs.
here is a definition of an OTA found on the web. What is Other Transaction Authority (OTA)?
Other Transactions (OTs) are legally binding instruments that may be used to engage industry and academia for a broad range of research and prototyping activities. OTs are typically defined by what they are not: they are not standard procurement contracts, grants, or cooperative agreements. As such, they are generally not subject to the federal laws and regulations that apply to government procurement contracts (e.g., FAR/DFARS).
A past company we allowed IR&D projects to do their own work and CM was only contacted if they wanted to release any of their documents, drawings, or SW as engineering releases. But none of their products could be used as formal released because they didn't go thru full formal testing. Ideas or thoughts, or suggestions.
what is the role of software builds like private, integration and release builds in software development life cycle? What kind of documentation is required at build level? Can i allocate version no to a build and when version allocation came into action?
We may need to switch from our long standing, 20+ years use of PVCS VM to GIT. CM would like to maintain a Master repository with no branching but allow the developers the freedon to do so bur then merge back into the master. Also are their resources available on pulling information from GIT repository for reports as in a list of files, revisions and change dates for each baseline? Is their any formal training available for GIT and setting it up? Thanks for any guidance on this.
Tools like JIRA, Service Now for Incident management, I'm looking for a software platform that will keep track of all related documentation, test plans, user sign offs etc... But what I have not been able to find and is critical for me is a Parent - Child, Child - Child relationship of all changes.
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.