Calculated planning for teams

See what
your team can deliver
with the current inputs

RunMyPlan calculates the order of work, taking dependencies, skills and calendars into account.

See what fits into the plan, where work will wait and which inputs affect the delivery date.

Beta · start with one team
Separate tasks. One delivery date.
Team plan4 work items
BackendModel2 days
BackendAPI2 days
FrontendScreen3 days
QATesting2 days
QA calendarDay 6 · unavailable
6
Forecast duration
8working
days
Your tracker stores tasks.RunMyPlan adds a planning calculation layer.01 / The plan and its constraints

See what shifts the plan.

Scroll the timeline left or right.

Task / role
Working days 1–5Working days 6–10
01020304050607080910
Team plan4Summary row
Plan · 8 days
QA workloadNo added work
No additional work
Data modelBackend · 2 days
Model · 2 days
Settings screenFrontend · after the model
Screen · 3 days
APIBackend · after the model
API · 2 days
Scenario testingQA · after API and screen
No QA
QA · 2 days
Done
What changed?Choose a scenario

QA calendarFour work items, API and screen in parallel, and one day when QA is unavailable.

What makes up the timeline.

The same scenario as on the chart. See how a changed constraint contributes to the total duration.

Why does it take 8 days?

QA calendar
012Modelworking days
02
API · 2 daysScreen · 3 days
3Parallel workmax(2, 3) = 3 days
031QA calendarday 6
042Testingworking days
Contribution to duration
2 + max(2, 3) + 1 + 2
Whole plan
=
Plan duration8working days

The API and screen are ready by the end of day 5. QA is unavailable on day 6, so testing starts on day 7.

API and screen work run in parallel: the longer branch determines the duration, followed by waiting and testing.

01

Confirm the inputs

Tasks and estimates, dependencies, roles and skills, calendars and priorities. Missing data needs a decision from its owner.

Built on confirmed data
02

Get a calculated plan

Work sequences and forecast dates that account for your constraints. You can also see work that could not be scheduled.

Deterministic calculation
03

Discuss the impact

Review bottlenecks with your team. When inputs change, calculate a new plan and compare the results.

A forecast to inform the discussion

One change.
Clear consequences.

Who can take the work, when it can start and what moves next. Each example shows specific inputs and their effect on the plan.

PeopleExample 01

Leave and time off

Testing is ready on Monday and takes 2 days. Anna is on leave Monday–Tuesday. Ilya has the required skills and is available on those days.

With Anna, testing finishes on Thursday; with Ilya, on Tuesday.

The calculation can select an alternative based on task requirements and availability. Your team decides whether to adopt the resulting plan.

Working timeExample 02

Meetings and available time

The working day is 09:00–17:00. Two meetings take 2 hours and tasks take 5 hours. The 14:00–15:00 slot is free.

A meeting from 14:00 to 15:00 fits without shifting tasks.

Select “Added” to see how available time changes. The team chooses the meeting time.

PeopleExample 03

Work on another project

Payment testing is ready on Monday and takes 2 days. Boris is busy on another project Monday–Wednesday. Vera has the required QA skills and is available Tuesday–Wednesday.

Boris finishes on Friday. Vera can finish on Wednesday.

Other commitments are already included in the inputs. Selecting an alternative depends on skills and availability.

PeopleExample 04

A team member leaves

Masha is unavailable from Wednesday. Migration is ready to start on Wednesday and takes 2 days. Oleg is qualified and available Thursday–Friday.

Masha is no longer available. Oleg can do the work on Thursday–Friday.

The plan accounts for the departure date. Remaining work can be assigned to another qualified person.

CalendarExample 05

Change freeze

Deployment is ready on Tuesday and takes 1 day. Deployments are blocked Tuesday–Wednesday. Another day of testing is needed afterwards.

Deployment is on Thursday, testing on Friday.

The restriction blocks deployment specifically. Testing starts after deployment finishes.

CalendarExample 06

Holidays and non-working days

Work starts on Tuesday and needs 2 working days. In this example, Wednesday is a public holiday.

The two working days are Tuesday and Thursday. Work finishes on Thursday.

The holiday uses no working capacity and does not count as a task working day.

Task flowExample 07

Available, but no work is ready

