Do You Think That Someone Could Be A Good Systems Manager?

21 Do You Think That Someone Could Be A Good Systems Manager But A Po

2–1 Do you think that someone could be a good systems manager but a poor project manager? What about the reverse situation? State any assumptions that you may have to make.

2–2 For each of the following projects, state whether we are discussing an open, closed, or extended system: A high-technology project, New product R&D, An online computer system for a bank, Construction of a chemical plant, Developing an in-house cost accounting reporting system.

Paper For Above instruction

The distinction between systems management and project management reflects different skill sets, focus areas, and functional responsibilities. While these two roles overlap in managing complex activities, it is entirely possible for an individual to excel in one area and be less competent in the other. This essay explores whether a person could be a good systems manager but a poor project manager, and vice versa, and discusses the classification of several projects as open, closed, or extended systems.

Possibility of being a good systems manager but a poor project manager

A systems manager typically oversees the overall operation, integration, and maintenance of complex information systems within an organization. They need to possess strong technical expertise, strategic thinking, and the ability to coordinate among different technical teams and departments. A competent systems manager ensures systems are reliable, scalable, and aligned with organizational goals. However, being a good systems manager does not inherently imply proficiency in managing specific projects with defined deliverables, budgets, and timelines.

Therefore, someone could be excellent in ensuring ongoing system health, troubleshooting, and aligning systems with strategic objectives but lack the skills necessary for traditional project management. For example, they may struggle with planning timelines, managing scope creep, or handling stakeholder expectations—skills crucial for project management. Such a person might excel in continuous operational roles, but if assigned as a project manager without adequate training or experience, they may fall short of delivering specific project outcomes effectively.

Possibility of being a good project manager but a poor systems manager

Conversely, a project manager is primarily focused on achieving specific project goals within constraints such as scope, schedule, and budget. Successful project managers possess strong organizational, communication, and leadership skills. They are adept at planning, risk management, and coordinating diverse teams towards common objectives. However, this role does not necessarily require deep technical expertise in system architecture or ongoing system maintenance.

Someone could be highly effective in managing a project’s phases—initiating, planning, executing, monitoring, and closing—and ensuring timely delivery but lack the broader vision or technical insight needed for sustained systems operations. After project completion, they might find it challenging to maintain or troubleshoot the system effectively, leading to potential operational issues. Their strengths in project execution do not automatically translate into long-term systems management capabilities, which require different skill sets such as continuous improvement and technical upkeep.

Assumptions and considerations

These assessments assume that individuals are evaluated based on their core competencies relevant to each role and that their skill sets are not confined solely to technical knowledge or managerial capabilities. It also presumes that organizational support, training, and experience influence their effectiveness in these roles. Furthermore, it is assumed that organizational structure and project scope can influence whether a person’s skill set aligns more with systems management or project management.

Classifying projects as open, closed, or extended systems

The classification of projects into open, closed, or extended systems depends on the boundaries and interactions with external environments.

High-technology project

This typically involves cutting-edge research and development, often requiring interaction with external technological advancements, suppliers, and research entities. Thus, a high-technology project is generally an extended system due to its interactions beyond organizational boundaries.

New product R&D

Research and development projects usually deal with uncertain outcomes, external collaborations, and adaptive processes. They are often considered open systems because they exchange information, knowledge, and resources with external entities, such as research institutions and industry partners.

Online computer system for a bank

This project involves designing and implementing a system that integrates with external banking networks and customer interfaces. The system must adapt to external regulatory requirements and technological changes, making it an extended or open system, depending on the scope of external interactions.

Construction of a chemical plant

This is largely a closed system once the project is underway, as its primary boundaries are within the organizational and physical limits of the construction zone. External interactions are mainly related to supply chains and regulatory bodies, but the core project is self-contained, indicating a closed system.

Developing an in-house cost accounting reporting system

This project is typically an open system because it continuously interacts with various organizational units, external accounting standards, and possibly external auditors. Its purpose is to adapt and integrate with ongoing internal processes and external compliance requirements.

Conclusion

Understanding the distinctions between systems management and project management, as well as classifying projects as open, closed, or extended systems, is essential for effective organizational planning and execution. Recognizing individual strengths and project boundaries ensures better alignment of roles, resources, and expectations, ultimately leading to more successful outcomes.

References

• Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. John Wiley & Sons.
• Schwalbe, K. (2018). Information Technology Project Management (9th ed.). Cengage Learning.
• Larson, E., & Gray, C. (2020). Project Management: The Managerial Process. McGraw-Hill Education.
• Wysocki, R. K. (2014). Effective Project Management: Traditional, Agile, Extreme. John Wiley & Sons.
• PMBOK® Guide (6th edition). (2017). Project Management Institute.
• Ulrich, D., & Barney, J. B. (1984). Perspectives in Organization Design and Effectiveness. Administrative Science Quarterly, 29(4), 519-556.
• Davies, A., & Brady, T. (2000). Organizational Capability and Competitiveness. Strategic Management Journal, 21(1), 17-25.
• McConnell, S. (1996). Software Project Survival Guide. Microsoft Press.
• Snyder, C. S. (2019). Managing Complex Projects: A New Model. Routledge.
• Turner, J. R. (2014). Handbook of Project-Based Management. McGraw-Hill Education.