Project Manager Role Description

From Open Source Ecology
Revision as of 18:02, 16 May 2015 by Marcin (talk | contribs)
Jump to navigation Jump to search

Role

Improvement Triggers - Conditions of Satisfaction

For OSE to achieve intrinsically-motivated, rapid development velocity that exceeds any found in extrinsically motivated work (see OSE Theory of Responsibility) - a part of the path to get there involves efficiency and rapid learning (personal and organizational) that allows contributors to feel that their time is well spent on achieving tangible results. To this end, we need to define specific performance requirements to be able to measure progress - and to enact corrective measures on an ongoing basis - until desired results are met. Thus, here are various check points that the Project Manager must manage at all times - for the Project Management to be effective. If these conditions are being missed on a regular basis, then the Development Process must be changed strategically until the normal operation of OSE does end up meeting these checkpoints effortlessly. If these checkpoints are not being met, an efficient process is not occurring. To address any gaps - the process may have to be refined so that structurally, the default action meets the condition of satisfaction. For example, to address the issue of individuals not uploading their work immediately, an online platform may be the OSE standard, where work in the cloud means that the document is available to the rest of the team by default.

  • Are updated CAD files being uploaded as soon as they are available, or is the individual producing them need to be reminded continuously?
  • Does the contributor's log show the work done?
  • Is there a way to know automatically (without asking) what work has been done?


Before 2015