The CMS Already Knew How
ai
A proof of concept that lets authors create unpublished course content through an assistant, using the CMS screens that already exist. The months were in the retyping, not in a missing system.
Berlin / Stockholm
Solution Architect & Team Lead

ALM platforms, hosted integrations, and agent engineering — written as delivery practice, not as a slide.
ai
A proof of concept that lets authors create unpublished course content through an assistant, using the CMS screens that already exist. The months were in the retyping, not in a missing system.
ai
After a year of putting AI agents into real delivery work, the useful split is not "better prompts." It is rules, skills, workflows, and loops — and knowing which one should stop the agent.
polarion
Polarion is more useful when you treat it as an extension host. Here is how I keep workflow functions, script catalogs, and external calls durable instead of becoming paste-bin folklore.
alm
A related-to link is not traceability. Here is how I think about suspect links, stale vs confirmed relationships, and what "parity" means when two ALM tools must agree.
integration
The hard part of ALM integrations is not the API. It is making a panel inside Jira, Azure DevOps, or Polarion look like it belongs there — including the host's theme and the host's login.
accessibility
WCAG work sticks when it lives in Cypress and CI, not in a slide at the end of a release. Here is the delivery shape I use: rules, custom commands, and a gate that can fail the build.
Pick a time that works.