It Project Management and Systems Management

In a project, there are so many factors to consider like cost, time, quality product, etc. But, the top three ever-present factors in a project that need to be considered are Cost, Scope and Time. These three are also the constraints in Project Management.
In cost, a team usually ponders about the likely expenses to be incurred while building a product. In scope, a team tries to determine what the project is trying to accomplish. And, in time, a team has to finish the product with what time allotment given to them. These discussions are about Project Management, but what about managing the actual building of the system? There’s a different kind of approach used in an analytical way to handle problem-solving and management issues, and that is Systems Management. Sounds new right? But actually, it’s been used since the 50’s.
Systems Management is divided into three parts: (1) systems philosophy – views things as systems, (2) systems analysis – problem solving approach, and (3) systems management – address business, organizational and technical issues.
There are two major phases in a project. These are project feasibility and project acquisition. The former determines the concept and the initial development plans of a project. While the latter executes and implements the plans a team has created while also considering potential risks.
I had an experience before where in my team didn’t fully discuss the concept of the project we are trying to build. We suffered a lot because in a way we realized, in the middle of the building process, that the IT product we are trying to build is not feasible at all considering what resources, time, etc. my team has. Probably, if we have done a thorough study of the system we are trying to build, we probably detected as early as Project Feasibility stage that the system is not feasible at all.
Systems Development Life Cycle (SDLC) is one very useful method or guide in systems management. Developers use it to help them as they go along in building a system/IT product. SDLC is a useful tool because it describes the phases involved in developing systems. The most popular phases (common in many Life Cycle models) are: planning, analysis, design, implementation and maintenance. Samples of SDLC models are: waterfall, spiral, incremental release, RAD, and prototyping. Using SDLC is important because there is a smooth transition from one phase to another, there is a smooth execution of plans, there is a detailed description and set of activities for every stage, and it serves as guide. Thus, eliminating “groping in the dark” and confusion about what to do next.
P. Lobrin
plobrin@gmail.com