TASKey TEAM is not traditional construction based project management software. TASKey TEAM employs a distributed management method that integrates general management and project management methods.
The simple method works for any sized team and then connects teams together to create an enterprise wide solution. The focus is on helping individuals and teams to be more productive, and automatically aggregating key team information in real-time to provide managers with the information they need to make sound decisions.
Some examples of the differences between traditional project management software and TASKey TEAM distributed management software are:
|Does not manage goals and objectives or assumptions that are critical for success. || |
Integrates many general management planning and coordinating methods including the management of goals (outcomes), objectives (outputs) and assumptions.
|The majority of people tend to intermittently use project management software for drawing schedules of tasks/activities. Project managers who gain direct benefits usually have an assistant to operate the software and maintain project data. ||Each individual gains direct benefits from using TASKey TEAM, and indirect benefits from a significant reduction in the effort required to keep management informed. Plus management receives the real-time, relevant information they need to make sound decisions.|
|Works at project and task/activity levels only. ||Works at project, task/activity and action levels. The action level is essential because it breaks tasks into meaningful actions that must be done to successfully complete a task/activity. |
|Does not connect to To Do lists of simple actions. ||Connects projects and tasks/activities to To Do lists of simple actions (like most people write on a daily basis to remind themselves of the things they need to do).|
|Schedule bars need to be updated manually (usually by estimating % complete). ||Schedule bars are automatically updated when actions are completed.|
|Users need to check schedules to see if other peoples' changes affect them. ||Users are notified of schedule changes that affect them and when scheduling problems are resolved.|
|Project schedules are related to organisation breakdown structures. ||Project and task schedules are team based and customised for each user - so they only see relevant information.|
|Designed for single, usually complex, projects. ||Designed for multiple projects, but can be used for single projects.|
|Allows dependencies between tasks to automatically update the duration of project activities. This is helpful in construction type projects were tasks need to be done sequentially, but it is unhelpful where the sequence of effort can be highly variable (as is the case in business situations). ||Maintains parent-child task relationships, but doesn't employ dependencies or Critical Path Methods.|
|Top level tasks can only be used to span the sub-tasks (earliest start and latest end). ||Managers can set a task length and allow team members to organise their tasks within the allocated time. This facilitates flexibility and allows multiple tasks to be done concurrently.|
|Diary/calendar type alarms are not usually provided. ||Alarms can be attached to any action.|
|Designed to help the project manager control a project. ||Designed to help people (including project managers) doing projects and tasks, and to provide aggregated real-time data to management (including project managers).|
|Relates to a fairly rigid organisation structure. ||Independent of organisation structure, so teams can be easily created, modified and dissolved.|
Ready to check it out? Order Now
Want to see detailed information and functions? View our Product Page
Need to ask some questions? Contact Us