Home / Roles & Responsibilities
Organization Structure
Shared / Leadership Layer
Business Stakeholders
Product Owner
Functional Lead
Technical Architect
Design Team (UI/UX)
↓
Scrum Teams
Each team: Technical Lead (Scrum Master) + Backend Devs + Frontend Devs + QA Engineer + Project Coordinator
↔
Customer Success Team
Direct client relationship, first point of contact for issues
Team Composition
Shared Roles (Across All Teams)
| Role |
Count |
Scope |
| Business Stakeholders |
Multiple |
Provide requirements, validate priorities, accept deliverables |
| Product Owner |
1 |
Backlog management, PRD ownership, story acceptance |
| Functional Lead |
1 |
Cross-team oversight, stakeholder management, go/no-go decisions |
| Technical Architect |
1 |
Architecture decisions, technical standards, cross-team technical alignment |
| Design Team (UI/UX) |
1-3 |
User research, wireframes, mockups, design handoff |
Scrum Team Composition (Per Team)
| Role |
Count |
Responsibilities |
Technical Lead
(also Scrum Master) |
1 |
Technical decisions, code review, facilitates all ceremonies, removes blockers, protects sprint |
| Backend Developers |
2-4 |
API development, database, integrations, backend testing |
| Frontend Developers |
1-3 |
UI implementation, UX integration, responsive design, frontend testing |
| Quality Engineer |
1 |
Test planning, execution, regression testing, quality advocacy |
| Project Coordinator |
1 |
Sprint tracking, meeting coordination, status reporting, documentation |
Customer Success Team
| Role |
Count |
Responsibilities |
| Client Success Manager (CSM) |
Multiple |
Key account relationships, first point of contact for client issues, raises issues to #sequifi_support |
Team Size: A typical scrum team has 5-9 members (Technical Lead + 2-4 Backend + 1-3 Frontend + 1 QA + 1 PC).
Shared / Leadership Roles
Functional Lead
| Aspect | Details |
|---|
| Reports To | CEO / COO |
| Scope | All delivery teams (shared across all teams) |
| Key Responsibilities |
- Cross-team oversight and coordination
- Business alignment and stakeholder management
- Go/no-go decisions for releases
- Escalation point for all teams
- Resource allocation across teams
- PRD sign-off (required approver)
|
| Decision Authority | Release approval, escalation resolution, cross-team priorities |
Technical Architect
| Aspect | Details |
|---|
| Reports To | CTO |
| Scope | All technical decisions (shared across all teams) |
| Key Responsibilities |
- Architecture decisions and technical standards
- Cross-team technical dependencies and alignment
- Technical release approval
- Merge to main (triggers production deploy) - reviews and approves PRs from Developers
- RCA facilitation for P0 incidents
- Rollback decisions
- PRD sign-off (required approver)
- Mentoring Technical Leads across teams
|
| Decision Authority | Architecture, technical standards, merge to main (production deploy), technical go/no-go, rollback |
Product Owner
| Aspect | Details |
|---|
| Reports To | CEO / COO |
| Scope | Product backlog and requirements (shared across all teams) |
| Key Responsibilities |
- Backlog management and prioritization
- Stakeholder alignment
- Acceptance criteria definition
- PRD ownership and creation
- Sprint goal definition
- Story acceptance/rejection at Sprint Review
|
| Decision Authority | Backlog priority, acceptance criteria, feature approval |
Design Team (UI/UX)
| Aspect | Details |
|---|
| Scope | Design for all teams (shared resource) |
| Key Responsibilities |
- User research and journey mapping
- Wireframes and prototypes
- Visual design and component specifications
- Design handoff to development teams
- Works one sprint ahead of development
|
Scrum Team Roles
Technical Lead (also Scrum Master)
| Aspect | Details |
|---|
| Reports To | Functional Lead, Technical Architect |
| Scope | Single Scrum team |
| Key Responsibilities |
- Technical: Technical decisions and code quality for the team
- Technical: Code review and PR approvals within team
- Technical: Coordinate with Technical Architect on architecture decisions
- Scrum Master: Facilitate all Scrum ceremonies (Planning, Standup, Review, Retro)
- Scrum Master: Remove blockers for the team
- Scrum Master: Protect sprint from scope changes
- Scrum Master: Coach team on Agile practices
- Report progress to Functional Lead and Technical Architect
- Merge to staging for QA testing (shared with Developer)
- Bug severity classification (final decision)
|
| Decision Authority | Team-level technical decisions, sprint protection, blocker escalation, bug severity classification |
Combined Role: The Technical Lead in each team serves as both the technical authority and Scrum Master. This ensures technical decisions and process facilitation are aligned, and reduces coordination overhead.
Backend Developer
| Aspect | Details |
|---|
| Reports To | Technical Lead |
| Key Responsibilities |
- API development
- Database design and optimization
- Third-party integrations
- Backend testing (unit, integration)
- Code reviews
|
Frontend Developer
| Aspect | Details |
|---|
| Reports To | Technical Lead |
| Key Responsibilities |
- UI implementation from designs
- UX integration
- Frontend testing
- Responsive design implementation
- Code reviews
|
Project Coordinator
| Aspect | Details |
|---|
| Reports To | Technical Lead |
| Scope | Single Scrum team |
| Key Responsibilities |
- Sprint progress tracking and metrics
- Meeting coordination and scheduling
- Status reporting and dashboards
- Cross-team communication support
- Documentation and process maintenance
- Resource and timeline tracking
- First responder for support issues (Tier 1)
|
Customer Success Team
The Customer Success Team works directly with customers and serves as the bridge between clients and the development organization.
Client Success Manager (CSM)
| Aspect | Details |
|---|
| Key Responsibilities |
- Key account relationships - primary contact for clients
- First point of contact for client issues
- Raises issues to #sequifi_support Slack channel
- Incident communication to clients during P0/P1 events
- Feature adoption and client training
- Gathers client feedback for product improvements
|
Issue Flow: Client → CSM → #sequifi_support → Development Team. CSM keeps client informed throughout resolution.
Quality Assurance
Quality Engineer (per team)
| Aspect | Details |
|---|
| Reports To | Technical Lead |
| Key Responsibilities |
- Test case creation and execution
- Bug documentation and tracking
- Regression testing
- Exploratory testing
- Quality advocacy within the team
- Release sign-off for team's features (can block releases)
- Bug severity input (with Technical Lead)
|
| Decision Authority | QA sign-off (veto power for team's features), test coverage |
RACI Matrix - Bug Fix Process
R = Responsible | A = Accountable | C = Consulted | I = Informed
| Activity |
TA |
TL |
Developer |
QA |
CSM |
PC |
| Client reports issue |
- |
- |
- |
- |
R |
I |
| Post to #sequifi_support |
I |
I |
- |
I |
R |
I |
| Bug triage & logging |
I |
I |
- |
I |
- |
R |
| Bug classification |
C |
A |
- |
C |
- |
R |
| Developer assignment |
I |
A/R |
I |
- |
- |
- |
| Fix development |
C |
C |
A/R |
- |
I |
I |
| Code review |
C |
A |
R |
- |
- |
- |
| QA testing |
- |
- |
- |
A/R |
- |
- |
| QA sign-off |
I |
I |
- |
A/R |
I |
I |
| Production deploy (merge) |
A/R |
C |
- |
C |
I |
I |
| Post-deploy monitor |
C |
C |
R |
R |
I |
R |
| Rollback decision |
A |
R |
- |
C |
I |
I |
Legend: TA = Technical Architect, TL = Technical Lead, QA = Quality Engineer, CSM = Client Success Manager, PC = Project Coordinator
RACI Matrix - Feature Development Process
R = Responsible | A = Accountable | C = Consulted | I = Informed
| Activity |
PO |
FL |
TA |
TL |
Dev |
UX |
QA |
PC |
| Backlog intake & prioritization |
A/R |
C |
C |
I |
- |
- |
- |
I |
| Stakeholder refinement |
A/R |
R |
C |
C |
- |
C |
- |
R |
| UX/UI design |
C |
I |
C |
C |
C |
A/R |
- |
I |
| PRD creation |
A/R |
C |
C |
C |
- |
C |
C |
R |
| Technical feasibility & estimation |
I |
I |
A |
R |
R |
- |
C |
- |
| Sprint planning |
C |
I |
C |
A/R |
R |
- |
R |
R |
| Development |
I |
- |
C |
A |
R |
- |
- |
I |
| Code review |
- |
- |
C |
A/R |
R |
- |
- |
- |
| QA testing (staging) |
- |
- |
- |
I |
C |
- |
A/R |
- |
| UAT coordination |
C |
R |
- |
I |
- |
- |
A |
R |
| Go/No-go decision |
C |
A |
C |
C |
- |
- |
R |
I |
| Production deploy |
I |
I |
A/R |
C |
R |
- |
C |
I |
| Release communication |
A |
I |
- |
I |
- |
- |
- |
R |
| Sprint review & demo |
A |
C |
I |
R |
R |
I |
I |
R |
| Retrospective |
I |
I |
I |
A/R |
R |
- |
R |
R |
Legend: PO = Product Owner, FL = Functional Lead, TA = Technical Architect, TL = Technical Lead, Dev = Developer, UX = Design Team, QA = Quality Engineer, PC = Project Coordinator