Project Management and Client Delivery Standard

Organization: Igzibo Engineering Solutions, Inc.
Version: 1.0
Status: Living policy
Effective Date: September 16, 2026
Owner: Igzibo Engineering Solutions, Inc.
Review Cycle: At least annually and after material changes to applicable law, client requirements, technology, or business operations.

1. Purpose

Establishes baseline requirements for planning, managing, delivering, and closing technical projects.

2. Scope

Employees, contractors, consultants, project managers, technical leads, engineers, developers, R&D personnel, and third parties performing project work.

Definitions

Client: An organization receiving recruiting, staffing, project-management, engineering, R&D, or technology services from Igzibo. Deliverable: A work product, service output, report, software component, document, analysis, or other engagement output. Igzibo: Igzibo Engineering Solutions, Inc. RACI (Responsible, Accountable, Consulted, Informed): A role-assignment model used to clarify project responsibilities. SOW (Statement of Work): A contractual document defining services, deliverables, responsibilities, assumptions, and engagement terms.

3. Core Principles

Projects require clear scope, responsibilities, requirements, risk management, accurate status reporting, controlled changes, client-information protection, traceable decisions, quality review, and contract-aware delivery.

4. Initiation and Planning

Before substantive work begins, establish the applicable contract or SOW, objectives, scope and exclusions, deliverables, milestones, dependencies, assumptions, constraints, security/privacy requirements, intellectual-property terms, and acceptance criteria.

5. Requirements and Change Control

Document material requirements and resolve ambiguity. Material scope, cost, schedule, deliverable, or assumption changes require appropriate approval and documentation.

6. Roles, Status, Risks, and Issues

Assign project and technical responsibility. Status reports must accurately describe completed work, risks, issues, dependencies, and decisions. Material risks should have owners and mitigation.

7. Quality and Client Communications

Deliverables must satisfy applicable acceptance criteria. Client communications must be accurate and within authorized roles. Material delivery, security, privacy, contract, scope, quality, or legal risks must be escalated.

8. Client Data, IP, and AI

Handle client information under applicable classification, privacy, security, and contractual requirements. Do not reuse client materials across engagements without authorization. AI-assisted work must follow the AI and Generative AI Usage Standard.

9. Closure

Project closure should address acceptance, outstanding issues, documentation, knowledge transfer, access removal, data return or disposal, intellectual-property records, final contractual matters, and lessons learned where appropriate.

10. Exceptions and Enforcement

Exceptions require documented authorization. Violations may result in corrective action, project removal, contractual remedies, or termination.

11. References and Research Basis

• NIST, Cybersecurity Framework (CSF) 2.0.

CSF 2.0 provides high-level cybersecurity risk-management outcomes and does not prescribe a single project-management methodology.

Version History