We had a great question from a Professor at the University of Iowa last week that I would like to share. He is looking to set up a workshop for Industrial Engineering and was evaluating software tools for task analysis, and he wanted to be sure that TaskArchitect could track changes.
We pointed out that there are several ways you can use TaskArchitect to manage changes (or prevent them) in a large task analysis,
1. Manage how far any given task is analyzed. In order to keep track of which tasks do not need further analysis, you can mark a task as 'stopped'. Stopped tasks can be edited, but sub-tasks cannot be added to them. Stopped tasks are marked with a red lock symbol. When you have decided that a task analysis is correct and needs no more review or changes, you mark the task as complete. Completed tasks cannot be edited and subtasks cannot be added. Tasks that are completed have a green check symbol next to them.
2. Identify who is making changes and when. TaskArchitect records the user id and date of last change for each task. You can see the information at the bottom of the task details window.
3. Collaborate with others so that many tasks can be analyzed in parallel. If you have multiple copies of our software, you may detach a string of tasks and send it to another user to work on an reattach later.
4. Create a project specific property. You can create a specific task property to record anything else you might want to track. For example, if you had two teams working on a task you could create a task property so that the team editing the task can select who last worked on the task.