User Tools

Site Tools


defining-tasks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
defining-tasks [2016/08/21 11:40]
127.0.0.1 external edit
defining-tasks [2016/09/01 10:53] (current)
Line 1: Line 1:
-Everyone has their own sense of what a project is or what a task is, and how far they want to refine that concept. As an example, let's say you need food for a party, so you create a task with the title "Get Food". What does that mean?+====== Defining Tasks ====== 
 +Everyone has their own sense of what a project is or what a task is, and how far they want to refine that concept. As an example, let's say you need food for a party, so you create a task with the title "Get Food". What does that mean?
  
 You could simply create a task for each food item. You could simply create a task for each food item.
   * Get Food   * Get Food
-  - Cake from Bakery +    * Cake from Bakery 
-  ​- ​Bread from Bakery +    ​* ​Bread from Bakery 
-  ​- ​Eggs from Corner Market +    ​* ​Eggs from Corner Market 
-  ​- ​Beer from Liquor Store +    ​* ​Beer from Liquor Store 
-  ​- ​Wine from Liquor Store+    ​* ​Wine from Liquor Store
  
 Or you can create a sub-task for each grocery store, with a sub-task under each store for each food item. Or you can create a sub-task for each grocery store, with a sub-task under each store for each food item.
   * Get Food   * Get Food
-  - Bakery +    * Bakery 
-    ​- ​Cake +      ​* ​Cake 
-    ​- ​Bread +      ​* ​Bread 
-    ​- ​Corner Market +      ​* ​Corner Market 
-    ​- ​Eggs +      ​* ​Eggs 
-  ​- ​Liquor Store +    ​* ​Liquor Store 
-    ​- ​Beer +      ​* ​Beer 
-    ​- ​Wine+      ​* ​Wine
  
 The implication here is that "​Bakery"​ isn't a task as in "​something to do", it's just a task for organization,​ a container to support other tasks underneath it. So tasks are used for organization as well as to itemize concrete things to do. Note also here that each food item task is a thing to "​get",​ not a thing to "​do"​. The implication here is that "​Bakery"​ isn't a task as in "​something to do", it's just a task for organization,​ a container to support other tasks underneath it. So tasks are used for organization as well as to itemize concrete things to do. Note also here that each food item task is a thing to "​get",​ not a thing to "​do"​.
Line 26: Line 27:
 For example: In this scenario there is a party, so perhaps you want a top-level task called Party with Get Food as one of the sub-tasks, and food items under that.  For example: In this scenario there is a party, so perhaps you want a top-level task called Party with Get Food as one of the sub-tasks, and food items under that. 
   * Party   * Party
-  - Get Food +    * Get Food 
-    ​- ​Bakery +      ​* ​Bakery 
-      ​- ​Cake+        ​* ​Cake
  
 Note here that Party was made a top-level task, and Get Food and related "​nodes"​ were shifted to be sub-tasks of Party. Note here that Party was made a top-level task, and Get Food and related "​nodes"​ were shifted to be sub-tasks of Party.
   * Birthday   * Birthday
-  - Party +    * Party 
-    ​- ​Get Food +      ​* ​Get Food 
-    ​- ​Send Invitations +      ​* ​Send Invitations 
-    ​- ​Decorate +      ​* ​Decorate 
-    ​- ​Clean House +      ​* ​Clean House 
-    ​- ​Get Gifts+      ​* ​Get Gifts
  
 But what is the party for? If it's a birthday then the party might just be one sub-task under that, and there are probably tasks other than just getting food. Again we create a new top-level task and shift everything else under it, then add new ones. But what is the party for? If it's a birthday then the party might just be one sub-task under that, and there are probably tasks other than just getting food. Again we create a new top-level task and shift everything else under it, then add new ones.
Line 43: Line 44:
 Finally, note above that with a random thought process, the various tasks seem out of order. Tasks don't necessarily need to be entered or displayed in the order in which they occur. But after tasks are created, it's easy to move them up and down in a way that makes more sense. Finally, note above that with a random thought process, the various tasks seem out of order. Tasks don't necessarily need to be entered or displayed in the order in which they occur. But after tasks are created, it's easy to move them up and down in a way that makes more sense.
   * Birthday   * Birthday
-  - Send Invitations +    * Send Invitations 
-  ​- ​Get Gifts +    ​* ​Get Gifts 
-  ​- ​Party +    ​* ​Party 
-    ​- ​Get Food +      ​* ​Get Food 
-    ​- ​Clean House +      ​* ​Clean House 
-    ​- ​Decorate+      ​* ​Decorate
  
 Task lists grow and get re-arranged like this all the time - as you explore each task you think about more specific things that need to be done. You might estimate a business project to take 50 hours but to document that you'll need to think about each milestone, and what needs to be done to achieve each goal. So tasks routinely get added, shifted, and moved around in whatever way seems most appropriate. Task lists grow and get re-arranged like this all the time - as you explore each task you think about more specific things that need to be done. You might estimate a business project to take 50 hours but to document that you'll need to think about each milestone, and what needs to be done to achieve each goal. So tasks routinely get added, shifted, and moved around in whatever way seems most appropriate.
Line 55: Line 56:
  
 Other examples for structuring ToDoLists are available: Other examples for structuring ToDoLists are available:
-  * Example for a [[./defining-tasks,​-consultant-example|consultant]] with clients +  * Example for a [[defining-tasks,​-consultant-example|consultant]] with clients 
-  * Example for a company [[./defining-tasks,​-employee-example|employee]]+  * Example for a company [[defining-tasks,​-employee-example|employee]]
  
defining-tasks.txt · Last modified: 2016/09/01 10:53 (external edit)