Six Key Parameters of an IT Project: From Triangle to Tetrahedron
In IT project management, the traditional triangle (time, scope, budget) is supplemented by a circle of quality, but this is still an oversimplification. In practice, six interrelated parameters are identified: time, scope, budget, quality, risks, and value. Their balance determines success, especially in developing unique software. Ignoring risks, quality, or value leads to missed deadlines and budget overruns.
Academic Justification of the Parameters
A project is defined as a temporary endeavor to create a unique product or result. From this definition, the basic parameters emerge:
- Scope — the amount of work required to achieve the result.
- Time — the timeframe for completion.
- Budget — the resources allocated for implementation.
The uniqueness of a project inevitably gives rise to additional parameters:
- Risks — the probability of deviations from the plan.
- Quality — compliance with requirements and expectations.
- Value — the usefulness of the result for stakeholders.
All six parameters are present in any project, even if not formalized. The secret to meeting deadlines and budget is explicitly defining quality, risks, and value from the start. Without this, when issues arise with scope or resources, quality and value are the first to suffer.
Preventing Failures:
- Formalize quality metrics with a user alignment matrix.
- Define value through sponsor expectations.
- Require contractors to provide a risk matrix based on similar projects.
Cultural Barriers in Management
In most companies, there is comfort in working with time, budget, and scope. Quality is often kept in reserve for maneuvering. Risks and value are ignored due to a lack of culture.
The question "Why this project?" causes discomfort if a company is not accustomed to discussing the value of any activity. Without such a culture, project value is sacrificed for the sake of deadlines: status meetings are conducted by rote, without verifying usefulness.
To maintain balance, all participants must understand the value. This requires a norm of asking "Why?" at any level—from developer tasks to company strategy.
Practical Case: Sacrifices of Unbalanced Parameters
In a real project, scope was estimated at 3,000 person-days, with a deadline of six months. A team of 22 people (plus 3 planned) was supposed to deliver 500 person-days per month. Reality: a new team does not immediately reach peak productivity.
Sequence of sacrifices:
- Risks increased due to resource shortages. Solution—hire beyond staff, adding secondary risks (low qualification of newcomers).
- Quality suffered: comprehensive testing was cut, half the features launched raw, expecting incidents.
- Value was lost: user-friendly features were dropped to avoid increasing scope.
Result—formal deadline met, but with compromises on all fronts.
Stalinist Approach: Prioritizing Value and Time
In a rigid hierarchy, value and time are determined by the customer (product owner). The project manager calculates the remaining parameters based on these priorities, requesting resources.
Advantages:
- Reduced risk of irrelevant results.
- Balance of six parameters through focus on value.
Disadvantages: over-insurance on resources and risks, potential inefficiency. But it is better to get a valuable result on time, even if slightly more expensive, than endless rework with degraded quality.
How to Achieve Balance in IT Projects
In agile and waterfall, ignoring risks and value leads to scope creep or technical debt. Recommendations for middle/senior PMs:
- At initiation: Create a matrix of all six parameters with metrics (e.g., MTTR for quality, ROI for value).
- During execution: Weekly tracking of deviations, with adjustments based on priorities.
- At closure: Audit—how well value was preserved vs. sacrifices.
| Parameter | Example Metric | Impact on Others |
|-----------|----------------|------------------|
| Time | Six months | Increases risks when compressed |
| Scope | 3,000 p/d | Correlates with budget |
| Budget | Fixed | Sacrifices quality |
| Quality | Test coverage | Secondary in quality |
| Risks | Matrix | Grows from resource shortages |
| Value | User feedback | Lost when features are cut |
Key Takeaways
- Six project parameters: time, scope, budget, quality, risks, value—form a tetrahedron with six faces.
- Ignoring risks, quality, and value leads to sacrifices under time/budget pressure.
- Formalization at the start (matrices, metrics) is key to balance.
- Corporate culture with the question "Why?" preserves value.
- Prioritizing value and time (as in the Stalinist approach) is more effective than chaotic rework.
— Editorial Team
No comments yet.