Project Management Michael L. Collard Department of Computer Science Kent State University

Management Spectrum People – recruiting, selection, performance management, training, compensation, career development, organization and work design, and team/culture development [CP-CMM] Product – establishment of objectives and scope, developer and customer interaction, alternatives Process – framework for a comprehensive plan Project – planning only way to handle complexity, still projects often fail

Project Management Understand the problem as well as possible as early in the process as possible Maintain momentum Track progress Make smart decisions

Organizing Principle [Boehm] Why is the system being developed? What will be done, by when? Who is responsible for a function? Where are they organizationally located? How will the job be done technically and managerially? How much of each resource is needed?

“Knowledge Management” Artifacts – source code, analysis and design models (e.g., UML), technical reports, test suites, etc. People – justifications, alternatives, problem areas, domain knowledge, social issues

People Senior Managers – define business issues Project/Technical Managers – plan, organize, control and motivate practitioners Practitioners – technical skills Customers – specify requirements End-Users – interact with the product

People Management Encourage idea contribution Increase communication Encourage being part of the process Encourage flexibility Encourage longevity Reward good solutions Allow for professional growth