Project dependency
A project dependency describes how a task or decision is tied to other results, dates or resources.
Make prerequisites and bottlenecks visible
A project dependency connects work, decisions or required resources. In a fictional example, the team can only make its final assessment of an interface test once the business field definition is approved. The test therefore has a content-related prerequisite.
A shared staffing bottleneck is a different type of constraint: independent tasks still cannot be performed simultaneously by the same fully occupied person. Both can affect planning. Record the required result or resource, responsible role, expected timing and consequence of delay. An arrow in a plan does not establish that the prerequisite has actually been met. Check its status before the dependent step.
Sources
Related terms
- Decision briefA decision brief prepares a specific choice by presenting options, rationale, consequences and unresolved assumptions.
- Software dependencyA software dependency is another software component a program needs. Indirectly introduced packages can also affect operation.
- Exit strategyA prepared route to switch, take over or retire an IT service in an orderly way.
- Migration costsEffort and expenditure for the planned move of data or functions to another environment.
- Investment costsCosts of building a new or expanded IT capability, as considered in project planning.
- Operating costsExpenditure to plan for the ongoing operation of an IT solution.
Articles on this topic
IT Consulting & Strategy with ASES
Strategy, architecture and technology choice