For delivery managers and team leads

Recalculate your team's plan in minutes

Once your data is ready, RunMyPlan accounts for the backlog, dependencies and team availability in every calculation. Tasks and daily work stay in your usual tracker.

01Less manual replanning02Your usual tracker03Real constraints
Beta · start with one team
≈30 sRecalculation estimate
≈1 hInitial setup estimate

Indicative figures. Actual time depends on data volume and quality.

Three answers to guide a decision
Baseline plan4 work items / 8 days
01
What fits?Model, API, screen and testing

The API and screen are built in parallel.

02
Where does work wait?QA is unavailable on day 6

Testing takes days 7–8. That is part of the timeline.

03
What if urgent testing is added?The planned finish moves back by a day
8→9working days

Urgent work takes day 7 for the same QA specialist.

The impact is visible. The team confirms the priority.

How many hours go into
rebuilding plans?

Two questions about your process. See how planning time could change if RunMyPlan handles the calculation.

Multiply monthly iterations by time per iteration. Enable JavaScript for an interactive estimate. Compare the time with your own plan. Try it with your plan →

Discuss the delivery date.
And what affects it.

The focus is on work readiness and delivery constraints. A fully booked team alone does not explain a finish date.

01 / Feasibility

Work starts when conditions allow

Estimates, dependencies, skills and calendars affect scheduling. Tasks that cannot be scheduled remain visible in the result.

02 / Delivery

Work order affects the overall finish

See what helps deliver the result sooner. Additional work is useful when it does not create another queue.

03 / Bottlenecks

Waiting has a concrete reason

A queue for a specialist, dependent work or an unavailable environment becomes something to act on, rather than a guess about dates.

04 / Explanation

Walk through the forecast with stakeholders

Show how the date is calculated and which inputs affect it. The team decides on commitments and buffers.

Check the impact of a change.

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.

Explain where the date comes from.

The same scenario as above: parallel work, waiting and testing make up the forecast. Adding all task durations does not give the delivery time.

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.

Understand the impact.
Then decide.

Estimates, availability or priorities changed? Update the inputs and run a new calculation before agreeing a date.

Review the plan before the meeting

Start the discussion with specific work and dates. Check a new scenario instead of manually moving every related task.

Make the cost of urgent work visible

Which work will give way to the urgent task? How far will the finish move? Discuss the impact of the chosen priority.

Check an available slot

Add technical debt, a small task or keep a buffer? Define a scenario and check its impact on the main plan.

Before recalculating, review the summary of input changes. The team chooses additional tasks; completed plans can be compared manually.

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.

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.

Confirm the inputs.
Calculate. Agree on the next step.

You control the data and rules. The algorithm calculates the work sequence and forecast under those conditions.

01

Prepare your data

Import your backlog from XLSX and confirm estimates, dependencies, people and availability.

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

Agree on changes to scope, priority or availability. A new calculation helps assess the impact; the team makes the decision.

A forecast to inform the discussion
Same inputs and rules, same result

Dates are calculated by a deterministic algorithm. The result can be reproduced with the same data snapshot and the same algorithm and rules version.

Your usual tracker for daily work.
RunMyPlan for calculation.

Daily tasks stay in your system. For the first calculation, prepare your backlog in XLSX and confirm the team's 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

Test the value
with your team.

Take one task source and a specific replanning situation. Compare the first result with how you usually rebuild the plan.

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

Measure the time spent preparing and revising the plan. Note which decisions the result helped you make.

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

Questions
answered.

We already plan quickly. What else should we test?

Then test other questions: can you tell what urgent work will delay, why the next stage is waiting and how the timeline adds up? Then try a complex case of your own and see whether the calculation helps you decide.

Do 30 seconds and one hour apply to every team?

No. These are indicative figures: about 30 seconds to recalculate and about an hour for initial setup. Actual time depends on data volume and quality. Compare them with actual times on your own plan.

Do we need to move our work from Excel or our tracker?

Your team keeps its usual tracker and daily workflow. Data must be prepared for calculation. Import support varies by source; the connection method is checked separately.

Does RunMyPlan guarantee the delivery date?

No. The date is a forecast based on confirmed inputs. Estimates, availability and priorities may change. The team assesses buffers, risks and external commitments.

Can every available slot be filled automatically?

Available time must be matched with ready tasks, skills and dependencies. You can test a scenario proposed by a person; automatic selection of additional tasks is planned for future development.

Does AI calculate the dates?

No. A deterministic algorithm calculates the plan. The team confirms the data and rules.

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.