Elements Catalyst supports the Agile Business Analysis cycle. The boxes to the left of the dotted line are Agile Business Analysis (and are supported by Elements Catalyst), and to the right of the dotted line are the Agile Development activities.
The Elements key modules are:
- Capture Requirements: An easy, but formalized approach for capturing and managing requirements from “submitted” to “implemented”. To give more context to the requirements, add supporting information and collaborate through a comment stream.
- Map Processes: Document end to end business processes with input from the requirements, ensuring everyone in the organization is on the same page and can use them as the “operations manual” to find documents, training and apps in context. This will also validate and expand on the requirements, or even generate new ones.
- Baseline Supporting Systems: What has been configured in Salesforce and the other systems? Find out and relate it back to requirements and operational process steps so that it makes sense.
- Write User Stories: Using the simple format, “As a ____ I want to _____ so I can ____”, write business user stories for every requirement so the dev team understand what they need to build. The acceptance criteria are now tighter as the user story is in the context of the process and the relationships between requirements is more obvious.
- Develop User Stories and Deliver Systems: Elements Catalyst does NOT deliver this
- Governance, releases and versions: Good governance of the evolution of your processes is best practice. Every time you release changes to your systems, there are probably changes to process documentation, so make sure that you manage the updates and archive the previous versions. If you work in a regulated industry like food, pharma or financial services, you already know all of this.
Cloud on AWS
Elements Catalyst is a 100% cloud app running on AWS (AmazonWebService) with tight integrations into other enterprise apps, such as Salesforce.
A Space allows you – from a single login – to keep different projects or clients separate. Perfect for consultants working with different clients, or companies with very separate divisions.
DON'T think of a Space like a folder. You can control who can view or edit content within a Space. Most companies will have one or two Spaces.
This is an enterprise app with an elegant sharing model.
- Every user is an Admin in their own Personal Space.
- Users need to be invited to a team Space by a Space Admin.
- When a user is in a Space, they can see and raise requirements, but only certain users can manage requirements.
- The owner of a map decides which users in a Space can view, edit, or manage a process map.
- Reference Models are controlled. Users can be given view rights or edit rights.
- Release Managers control the version control and publishing content.
Collaboration / comments
Every object (requirement, user story, process diagram, ref model node) has a comment stream so that users can collaborate.