Software Engineering Management
Metadata
- Practice ID: TECH-SE-01
- Status: Draft
- Version: 2.0
- Owner Role: Engineering Lead
- Guild: GL04 Technology Guild
Purpose and Objectives
This practice defines how Calab.ai manages software engineering capability, code quality, testing standards, and technical knowledge development across all engineering teams. It ensures engineers at all levels demonstrate appropriate coding proficiency, testing discipline, knowledge depth, and continuous learning aligned to their seniority.
Scope
In Scope
- Software development standards and best practices
- Code quality and review processes
- Unit testing and integration testing standards
- Object-oriented programming and design pattern competency
- Technical knowledge development and certification
- Peer mentoring and knowledge sharing for development skills
- Coding standards and documentation requirements
Out of Scope
- Solution design and architecture (owned by Solution Engineering Management)
- Platform and infrastructure architecture (owned by Platform Architecture Management)
- Release coordination and deployment (covered by release processes)
- Project delivery management (owned by Project Management)
- Product roadmap and feature prioritisation (owned by Product Management)
Interfaces
Dependencies (Practices We Depend On)
- Solution Engineering Management - Design documents inform development
- Platform Architecture Management - Platform constraints guide implementation
- Project Management - Project timelines and resource allocation
Dependents (Practices That Depend On Us)
- Solution Engineering Management - Implementation feedback informs design
- Project Management - Development estimates inform project planning
- HR Management - Evaluation criteria for software engineering competencies
Related Practices and Resources
Related Practices
- Solution Engineering Management - Design-to-code alignment
- Platform Architecture Management - Technology platform guidance
- Project Management - Development sprint management
Key Processes
- Code Review Process
- Testing Standards Process
- Technical Knowledge Assessment Process
- Certification Tracking Process
Key Templates
- Code Review Checklist Template
- Test Plan Template
- Technical Assessment Template
KPIs and Success Signals
- KPI 1: Code review coverage (Target: 100%)
- KPI 2: Unit test coverage (Target: >=80%)
- KPI 3: Certification attainment rate (Target: per role level requirements)
- KPI 4: Technical debt ratio (Target: ⇐10%)
- Success Signal 1: Consistent code quality across all projects
- Success Signal 2: Engineers demonstrate progressive skill development
Review Cadence
- Practice Review: Quarterly
- Artefact Review: Bi-annually
- Owner: Engineering Lead
Change Log
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | 2026-02-11 | Build Agent | Initial creation (incorrect Release Management content) |
| 1.1 | 2026-02-13 | Build Agent | Consolidated from README into Overview |
| 2.0 | 2026-02-16 | Build Agent | Corrected content from Release Management to Software Engineering Management (Plan 07) |