tokarev

Amusingly, I've come to appreciate grammar and spelling mistakes in blog posts, as they hint the text wasn't written with AI

Route is in the early preview stage, there are no plans yet. Just register and you're set.

Currently the focus of our attention is on small software companies, but we believe that the milestone-based approach would be beneficial to projects in any industry. Milestones bring visibility - the project route is explicitly defined, everyone on the team sees where the project is headed. The other advantage is flexibility - since the project is divided into smaller parts, it's easier to spot problems as they arise.

Of course, this approach is not for all use cases. For example, it won't work for very short projects - too much hassle setting up all those milestones.

Actually, the most popular browsers of our target audience are Google Chrome (the lion's share), Safari and Firefox. Since supporting IE is such a pain, we decided to go without it, at least for now.

Route was designed with milestone-based workflow in mind. You create milestones, you set due dates on them, you specify goals for each milestone - at the end you get a nicely delineated route through the project plan. Trello is a more general solution.

Hi James, thanks for feedback! It is very helpful, since you've shown us that we need to demonstrate the relation b/w tasks, goals, milestones and backlog more clearly. The backlog holds tasks and goals which haven't been assigned to a milestone. Each milestone has its own tasks and goals (but you can move them to another milestone or the backlog if you need). In general, all the interesting stuff happens in milestones, while the backlog holds tasks and goals whose time has not come yet.

Thanks for response! Actually this pop-up behavior is intentional, so that you don't have to aim at the "next" button. The product tour is custom built - nothing fancy, just CSS3 animation.