(Kotch, 2004) The level would be characterized by a lack of quality controls and clear managerial standards and objectives, with little supervision and employee 'check ins' in the form of meetings.
Level 2: Defined but inappropriately so Project management at this level would set goals, and have a set schedule, but the goal objectives often create chaos because they were inflexible or unobtainable in the entirety. There may be a clear leader, but there is no clear chain of command beneath the leader. Critically, there is an absence of standard operating procedures for management and ways of evaluating performance. Things may go well, occasionally, but as if by chance, and because of individual and sporadic employee competence or brilliance in ways that cannot carry over into regular working methods or other organizational departments.
Level 3: Acceptable
There is clear set of project manager procedures that are reliable. There are standard management practices and a chain of command, an overall set of project objectives, and a sense of responsibility for getting particular jobs done, even if some links in the chain of command might be lacking. Quality control measures exist, and are often met, as the goals are testable. Also, there is a commitment to developing checks for organizational leaders to monitor progress and development,...
Delphi Study: Influence of Environmental Sustainability Initiatives on Information Systems Table of Contents (first draft) Green IT Current Methods and Solutions Green IT and energy costs Green It and Email Systems Green IT and ICT Green IT and ESS Green IT and TPS Green IT and DSS Green IT and other support systems Green IT and GHG reduction Green IT and the Government Sector Green IT and the Corporate Sector Future Prospects of Green IT in the software industry The paper focuses on how the
Our semester plans gives you unlimited, unrestricted access to our entire library of resources —writing tools, guides, example essays, tutorials, class notes, and more.
Get Started Now