New Inventory Management Softwares Online

The following may apply in general, or only to specific products.

1. May not be derived from a sound project management method. For example, displaying the Gantt chart view by default encourages users to focus on timed task scheduling too early, rather than identifying objectives, deliverables and the imposed logical progress of events (dig the trench first to put in the drain pipe).

2. May be inconsistent with the type of project management method. For example, traditional (e.g. Waterfall) vs. agile (e.g. Scrum).

3. Focuses primarily on the planning phase and does not offer enough functionality for project tracking, control and in particular plan-adjustment. There may be excessive dependency on the first paper print-out of a project plan, which is simply a snapshot at one moment in time. The plan is dynamic; as the project progresses the plan must change to accommodate tasks that are completed early, late, re-sequenced, etc. Good management software should not only facilitate this, but assist with impact assessment and communication of plan changes.

4. Does not make a clear distinction between the planning phase and post planning phase, leading to user confusion and frustration when the software does not behave as expected. For example, shortening the duration of a task when an additional human resource is assigned to it while the project is still being planned.

5. Offer complicated features to meet the needs of project management or project scheduling professionals, which must be understood in order to effectively use the product. Additional features may be so complicated as to be of no use to anyone. Complex task prioritization and resource leveling algorithms for example can produce results that make no intuitive sense, and overallocation is often more simply resolved manually.
Some people may achieve better results using simpler technique, (e.g. pen and paper), yet feel pressured into using project management software by company policy (discussion).

6. Similar to PowerPoint, project management software might shield the manager from important interpersonal contact.

7. New types of software are challenging the traditional definition of Project Management. Frequently, users of project management software are not actually managing a discrete project. For instance, managing the ongoing marketing for an already-released product is not a “project” in the traditional sense of the term; it does not involve management of discrete resources working on something with a discrete beginning/end.

8. Groupware applications now add “project management” features that directly support this type of workflow-oriented project management. Classically-trained Project Managers may argue whether this is “sound project management.” However, the end-users of such tools will refer to it as such, and the de-facto definition of the term Project Management may change.

When there are multiple larger projects, project management software can be very useful. Nevertheless, one should probably not use management software if only a single small project is involved, as management software incurs a larger time-overhead than is worthwhile.

Ps: Thats Criticisms of project management software but not to all specific tools and software. But normally it works like that.

Task management software tools abound in the marketplace. Some are free; others exist for enterprise-wide deployment purposes. Some boast enterprise-wide task creation, visualization and notifications capabilities – among others – scalable to small, medium and Fortune 100 size companies, from individual projects to ongoing corporate task management. Did we always use Task Management softwares for certain project?

Project management and calendaring software also often provide task management software with advanced support for task management activities and corresponding software environment dimensions, reciprocating the myriad project and performance activities built into most good enterprise-level task management software products.

Software dimensions criss-crossing nearly all lines of task management products include task creation, task visualization, notifications, assign resources, compatibility, configurability, scalability, and reporting

• Task creation encompasses collaborative capabilities for turning ideas into actions (tasks). Includes activities involved before setting tasks, particularly patterns of collaboration involving planning
• Task visualization encompasses presentation of tasks, most often through time and list forms. Priority visualization encompasses classification (e.g., budget, time, stakeholder) and mechanism (e.g., color code or text). Calendaring covers scheduling (e.g., availability, meetings, appointments and other potential conflicts) and notifications.
• Notifications encompass configurable settings for informing past, present and pending deadlines.
• Assigning resources encompasses the ability to delegate tasks and tools to single or multiple people.
• Compatibility encompasses the ability of a task management environment to connect to other systems, software and environments. It includes setting a structure and restrictions on communication going from the task management environment to other software, systems and environments.
• Configurability encompasses ability to add, remove and manage functionality and usability in task management environments.
• Scalability encompasses ability to perform a task properly when a change in the quantity of users is done to meet the specific task requirements.
• Reporting encompasses presentation of information by displaying either in tabular or graphical display

So, what do you think about Task Management now? I guess not many people use it wisely unless only few peoples. How about Task Management Softwares? What do you think we can do with that for future?

Credit to Wikipedia and inFlow Inventory Software