Looking for Agile Approaches to classical Configuration Management

robertr5 over 7 years ago

I'm searching for documentation on recommended agile approaches project Configuration Management (CM) processes such as mapping requirements to releases, mapping release-specific export files for release, any kind of Configuration Control Board procedures, etc. If these are being done in a Dept of Defense context this is even better. I already checked out the Appian Playbook under Configuration Management, Program Management and Project Management and found that it does not address the classical CM processes. If some of the typical CM processes are no longer needed under agile, that would be helpful to know also. Thanks.

Discussion posts and replies are publicly visible

Parents

0 Ashvin Kapur over 7 years ago

Robert, from my experience, CM processes are not handled directly in Appian. Like kondetiv mentions above, there is no ootb structure in place as there is with Pega or other tools. Typically, I've seen clients use external systems, such as QuickBase, JIRA, or VersionOne to manage their release and requirement management needs.

As to your second point about Agile, it really depends on the controls of your organization. With multiple deployments and a constantly evolving requirement base, CM processes become even more important in some cases, as you need to be able to report on requirements delivered in each release, their status in lower environments, and keep a repository of exported applications in case of a rollback request/need. My suggestion would be to first understand what your organization requires with regards to CM controls, and then find a tool that can get you there.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Ashvin Kapur over 7 years ago

Robert, from my experience, CM processes are not handled directly in Appian. Like kondetiv mentions above, there is no ootb structure in place as there is with Pega or other tools. Typically, I've seen clients use external systems, such as QuickBase, JIRA, or VersionOne to manage their release and requirement management needs.

As to your second point about Agile, it really depends on the controls of your organization. With multiple deployments and a constantly evolving requirement base, CM processes become even more important in some cases, as you need to be able to report on requirements delivered in each release, their status in lower environments, and keep a repository of exported applications in case of a rollback request/need. My suggestion would be to first understand what your organization requires with regards to CM controls, and then find a tool that can get you there.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data