Participants interpret project delivery based on their knowledge and experience and approach it based on science, applied science, or art.

Science Practiced by Methodologists

Science

Science is methodical, precise and planned.

A Bachelor of Science in Information Technology, or equivalent, is awarded to students who complete undergraduate computing or computer studies coursework. This qualification confirms that IT is firmly based on science, emphasising that an enterprise IT project is, in essence, a scientific endeavour involving the construction and maintenance of complex hardware, software, and information systems.

In enterprise IT projects, science refers to systematic, precise, and planned approaches. Key practices include:

  • Identifying every task and mapping out dependencies to ensure efficiency and predictability.
  • Following industry standards and best practices to maintain quality and consistency.
  • Documenting everything throughout the project phases.
  • Completing tasks with a high degree of quality to avoid errors and rework.

This approach ensures controlled project progression, minimising risks and enhancing the overall quality of the final product. However, it also limits flexibility to adapt to unexpected changes, which can be a disadvantage in dynamic environments.

Inexperienced IT graduates often rely heavily on pure scientific principles and academic theories, lacking the practical insights needed for real-world applications.

Applied Science Employed by Pragmatists

Applied science is methodical, precise and planned—with acceptable tweaks.

An enterprise IT project is applied science. Unlike pure science, which thrives on experimentation in controlled environments, applied science tackles real-world applications that are unpredictable and specific to each project. In this context, there is one opportunity to deliver an IT project within a predetermined timeframe and budget. Every clock tick represents money spent, so maximised time and resource efficiencies determine project success.

In enterprise IT projects, applied science means being methodical, precise, and planned for —yet adaptable enough to make necessary modifications. This approach recognises that while the core principles of science guide the project, adjustments are inevitable due to the unpredictable nature of real-world situations.

The ideal project team comprises academically qualified participants with substantial experience in enterprise IT project delivery. These participants can blend rigorous scientific methods with creative problem-solving. This balanced approach, or creative science, highlights that a participant must thoroughly understand theories to know, with confidence, what their creativity will break.

Artistic Approaches by Improvisers

Art

Art is non-methodical, flexible and unplanned.

When IT enterprise projects are approached without adherence to scientific principles, they take on the characteristics of art rather than applied science. This situation arises when participants without formal project qualifications rely on trial-and-error methods instead of systematic planning and analysis, disregarding textbook theories in favour of creativity from internet searches and lessons from previous projects. This often leads to chaotic project execution.

In this scenario, the rigour of a Bachelor of Science in Software Engineering is transformed into a Bachelor of Arts in Software Cutting Corners, where documentation, planning, structure, and control are noticeably missing.

Enterprise IT projects treated as art are characterised by the following:

  • Lack of project direction.
  • Absence of a project schedule or reliance on a one-page project schedule.
  • Undefined and out-of-control project scope. Ambiguous deliverables.
  • Fluid roles and responsibilities.
  • Decision-making is based on anecdotal experience, personal preferences, and opinions.
  • Endless meetings discuss what they think needs to be done, with no one doing what needs to be done.

While creative practices can be beneficial, participants must operate within the boundaries of scientific methods and established standards. Participants who practice art produce unpredictable and unreliable results, disrupting project stability and compromising the quality and timeliness of deliverables.

Treating a large and complex enterprise IT initiative as an art project is
Disaster. Waiting. To. Happen.

Enterprise IT Projects Treated as Science, Applied Science, and Art

Table 4 compares aspects of enterprise IT projects—including schedule, scope, deliverables, and roles and responsibilities—illustrating different approaches to project delivery through the lenses of science, applied science, and art.

Table 3: A Comparative Analysis of Enterprise IT Projects Treated as Science, Applied Science, and Art
Aspect Pure Science Applied Science Art
Schedule Detailed tasks identified with strict adherence to timelines<./td> Detailed tasks identified with flexibility around the critical path<./td> High-level tasks are identified with a focus on flow without deadlines.
Scope A fixed scope is defined. A defined and prioritised scope. The scope is often not clearly defined.
Roles and responsibilities Clearly defined roles with specific expertise and accountability. Clearly defined roles with interdisciplinary collaboration and accountability. Fluid roles with participants assuming responsibilities without the necessary knowledge, leading to a lack of accountability.
Decision-making Methodical decisions are based on scientific evidence. Decisions are informed by scientific evidence and feasibility. Subjective choices based on previous project experiences and personal opinions.
Deliverables Project documents as prescribed by the delivery model. Project documents as prescribed by the delivery model with fit-for-purpose adjustments. Meeting notes and emails as project documents.
Final product Technically superior. Functional and meets user needs. Minimum functionality supplemented by workarounds.
Effectiveness Medium, due to inflexibility and potential for overlooking practical constraints. High, due to a balanced approach ensuring relevant project outcomes. Low, as the absence of structure can lead to disarray, making this approach unsustainable.