Development runs Monday–Thursday, followed by 1 day of testing. QA is available Wednesday–Friday, but no other tasks are ready.

Two available QA days appear as a gap in the flow.

This is a reason to review dependencies and task breakdown. The gap may be a justified buffer; it does not prove that something is wrong.

External conditionsExample 08

External dependencies

The test environment will be ready by the end of Wednesday. Testing takes 2 days; QA is available all week.

Testing starts on Thursday and finishes on Friday.

The start depends on the test environment being ready. The team provides the external readiness date; it is not a guarantee from the external party.

Plan changesExample 09

Unplanned urgent task

One QA person: 2 days for “Payments”, then 1 day for “Report”. Before Monday begins, an urgent 1-day test is added at the highest priority.

Both planned items shift by 1 working day.

Payments: Mon–Tue → Tue–Wed. Report: Wed → Thu. You can see exactly which work moves and by how much.

Three more inputs: profiles, estimates and flow rules
Person’s profileExample 10

Roles and skills

The task needs a Backend developer with SQL for 1 day. It is assigned to Lena, who has the right profile and is free on Tuesday. Dima is free on Monday, but works in Frontend.

Lena works on Tuesday: both her profile and availability fit.

Free time alone does not make someone qualified. This example checks a specified assignment.

EstimatesExample 11

Changing a work estimate

API work is estimated at 2 days, followed by 1 day of testing. The new API estimate is 3 days. All other inputs stay the same.

Testing moves from Wednesday to Thursday: +1 working day.

The API duration changed. The linked testing keeps its own estimate, but starts later.

Flow rulesExample 12

Priorities and WIP

WIP = 1: one work item at a time. One person, 2 days for API and 1 day for a report. Both are ready on Monday. Compare “API first” with “Report first”.

With the report first, it finishes 2 days earlier and the API finishes 1 day later.

The overall finish is still Wednesday. The calculation respects the selected order and WIP without adding resources.

Each example is a separate situation with specified inputs. Available rules and scenarios depend on your plan. Decisions about people, meetings and commitments stay with the team.

Work in your tracker.
Check your plan in RunMyPlan.

Start with one task source. Import your backlog from XLSX and add a working calendar.

Your team updates the tracker through its usual workflow.

XLSX import

Upload tasks from a spreadsheet and confirm the column mappings. Example files are available to help you get started.

Available in beta

Google Calendar

Connect your calendar to account for meeting time in calculations. Connection availability depends on your Google account.

Available in beta

Jira Cloud

Read-only task import. Connection availability depends on your project settings.

Limited access

Yandex Tracker and other sources

If your source can export tasks to a spreadsheet, prepare an XLSX file for import. Direct connectivity depends on the source.

Start with XLSX

Start with one team.
And a specific question about the plan.

For example: what fits within current resources, where queues form and which inputs affect the finish date.

Contact support

A useful starting scope

  • One team and one main task source
  • Estimates, dependencies and calendars you can confirm
  • A data owner who can confirm the inputs

Run your first calculation and review which constraints affect the timeline.

If you need help with your first calculation, we can discuss assisted setup separately.

Questions
answered.

Is this another task tracker?

RunMyPlan adds a calculation layer for planning. It helps check whether a plan is feasible while your team’s daily work stays in its familiar task system. We check connectivity for your setup separately.

Does RunMyPlan guarantee the calculated date?

No. A calculated date is a forecast based on confirmed inputs. Estimates, availability, priorities and dependencies can change. People decide on external commitments, considering risks and buffers.

Does AI plan instead of the manager?

The plan itself is calculated by a deterministic algorithm. AI assistance with data preparation is planned. The team confirms rules, inputs and management decisions.

Do we need to change Scrum or Kanban?

The service does not replace your team’s practices. Try it alongside your existing process as an additional planning layer. Its fit with your rules can be discussed during the pilot.

Can we start with several teams?

You can set up several teams. Starting with one makes the first calculation simpler. If people work across teams, confirm their availability for each calculation.

How do we get started?

Sign in to the beta, create your workspace and set up a team. Start with one XLSX task set. Contact support if you need help.

Start with your team’s plan

Create a workspace, set up your team and upload your backlog. Your first calculation helps you check the inputs.