Project Overview: AI/Quality Sentinel (AI/QS)
1. The Problem
Lack of quality in software projects is often not a technical failure, but a context failure.
- Understanding Gaps: Vague requirements in Jira generate code that doesn’t meet business needs.
- Lack of Consistency: Tight deadlines lead to neglect of best practices.
- Review Overload: Human reviewers (Tech Leads/Seniors) spend time on syntax and forget to validate if the ticket’s business rule was actually fulfilled.
2. The Solution
AI/Quality Sentinel is an intelligent governance agent that acts as a bridge between management (Jira) and execution (GitHub/GitLab). It analyzes the “quality triangle”:
- Intention: What the ticket says.
- Execution: What the code does.
- Pattern: What Thoughtworks best practices require.
3. Main Objectives
- Reduce rework by 30% by identifying misalignments before merge.
- Improve backlog health through quality analysis of user stories.
- Transform the developer into a “Strategic Reviewer,” delegating detailed pattern analysis to AI.
4. AI/works™ Differentiator
The solution uses TW’s secure infrastructure to ensure that sensitive customer data and proprietary code are processed under rigorous privacy standards.
5. Hackathon Team Model (up to 3 people)
- Person 1: Product and prioritization (PO + SM)
- Person 2: Generalist development focused on core implementation and integrations
- Person 3: Generalist development focused on core implementation and practical QA
For the full role contribution map and detailed responsibilities, see:
Execution Priority for Hackathon
- Prioritize business rules, integrations, and end-to-end evidence of value.
- Keep the interface minimal in the first iteration (API/CLI is acceptable for demo validation).
- Evolve interface polish only if there is remaining time.
👥 Team Roles
Learn about the team structure and how different professionals can help:
Documentation
Languages