Tandimy is an all-in-one AI project management platform that combines Kanban boards, Gantt charts, Sprints, OKR tracking, RACI matrix, workload planning, smart automations, and integrations with Outlook, universal IMAP email, Google Drive and Slack — in a single connected workspace.

Yes. Tandimy offers a completely free plan with no time limit and no credit card required. You get 1 member, 1 project, basic Kanban, 1GB storage and 20 AI credits per month. Paid plans start at $19/month.

How does Tandimy AI work?

Tandimy AI reads your project data in real time — tasks, deadlines, assignees — and generates instant recommendations: risk detection, bottleneck identification, workload balancing suggestions, and calendar planning. You can also chat with the AI in natural language to ask any question about your projects.

What integrations does Tandimy support?

Tandimy integrates with Outlook (Microsoft 365 inbox), universal IMAP mailboxes (Yahoo, iCloud, ProtonMail Bridge — converts emails to tasks), Google Drive (attach files to projects), Slack (real-time notifications), plus Webhooks and a REST API for custom integrations.

Is Tandimy GDPR compliant?

Yes. All Tandimy data is hosted in the EU, encrypted in transit and at rest. The platform supports two-factor authentication (2FA), audit logs, role-based permissions, and SSO/SAML for Enterprise plans. Full GDPR compliance.

How is Tandimy different from Asana, Trello or Monday?

Tandimy combines everything competitors offer separately — Kanban, Gantt, Sprints, OKR, RACI, workload — and adds native AI analysis, no-code automations, Outlook/IMAP/Drive/Slack integrations, and flat team pricing with no per-seat billing. All in one platform, starting free.

Can I manage freelancers and contractors in Tandimy?

Yes. From the Growth plan, you can add external contractors and freelancers, assign them missions, track their progress, and control exactly what they can see — without exposing sensitive internal information.

Does Tandimy have automations?

Yes. Tandimy lets you create no-code automation rules with trigger + action logic. Example: when a task is overdue → send a Slack alert + email to assignee. 15+ triggers and 8+ actions available, starting from the Starter plan.

Continue reading

🔁 Scrum Guide · Tandimy Blog

Sprint Retrospective: How to Run It Effectively

A sprint retrospective that boils down to "all good, let's keep going" is worthless. Here's a 5-step format to turn this Scrum ritual into a real engine of continuous improvement, sprint after sprint.

✍️ Tandimy Team🗓️ 2026⏱️ 8 min read

A continuous improvement loop

Observe

Understand

Decide

Apply

Why the retrospective is the most underrated ritual

In an agile cycle, sprint planning organizes upcoming work, but the retrospective is one of the five official events in the Scrum Guide, dedicated to improving how the team itself works — not the product, the process. Skipped or rushed in 5 minutes, it lets the same friction points repeat sprint after sprint.

A good retrospective doesn't look for a culprit: it looks for a limited number of concrete actions that actually get followed up on next sprint.

The 5-step format

Open (5 min)

Recap the goal of the sprint that just ended and the ground rules for the retro: talk about the process, not the people.

Gather facts (10 min)

Everyone individually notes what went well, what got stuck, and what surprised them — before any group discussion.

Generate insights (15 min)

Group similar points and discuss causes, not just symptoms: why did this blocker show up in the first place?

Decide on actions (10 min)

Pick 1 to 3 concrete actions max, each with an owner — not a list of 15 good intentions.

Close and follow up

Create each action as a real task linked to the project's epics, to check at the start of the next sprint. Without follow-up, the retro stays symbolic.

Golden rule: a retrospective with no action created in the project tool is just another meeting, not an improvement ritual. Always turn decisions into assigned tasks.

3 retrospective formats worth trying

Start / Stop / Continue

What the team should start doing, stop doing, and keep doing. Simple and effective to get started.

Mad / Sad / Glad

Sort the sprint's feelings by emotion: what frustrated, disappointed, or satisfied the team. Useful after a tense sprint.

4L (Liked, Learned, Lacked, Longed for)

A richer format for mature teams: what was liked, learned, missing, and wished for.

Sailboat

Visualize favorable winds (what pushes the team forward), anchors (what slows it down) and rocks (upcoming risks) as a boat.

To go deeper, see the official resource Scrum.org: What is a Sprint Retrospective and the method's background on Wikipedia.

Turn your retrospectives into tracked work

Create the actions decided in the meeting directly as tasks linked to the next sprint. Free.

Try it free →

Frequently asked questions

How long should a retrospective last?

About 45 minutes for a 2-week sprint: enough to get to the bottom of things without becoming an endless meeting that discourages participation.

Who facilitates the retrospective?

In Scrum, it's typically the Scrum Master who facilitates, without imposing their own conclusions. The whole team participates and decides on actions collectively.

Should you run a retrospective every sprint?

Yes, it's one of the 5 official Scrum events. Skipping a retro "because everything's fine" is often exactly the sign that one is needed.