Project & Time Management Software

myAgilePomodoro is a time management software that brings you the best of two worlds: Agile's most common practices and the Pomodoro Technique®.

mAP is a free open-source, GPLv3, Java 6/7/8, 32/64-bit, utf-8, multilingual, skinnable,
standalone and portable application (no installer).

Main features

mAP is flexible: use it as a Agile software, a Pomodoro timer or simply a ToDo list.
mAP is meant for small to medium size teams and individuals.

  • Pomodoro: short / long breaks, interruptions / unplanned tasks, overestimations...
  • Pomodoro: full implementation of the technique + Sub-tasking
  • Import / Export: CSV, Excel 2003/07, XML, Google Drive
  • Agile: backlog management, story points, iteration...
  • Timer: ticking / ringing, mute, pause, resizing...
  • Charts: burn-down / up, target, scope, guide
  • Database: local SQLite / remote MySQL
  • System tray: progress icon, messages
  • Multilingual: English, French, Italian
  • Look and feel: themes








Pomodoro Technique®'s rules* vs mAP

* as per the official book of the Pomodoro Technique®.

Although mAP can be used to strictly follow the rules, it is flexible in many ways.

A Pomodoro Consists of 25 minutes Plus a Five-Minute Break

mAP allows shortening / lengthening pomodoros and short breaks.
mAP allows stopping automatically the timer at the end of pomodoros (workflow interruption).

After Every Four Pomodoros Comes a 15-30 Minute Break.

mAP allows shortening / lengthening long breaks.
mAP allows restarting a Set after stopping the timer.

The Pomodoro Is Indivisible. There are no half or quarter Pomodoros.

mAP allows voiding and shortening pomodoros.

If a Pomodoro Begins, It Has to Ring:
--> If a Pomodoro is interrupted definitively – i.e. the interruption isn’t handled – it’s considered void, never begun, and it can’t be recorded with an X.
--> If an activity is completed once a Pomodoro has already begun, continue reviewing the same activity until the Pomodoro rings.

Ringing and ticking sounds are customizable and possible to disable.
--> mAP allows pausing pomodoros' progression for later use.
--> mAP allows shortening pomodoros.

Protect the Pomodoro. Inform effectively, negotiate quickly to reschedule the interruption, call back the person who interrupted you as agreed.

mAP allows creating unplanned tasks and subtasks at any time and internal and external interruption tasks and subtasks during pomodoros.

If It Lasts More Than 5-7 Pomodoros, Break It Down. Complex activities should be divided into several activities.

mAP allows duplicating tasks and creating subtasks.

If It Lasts Less Than One Pomodoro, Add It Up. Simple tasks can be combined.

mAP allows merging tasks and subtasks.
mAP allows starting tasks and subtasks with no estimation.

Results Are Achieved Pomodoro after Pomodoro.

mAP measures accuracy and analyses errors (diff).
mAP allows creating burn-up and burndown charts.

The Next Pomodoro Will Go Better.

Just stick to mAP ;-)

Sub-tasking rules vs mAP

mAP implements two new rules to support sub-tasking.
We suggest these rules be added to the Pomodoro Technique®’s specification.

All the rules of the Pomodoro Technique® apply to sub-activities.

mAP allows creating, estimating and running subtasks.

Activities with sub-activities shouldn’t be estimated. Only sub-activities should.

mAP goes one step forward: it allows estimating and running parent tasks. Any change of pomodoros in a subtask is equally applied to its parent task.

Scrum's practices* vs mAP

* practices, artifacts, indicators...


mAP allows ordering the Backlog (Product Backlog), prioritizing the Iteration Backlog (Sprint Backlog) and managing the Release Backlog.


mAP may be used to monitor Sprint planning, daily Scrum, Sprint review and Sprint retrospective meetings with the Pomodoro Technique® (having breaks during meetings is not a bad idea).
Simply create tasks with a made-up type and set the estimate (time boxing). In the preferences, set the length of pomodoros and breaks that fits the meeting best.


mAP allows creating tasks and subtasks (items) with a set of pre-defined types (User Story, Epic…).
For convenience, tasks with type "User Story" present a skeleton of story ("As a {role}, I can…").


mAP allows setting the Iteration (Sprint) number on the tasks.
mAP allows iteration with number 0 for project ramp-up, initial technical stories, spikes…
mAP allows moving tasks from the Iteration Backlog back to the Backlog (descoping).
mAP allows moving tasks from the Iteration Backlog (In progress) to the Release Backlog (Done).
mAP allows setting tasks to Done-Done in the Release Backlog.
mAP allows re-opening tasks from the Release Backlog back to the Backlog (not Done-Done).
mAP allows prioritizing tasks AND subtasks in the Iteration Backlog.


mAP shows on the backlogs’ title bar the sum of story points (SP) of the tasks. For convenience, on the Release Backlog’s title bar, and when tasks are selected, it reads "V" (for Velocity).
mAP also shows the Productivity (story points per day) on the Release Backlog’s title bar when tasks are selected.


mAP allows creating burn-up, burn-down charts with target, guide and scope lines upon different configurable set of tasks.
A Scrum Master can easily create a Daily Burndown chart as a Product Owner can issue a Release Product Burn-up chart based on dates or a range of iterations.