Mazylon Pulse isn't a dashboard. It's a copilot that watches your projects continuously, coaches your teams at the right moment, and makes your Confluence processes (deployment, DoD, onboarding, incident…) answer in Teams.
Every morning at 8am in your team's Teams channel: an actionable, prioritized summary with traceable evidence.
~40 embedded business heuristics, written by agile coaches, tenant-calibratable via continuous feedback. Story structure, backlog health, cycle time, abandoned PRs, agile metrics and positive signals measured.
If you steer 3 to 8 projects, atomic signals aren't enough. The executive layer detects meta patterns per-project heuristics miss — portfolio drift, someone overloaded cross-projects, multi-team blocker, sprint miss streak. Delivered as Monday 8am digest + 4h cron push + dedicated dashboard + Teams intent.
One step more analytical than the exec view: median lead time, cumulative throughput, total WIP, median escape rate, predictability — all aggregated across your active projects, with « worst offenders » leaderboards that answer in 3 seconds « which of my projects is slowest, which has the most escaping bugs, where are we overloaded? ». Available in dashboard and Teams bot.
On each project, the Flow tab gives the metrics modern EMs actually use — lead time, throughput trend, average WIP, PR/backlog age distributions, effort mix, 5-sprint predictability, escape rate. No DORA connector required: everything is computed from your Jira/GH/GL/BB data already ingested.
Before, the coach analysis and Discovery status went stale for weeks unless someone clicked « Refresh ». Now, every Sunday 8pm local of your organization, Pulse re-syncs all connectors of your active projects and regenerates the agile coach report — your analyses are fresh Monday morning, hands-off.
The moment a dev creates a Jira ticket or opens a PR, Pulse reviews against Definition of Ready / PR quality criteria and privately coaches the author in Teams — without going through the manager.
Nearly 30 natural-language intents (FR / EN): project status, sprint forecast, KPIs, on-demand digest, coaching, project mute, doc questions, ceremony prep, retro action tracking. No commands to memorize.
Pulse doesn't add meetings. It preps the ones you already have. 24h before each configured ceremony, a focused prep pack is pushed to the project's LEADs in Teams. After a July refactor, each pack now surfaces 3-5× more actionable signals — no more isolated stagnating tickets but a real action plan for the facilitator.
2 weeks after a Planning Pack that warned TIGHT or OVERCOMMIT, Pulse measures the following sprint's closure. If the team shipped ≥85% of committed, a « 🎯 Overcommit avoided — well done! » message is automatically posted in the Teams meeting chat. The proactive loop goes all the way: signal → human adjustment → sprint delivered → measured recognition.
Capture the action items decided in retro directly from Teams — Pulse persists them, lists them on demand, and automatically reminds LEADs when a due date approaches. No more actions forgotten in a shared doc.
Pulse indexes your project-linked Confluence spaces AND cross-references each answer with the current Jira tickets / GitHub PRs of the user asking. That's the real wedge: Glean reads the doc, LinearB sees the delivery — Pulse combines both in real time in Teams.
Every Monday 09:00 UTC, a « 🚀 Pulse status — last 7 days » digest aggregating all your Mazylon projects is posted to OWNER/ADMIN. Targets EM/CTO steering multiple projects and wants a TL;DR without opening 5 dashboards. Auto-skip when the week has been quiet.
The engine correlates Jira ticket, GitHub PR and Teams conversation around the same unit of work. One timeline, always traceable.
Nine reports generated on demand or on webhook — from the dashboard OR from Teams in natural language. Always from real data, never from gut feel.
For Head of Eng / VP Eng steering a project portfolio: consolidated roadmap, cross-project dependencies, global capacity per team.
Each user finely controls what Pulse pushes to their Teams. 12 notification kinds individually toggle-able, 3 one-click presets, control from dashboard OR from the Teams bot in natural language. An EM steering 5 projects doesn't just take it — they choose.
From V2 and always opt-in: Mazylon can act on Jira, create sub-tasks, add comments, schedule Teams meetings.
V2 and beyond
The Scrum Master agent that preps your ceremonies is already here. Coming soon: a Delivery Manager agent that answers 'why is this sprint going to miss'. A PMO agent for multi-project visibility. Mazylon isn't one more tool — it's a team of agents that collaborate.
30 minutes with one of our founders. Live demo on your Jira if you want. No commitment.