Incrementality of IT Products: Waterfall vs Agile

# Incrementality and Technological Sophistication in IT Product Development: Key Concepts and Techniques

Incrementality allows for gradually expanding software functionality by adding new data, commands, or fixing bugs in stages. This is implemented through decomposition into user stories, simplifying deliveries to stakeholders. Take Cyberpunk 2077: since 2020, CD Projekt RED has released updates, including patch 1.6 with content from the Edgerunners series. Unlike traditional projects (construction, education) with fixed sequences, IT products enable parallel development of components.

High technological sophistication demands strict competencies: programmers need at least professional-level skills, testers and DBAs require mid-level specialized education, UI/UX designers need up to a year of training, and PMs need a bachelor's degree. Remote development cuts office costs, taps into a global talent pool, and pays based on actual work.

Waterfall Model: Strengths and Weaknesses

Developed by W. Royce in 1970 as a sequential flow of phases: analysis, design, implementation, testing, deployment. Each phase completes before the next begins.

Strengths:

• Clear phase boundaries with fixed dates for contracts.
• Firm fixed price, boosting client loyalty.
• Comprehensive documentation for team alignment.
• Easy onboarding of new members via phase artifacts.

Weaknesses:

• Hard to change requirements after approval.
• Long cycles that heighten risks (legal changes, business shifts, key staff departures).
• Schedule overruns: 89% on average per CHAOS Manifesto.

The model fits projects with fixed requirements and rigorous documentation.

Agile Model: Principles and Practices

Formulated in 2001 by a group of authors (K. Beck et al.). Leverages incrementality for iterative deliveries. Agile is not a methodology but a set of principles and practices.

Key Principles:

• Frequent deliveries of working software to refine requirements and achieve quick ROI.
• Openness to changes at any stage.
• Flexible processes that adapt to new tasks.
• Systematic delivery of functional products to minimize risks (bugs, mismatches).
• Stakeholder involvement through open communication.
• Team self-organization: sprint planning, user story decomposition (e.g., notifications on credit application status).
• Preference for face-to-face conversation.
• Progress measured by working code.
• Continuous team learning.
• KISS—keep it simple and transparent code.

Agile reduces requirement conflicts by focusing on user value.

IT Product Development Techniques

Uncertainty in requirements, intellectual labor, and limited resources spurred techniques like XP, RUP, AUP, RAD, DSDM, and Scrum.

| Technique | Description |

|----------|-------------|

| XP (Extreme Programming) | Extreme practices: pair programming, TDD, frequent releases to boost code quality. |

| RUP (Rational Unified Process) | Iterative-incremental process with phases: inception, elaboration, construction, transition. |

| AUP (Agile Unified Process) | Simplified RUP emphasizing simplicity. |

| RAD (Rapid Application Development) | Rapid prototyping for quick feedback. |

| DSDM (Dynamic Systems Development Method) | Focus on time and resources with MoSCoW prioritization. |

| Scrum | Framework with sprints, dailies, retrospectives for self-organizing teams. |

Technique selection depends on context: XP for small teams, Scrum for mid-sized projects with clear iterations.

IT Project Lifecycle Models

The lifecycle (LC) defines phase sequences. Main models:

• Waterfall: Linear, for predictable tasks.
• V-model: Waterfall extension with parallel testing.
• Incremental: Parallel streams with partial deliveries.
• Iterative: Repeating improvement cycles.
• Spiral: Risk-focused with prototypes.
• Agile-based: Sprints in Scrum/Kanban.

Hybrid models combine approaches (e.g., Water-Scrum-Fall).

Key Points

• Incrementality forms the basis for user story decomposition and iterative deliveries, setting IT apart from traditional projects.
• Technological sophistication requires skilled specialists and enables remote development.
• Waterfall provides documentation and fixed pricing but is vulnerable to changes.
• Agile emphasizes flexibility, frequent releases, and self-organization for rapid feedback response.
• Techniques (XP, Scrum) complement concepts, minimizing uncertainty risks.

— Editorial Team