The following items have been put forward as requested functionality for KPlato but have not yet been discussed in detail:
KPlato should be able to handle the following planning tasks:
Financial / Budget Calculations [Anders Johannsen]
The ability to replan based on scope changes [Chris H] [Brad Hards]
The ability to balance resources across multiple projects [Chris Clarke]
KPlato should be able to perform the following types of calculations:
Modeling using statistics and probability [Jim Sabatke]
Monte Carlo simulation [Jim Sabatke]
Schedule Variance [Jim Sabatke]
Effort Variance [Jim Sabatke]
KPlato should be able to perform the following file related activities:
Define templates for projects [Andrew Branch]
Define templates for task groups [Brad Hards]
Import MS Project files [Richard Bos]
KPlato should be able to perform the following general functionality:
Calendar functionality [Anders Johannsen]
Time reporting functions [Anders Johannsen]
Report generation [Anders Johannsen]
Feedback system [Anders Johannsen]
The following items are not expected to be implemented in the first release, but could be incorporated into subsequent releases:
Assign ownership to tasks
Networked planning functions so task owners can do their own planning and have it roll up into a master plan
Easily copy the project files between a laptop and a desktop
Incorporate permission and access controls for users, groups, and managers
Email notifications of significant events
Designate tasks/schedules interruptible or uninterruptible, with startup and shutdown penalties
KPlato should be able to support the following procedures:
Manage a change order mechanism