Looking for Agile Approaches to classical Configuration Management

@robertr5 Pega have well configuration management. For example it supports mapping requirements to releases and mapping release-specific export files for release etc. But appian don't have this kind mechanism. Everything is manual. Even i have gone through appian play book but didn't find any.

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.

Thanks kondetiv and ashvink!

As a follow-on question then, when Appian project managers lead an internal agile project, does anyone know what CM tool(s) they use?

Robert, that's probably a good question to bring up with any Appian employees, potentially at Appian world, or through an email to an account executive. I've seen Appian PMs use the products I stated above (QuickBase, JIRA, VersionOne) on client projects where they are the lead, but I don't have information on what products they use on internal projects.

@robertr5. Some useful material produced by like minded people.

Documentation on Agile Model.docx

scrum-guide-us.pdf