How we do it

We want you to change the plan. Life is constant change, and in order to succeed your plan must change with it.

And it should be easy to do.

Schedule versions

With traditional tools you don't change the working plan - because thats the only one you have. There's a single place to look at all the tasks and milestones, and any changes are reflected instantly.

You can still do this with FlyTrue.io, but we also encourage you to make bigger changes when needed.

Each project has a working version. But you can clone and compare separate versions of the whole project:

Compare tech-debt pay down now vs. later scenarios
See different outcomes based on resourcing
Visualise feature set trade-offs

And once you're happy, any version can become the working version for that project.

Everyone's task list is instantly updated, and all progress and to-do items are carried over.

Execution mode

While working towards the next goal - the only thing that matters is the next useful deliverable. (And this can be technical foundations too!)

Limiting the overall view helps narrow the team's focus and discussions as well. They can have productive conversations without getting pulled too far away from what they're trying to achieve right now.

Planning mode

All the usual stuff: tasks, milestones, allocations and dependencies.

You can also define a milestone outcome, and then tick-off completed parts as you go during execution.

Doing all of this work in the first place is usually aimed at helping some humans, we want to make sure that's always front and centre.

Updates pulled from where the devs are

Asking for updates constantly is a lot of human effort, and no one likes feeling like a micromanager.

We get simple, straightforward updates from wherever the people are (Slack, Teams, Discord, email).

Schedule Recommendations

You probably have an appreciation for just how much hidden work there is in 'herding the cats'.

We help introduce those unteachable-without-feeling-it secrets to executing a project successfully, so you dont have to do all the coaching to get the results you want.

Here's just a few:

Prioritising continual value delivery
Forcing integration early and often
Explicit handover tasks
The bug rate