Skip to main content

TimeTo

I just licensed a new software for my personal organization system: TimeTo. It tries to conciliate your schedule with you to-do list, automatically scheduling your tasks based on priorities and deadlines.
It has helped me in maintaining the concentration on what I’m doing at each time and how much time I spend on doing each type of task. Additionally, I have a very powerful way to complete my timesheet. I can tell you exactly what I was doing at a specific time in the past.
It is not easy to conciliate it with GTD and I still keep my lists on my Palm but I have improved my focus and I’m achieving more. I suggest you to give it a try.

Comments

Wronowski said…
Today I found an interesting post about TimeTo - If you want more information: http://www.murtworld.com/2005/11/timeto-dynamic-scheduling.php

Popular posts from this blog

Tools for blogging

Maintaining a blog sometimes is a difficult task, specially when you’re in the middle of a battle. It takes discipline and the belief that your ideas and experience could improve someone else’s. There are some tools to assist you in writing a blog but I discovered that my old palm and a simple sheet of paper can work better than new editors or browser plugins that allow you to post from any webpage. Maybe I’m facing a corollary of KISS principle (keep it simple, stupid). On the other hand, reading many blogs is almost impossible without a specific tool. I had a good time using RSSOwl and now I’m using GreatNews , both are free. I tried the Google Reader version of it but I’m usually offline when reading the blogs – usually at the airport. I also use my iPod to follow podcasts. If you’re a project manager I recommend Jerry Manas Project Results Podcast . What are you using to follow my blog? Leave your experience as a comment here!

Priorities & MoSCoW

One of the most important tasks a PM has on a software development project (maybe in all projects) is setting priorities. Usually time and money is shorter than everybody would like and you have to choose what to develop and what not to develop. It takes communication skills, a lot of negotiation and, at the end; everybody is a little bit frustrated… If your team is developing software iteratively and incrementally (and you should… but that’s a theme for another post), you have to prioritize each iteration sub-scope. To make scope more clear, at my company we adopt the MoSCoW list. I believe it originally has roots on DSDM (although it is used similarly on SCRUM, UP and it has elements of Cockburn’s actor-goal list) and it is a very powerful tool. Simply stated, it is a list of requirements (or actor-goals, or use case titles…) each one prioritized with a letter MSCW (Must, Should, Could and Won’t – that’s the origin of MoSCoW list name). I simplify the explanation to my clients, key-u