Feature Dependencies

Overview

Feature dependencies define the order in which features can be implemented within Agiloop IMPLEMENT.

Dependencies may exist for:

• Technical requirements
• Shared infrastructure or services
• Data model sequencing
• Authentication or platform prerequisites
• Preferred business rollout order
• Team workflow planning

A feature can have:

• No dependencies
• A single dependency
• Multiple dependencies

Agiloop allows dependencies to be reviewed and modified at any time.

How Dependencies Work

Agiloop IMPLEMENT enforces dependency rules during the implementation workflow.

A feature cannot be moved to the Ready status until all of its required dependency features have been completed and are in the Done status.

This helps ensure:

• Features are implemented in the correct order
• Required infrastructure exists before dependent work begins
• Generated code has the necessary supporting components available
• Implementation workflows remain stable and predictable

Dependencies Generated by INVENT

Agiloop INVENT automatically establishes feature dependencies during the specification and planning process.

These dependencies are typically created for technical reasons, such as:

• Backend APIs required before frontend features
• Authentication systems required before protected functionality
• Shared services needed by multiple features
• Database schema dependencies
• Messaging, caching, or infrastructure prerequisites

While dependencies can be modified manually, care should be taken before removing or changing INVENT-generated dependencies. Doing so without understanding the original reasoning may lead to implementation failures, missing functionality, or incomplete generated code.

How to Modify Feature Dependencies

Step 1: Open the Feature

Navigate to the INVENT tab and select the feature you want to modify.

Step 2: Open Work Breakdown

Within the selected feature, navigate to the Work Breakdown view.

Step 3: Select Dependencies

Locate and select the Dependencies label or section.

Agiloop will present a list of available feature IDs.

Step 4: Select Required Dependencies

Choose all features that must be completed before the current feature can move into the Ready state.

Changes are applied automatically.

Best Practices

• Avoid removing INVENT-generated dependencies unless you fully understand their purpose
• Keep dependency chains as simple as possible
• Use dependencies to enforce architectural sequencing, not task management
• Review dependencies before starting implementation cycles
• Ensure shared platform and infrastructure features are completed early