It's not a bug, it's a feature!
- 628 views
The curse of Project is that it’s functionalities seem intuitive and we believe we know what they mean and how to use them implicitly. Yet, although logical when you know them, Project features are ...
The curse of Project is that it’s functionalities seem intuitive and we believe we know what they mean and how to use them implicitly. Yet, although logical when you know them, Project features are numerous and quite a few are complex. In addition, almost all Project/Project Server features require that you follow at least some procedure to be able to use them effectively. The curse ends with many people running Project/Project Server at least once, some using it for basic initial schedule development and a very few using it in the full capability. Being human, we tend to blame it on the tool so – it must be a bug!
The goal of this presentation is to alter the negative usage statistics for Project – at least for those of you who will attend! We will identify five simple but key areas; technical or procedural – that are typically misused or are not used at all due to the misconception. For each of those we will shortly show what exactly is a problem and propose the solution. Among the five areas, we will be discussing effects of dynamic scheduling, options for re-planning, options for automatic resource scheduling (or lack of those) and options for tracking and reporting on task progress.
This session is for everyone who uses Project (with or without the server component) or needs to support others using Project in their organizations. Those of you who have conceptual complaints about some Project/Project Server features are welcome to share them (I cannot promise to answer them but I will for sure use them in consecutive presentations).
- Total Views
- Views on SlideShare
- Embed Views