From: John Sullivan Date: Mon, 30 Jun 2008 01:55:08 +0000 (-0400) Subject: planner-el.texi (Keeping Track of Time): Recover paragraph that had X-Git-Url: https://repo.or.cz/w/planner-el.git/commitdiff_plain/b29398b9e8a41a5f6aeb70b95f7872d8442d6768 planner-el.texi (Keeping Track of Time): Recover paragraph that had been lost sometime in 2005. Closes #8184. --- diff --git a/ChangeLog b/ChangeLog index bb95b10..f29aa25 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2008-06-29 John Sullivan + + * planner-el.texi (Keeping Track of Time): Recover paragraph that + had been lost sometime in 2005. + 2008-05-18 John Sullivan * Release Planner 3.42. diff --git a/planner-el.texi b/planner-el.texi index dcc9d18..b900216 100644 --- a/planner-el.texi +++ b/planner-el.texi @@ -5922,8 +5922,14 @@ just how much time you spend working each day. If you add estimates to your task descriptions, you'll also be able to use this information to improve your time estimation skills. -Here's how you can keep track of the time you - +For example, I had converted the TODO my teammate sent me into entries +in my JapanProject plan page, and before starting my work I came up +with rough estimates of the time it would take me to do the tasks. I +also marked which tasks I felt were best suited for my coworker so +that he could get started without worrying about conflicts. I like +working on little tasks first, so I estimated the time it would take +me to complete each task and sorted by my estimates using the +@code{sort} command and some cutting and pasting. Then the fun began. I wanted to see if I could match my estimates. Before I started working on a task, I used @kbd{C-c TAB} to mark it