Knowledge Base

On this page most information about the Capturum Software Group is found in a central place. This so you can read and find the information here whenever you need it.

This document is being filled continuously . So if you are missing any information please don’t hesitate to ask.

As described in the “process” above we work through our standard Emendis workflow for which we have 2 scenario’s:

• Waterfall proces with 1 release (per phase)
• Scrum process with a release after each sprint

Both workflows are shown below. A short summary of the meaning of letters used:

• T = Test
• P = Production
• A = Acceptance
• B = Backlog Refinement
• L = Live release

Workflow following ‘Waterfall’ method with 1 release:

After each sprint we deliver Acceptance. Client test results are checked and marked “bug” or “improvement” by testing and projectmanagement. After this they will be fixed at the end of the current sprint. This till all sprints are done after which a “deliver” sprint is planned. During this sprint all is focussed on fixing all last improvements and bugs toward a Production release.

Workflow following ‘Scrum’ with release each sprint

After each sprint on Monday we will release Acceptance after all is tested and approved internally. After this the new sprint will start on a new release branch. Meanwhile the client can test and all redo/comments will be fixed on the previous release branch till the whole previous sprint is done. This to assure a Production release latest Thursday.
After this the release branch also will be merged to develop branche so all fixes and changes are present in the current sprint branch.