Planfix use cases: Difference between revisions
From Planfix
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 11: | Line 11: | ||
*... | *... | ||
== Project: Working with Office Inc. == | |||
Tasks: | Tasks: | ||
| Line 21: | Line 21: | ||
* ... | * ... | ||
==Project: Orders on eshopexample.com== | |||
Tasks: | Tasks: | ||
Latest revision as of 04:34, 12 March 2019
The main entities that Planfix uses are Projects, Tasks, and Actions (more about using them). These names don't mean you can only use Planfix for project-based work. Here are some examples of project and task names that illustrate different use cases for Planfix:
Project: Opening a store at W 89th St
Tasks:
- Order furniture
- Health clearance
- Firefighters: purchase equipment
- Firefighters: get licensed
- ...
Project: Working with Office Inc.
Tasks:
- 2 printers and a fax machine
- Laptop for chief accountaint
- Meeting with boss
- Classroom delivery
- ...
Project: Orders on eshopexample.com
Tasks:
- Order #125948
- Order #125949
- Order #125950
- Order #125951
- Order #125952
- ...
(About the last example: You can use the Task-Email feature to automatically upload tasks from different sources)
Take some time to think about what your approach will be for naming tasks and projects, and let your colleagues know what you decide.