In a past presentation, I presented my perspective on why IT project management is different from project management for some other industries. Project management is about managing with best practice processes, (see September newsletter article and the book), tailored to the particular program or project. A project manager is not only responsible for project initiation, planning, execution, control, reporting, and close out but for the development, configuration management, and quality assurance processes.
In IT the major focus is the development and implementation of systems or products (e.g., Networks/infrastructures, software and application systems, e-business and web sites) for their functional purpose: Processing and transmitting data and information 24/7 or triggered by events, including storage and retrieval. As we know, each project is different and each has it risks, challenges, and lessons learned. Although projects have many common activities/processes (as detailed in such documents as the Project Management Institutes’ Project Management Body of Knowledge (PMBOK), IT project management is not managing a project for design and construction of a bridge, highway, or house. Structures developed and constructed to with stand the elements. Many of these structures may have systems as part of them or used in their operation (e.g., operation of a bridge or manufacturing process). Every project is different and when you speak of IT and systems development projects in particular, developing systems that function depends on the interaction, integration, and interdependency of its elements (subsystems, components, modules or units) to accomplish its function(s) and purpose. You have to manage with a focus on system functions and just as important, where the system resides and operates (computer and hardware environments, etc.).
Project management requires individuals and teams to focus on the solution, configuration management to build in quality, and quality assurance to verify and validate/test (certify total compliance). The focus during development is to understand and know that you are managing the development of systems that may have to function 24/7 or by continuous events or activities. This is why requirements are specified (identified, defined, and documented) up front, essential for any project, detailing all the requirements for function/capability and performance, design, non-function qualities, materials, facilities, manufacture, etc. Documented “Quality” that you manage to the “end” of the project. IT Project Management is no less or more important than project management in any other industry, just understand and know what you are developing and implementing to have the proper management focus.
Leave a Reply
You must be logged in to post a comment.