Dependency
A relationship where one team's (or person's) work cannot proceed until another delivers something (data, a component, a decision, their time); the hardest thing to manage on the way to scale, addressed by surfacing early, mapping visibly, and designing out with clear interfaces.
Defined in 3 GAGE programs, which carry 4 distinct definitions of it. The wording above is taught in Certified AI Transformation Professional (CATP).
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
A relationship where one team's (or person's) work cannot proceed until another delivers something (data, a component, a decision, their time); the hardest thing to manage on the way to scale, addressed by surfacing early, mapping visibly, and designing out with clear interfaces.
In a modular codebase, any external object, class, or resource that a module needs to perform its function. A dependency that is created internally couples the module to a specific implementation; a dependency that is injected allows the implementation to vary.
Something an objective needs that the organization does not control. Its six common failure modes are unavailable, late, wrong, withdrawn, repriced and changed without notice.
A thing a risk rests on, runs through, or requires in order not to happen: a system, a supplier, a site, a jurisdiction, a person, a customer segment, or a control.
Where it is taught
The exact lessons this term appears in. The first module of every program is free with a free account.
- Agile Transformation Management · Implementation from Pilot to Scale, Certified AI Transformation Professional (CATP)
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.