aiwg
Version:
Cognitive architecture for AI-augmented software development with structured memory, ensemble validation, and closed-loop correction. FAIR-aligned artifacts, 84% cost reduction via human-in-the-loop, standards adopted by 100+ organizations.
91 lines (51 loc) • 2.18 kB
Markdown
Development-Organization Assessment Template
# Cover Page
- ``Project Name``
- `Development-Organization Assessment`
- `Version`1.0``
# Revision History
| Date | Version | Description | Author |
| --- | --- | --- | --- |
| ``dd/mmm/yy``|``x.x``|`<details>`|`<name>` |
# Ownership & Collaboration
- Document Owner: Environment Engineer
- Contributor Roles: Project Manager, Configuration Manager
- Automation Inputs: Process assessment interviews, tooling audit, capability metrics
- Automation Outputs: `development-organization-assessment.md` covering sections 1–6
# 1 Introduction
Outline purpose, scope, terminology, references, and structure of the assessment.
## 1.1 Purpose
## 1.2 Scope
## 1.3 Definitions, Acronyms, and Abbreviations
## 1.4 References
## 1.5 Overview
# 2 Business Context
Summarize the market and domain in which the development organization operates.
# 3 External Factors
## 3.1 Customers
## 3.2 Competitors
## 3.3 Other Stakeholders
Capture expectations, pressures, and relationships influencing development.
# 4 Internal Factors
## 4.1 Development Process
## 4.2 Supporting Tools
## 4.3 Internal Organization
## 4.4 Competencies, Skills, and Attitudes
## 4.5 Capacity for Change
Assess internal capabilities, tooling, structure, and readiness for transformation.
# 5 Product Characteristics
## 5.1 Size of Software-Development Effort
## 5.2 Degree of Novelty
## 5.3 Type of Application
## 5.4 Technical Complexity
Describe product traits that influence process tailoring and resource needs.
# 6 Assessment Conclusion
Highlight major problem areas and improvement opportunities discovered.
# Appendices (Optional)
Include detailed surveys, metrics, or interview summaries supporting the assessment.
# Agent Notes
- Capture toolchain gaps to inform the Development Case tailoring decisions.
- Summarize recommended improvement actions with accountable roles.
- Verify the Automation Outputs entry is satisfied before signaling completion.
- Record strengths and gaps to inform process tailoring decisions.
- Summarize improvement actions with owners and target dates.