IHRIS Plan Development: Difference between revisions
From IHRIS Wiki
Sturlington (talk | contribs) (Initial status update; please update with changes) |
Sturlington (talk | contribs) |
||
Line 13: | Line 13: | ||
* All documentation to be distributed to technical advisory group for feedback | * All documentation to be distributed to technical advisory group for feedback | ||
* Open questions about the workforce planning model need to be resolved with technical advisory group (see [[Questions for Discussion]]) | * Open questions about the workforce planning model need to be resolved with technical advisory group (see [[Questions for Discussion]]) | ||
* Finalize workshop report and submit to RKM team | * Finalize workshop report and submit to RKM team (Carol) | ||
* Arrange intensive consultation with workforce planning export (participant in workshop) on-site to vet features, requirements and use of the model for the software | * Arrange intensive consultation with workforce planning export (participant in workshop) on-site to vet features, requirements and use of the model for the software | ||
* Hire a user interface designer if there is budget for it | * Hire a user interface designer if there is budget for it | ||
* Test software as it is being developed and get feedback from technical advisory group; keep documentation updated with changes | * Test software as it is being developed and get feedback from technical advisory group; keep documentation updated with changes | ||
* Write help and user manuals in consultation with technical advisory group | * Write help and user manuals in consultation with technical advisory group |
Revision as of 14:10, 29 February 2008
Development Update – iHRIS Plan - As of March 2008
iHRIS Plan Core
Developer: Luke
Status: initial features list (Planned Features -- Software and Planned Features -- Workforce Projection Model), requirements and use cases are completed; workshop report has been drafted
Next milestone: release version 1.0 by June for pilot testing; this is an initial proof-of-concept version
To-do’s
- All documentation to be distributed to technical advisory group for feedback
- Open questions about the workforce planning model need to be resolved with technical advisory group (see Questions for Discussion)
- Finalize workshop report and submit to RKM team (Carol)
- Arrange intensive consultation with workforce planning export (participant in workshop) on-site to vet features, requirements and use of the model for the software
- Hire a user interface designer if there is budget for it
- Test software as it is being developed and get feedback from technical advisory group; keep documentation updated with changes
- Write help and user manuals in consultation with technical advisory group