Project and Portfolio Execution

Projects, planning, progress, blockers, risks, dependencies, delivery health, portfolio, and intervention priority. This package has its own data model, workflows and interface contributions. Its documentation applies wherever the package is installed, not only to one industry solution.

Overview

Package: BND-PROJECT · Type: Business capability · Documentation: 1.0

Marketplace listing · Technical reference

A health indicator summarizes detected evidence, not ERP accounting. Missing or stale evidence remains visible and is not interpreted as healthy delivery.

User guide

1. Compare project health with the relevant plan snapshot and inspect deviations supported by sources.
2. Review blockers, risks and cross-project dependencies with their owners and affected milestones.
3. Prioritize an intervention and follow its linked action; use Scope Alignment for contractual change and acceptance decisions.

Screens owned by this package

• Project Execution — Portfolio — SCR-PRJ-01.
• Project Execution — Projects — SCR-PRJ-02.
• Project Execution — Risks & Issues — SCR-PRJ-03.
• Project Execution — Dependencies — SCR-PRJ-04.

Contributions to other screens

• Overview — owned by BND-OVERVIEW; this package contributes analysis or interface content.
• Meeting — Findings — owned by BND-FINDINGS; this package contributes analysis or interface content.
• Meeting — Decisions & Actions — owned by BND-WORK; this package contributes analysis or interface content.
• Meeting — Context — owned by BND-EVIDENCE; this package contributes analysis or interface content.
• Findings — Watching — owned by BND-FINDINGS; this package contributes analysis or interface content.
• Commercial Intelligence — Accounts — owned by BND-COMMERCIAL; this package contributes analysis or interface content.
• Project Execution — Scope Changes — owned by BND-SCOPE; this package contributes analysis or interface content.
• Project Execution — Acceptances — owned by BND-SCOPE; this package contributes analysis or interface content.
• Relationship & Trust — Overview — owned by BND-RELATIONSHIP; this package contributes analysis or interface content.
• Relationship & Trust — Accounts — owned by BND-RELATIONSHIP; this package contributes analysis or interface content.
• Relationship & Trust — Corrective Actions — owned by BND-RELATIONSHIP; this package contributes analysis or interface content.
• Decisions & Commitments — owned by BND-WORK; this package contributes analysis or interface content.

Configuration

Configuration changes are versioned overlays. Preview the changed permissions, schemas, workflow bindings and interface contributions in Development; qualify them in Testing and Staging before authorized Production promotion. A business administrator configures permitted solution settings; platform deployment authority is separate.

Technical reference

The implementation reference identifies DM-PROJECT, WFP-PROJECT-DELIVERY, 2 owned agents, interface contributions, policies and evaluation profiles. Shared platform services execute these definitions; they do not hard-code this package's business meaning.

Compatibility and dependencies

• Sources, Integrations, and Evidence Foundation — BND-EVIDENCE.
• Finding Lifecycle, Evidence Assurance, and Review — BND-FINDINGS.
• Decisions, Commitments, Actions, and Follow-Up — BND-WORK.

Direct consumers: Scope, Contract, SOW, and Acceptance Alignment, Engineering, Architecture, and Cross-Object Impact.

Dependencies declare compatible ranges; the installation resolver records exact signed versions and digests in the environment lock. This documentation's version is not an installed-package version. Before updating or removing the package, inspect dependent workflows, records, interface slots and retained artifacts. Never delete referenced evidence or silently remove a required capability.

Extensions and enrichment

Add project-type health dimensions, dependency analyses and portfolio widgets without rewriting the baseline plan or scope package.

Extensions declare their own package identity, dependencies, provided capabilities and evaluation evidence. They preserve the publisher's original package and are qualified with the complete resolved composition. See the developer extension guide.

Versions and upgrades

The documentation describes the current 1.x solution composition and the package's declared capabilities. The exact installed package, model, prompt and schema versions are shown in the environment lock and run provenance; no historical release sequence is implied.

1. Compare release manifests, permission changes and migrations against the current lock.
2. Test package behavior and affected dependent workflows with representative, authorized evidence.
3. Promote the signed release after approval and record the resulting lock.
4. Roll back only when schema/data compatibility and retained artifacts permit it. Irreversible migrations require a tested recovery or forward-fix plan; completed external actions require compensation, not a software rollback.

Used in solutions

Technology Consulting & Delivery includes this package as default active. That activation rule belongs to this solution; it does not make every business capability mandatory for every Telynt deployment.