Team Structure
Organizational Hierarchy
The Kinana development team operates within Ibtikar Edu Tech Solutions with a focused, lean structure optimized for agile product development.
Management Structure
Executive Leadership
CEO - Ibtikar Edu Tech Solutions
- Strategic direction for company and product portfolio
- Final approval authority for major product decisions
- Resource allocation and budget approval
- Stakeholder and investor relations
Reports to: Board of Directors / Parent company (YHT)
Product Development Team
Product Manager (Kinana)
Reports to: CEO
Direct Reports:
- Design Team (UI/UX Designers)
- Software Team (Solution Architect, Senior Developer, QA/PM)
Key Responsibilities:
- Product vision and roadmap
- Feature prioritization
- Stakeholder management
- PRD development and approval coordination
- Budget and resource planning
- Go-to-market strategy (pre-launch)
Decision Authority:
- Feature scope and priority
- Sprint commitments
- Product requirements
- User experience direction
Design Team
Reports to: Product Manager
UI/UX Designers
Team Size: 1-2 designers
Responsibilities:
- User interface design for Kinana platform components
- User experience flows and wireframes
- Design system maintenance
- Usability testing and iteration
- Visual design for Shell, Library, Videos, Podcasts, Brokkly sub-apps
- Collaboration with frontend developers
Deliverables:
- Figma/design tool mockups
- Design specifications for development
- UI component libraries
- User journey maps
Collaboration:
- Works closely with Product Manager on feature requirements
- Coordinates with Software Team on implementation feasibility
- Participates in sprint planning and reviews
Software Team
Reports to: Product Manager
Solution Architect
Seniority: Technical leadership role
Responsibilities:
- Technical architecture and system design
- Technology stack decisions
- Code review approval (final authority)
- Infrastructure planning (Azure, Kubernetes)
- Security and performance oversight
- Technical debt management
- Vendor and licensed platform evaluation
Key Activities:
- Architecture documentation
- Technical guidance during development
- Production deployment approval
- Cross-component integration design
Decision Authority:
- Technical approach and patterns
- Infrastructure configuration
- Code merge approval
- Technology selection
Senior Developer
Seniority: Implementation lead
Responsibilities:
- Feature implementation (frontend and backend)
- Code review (peer level)
- Deployment execution to staging and production
- Technical mentorship
- Local environment and CI/CD pipeline maintenance
- Bug investigation and resolution
Key Activities:
- Daily development work
- Pull request creation and review
- Staging deployment coordination
- Technical documentation
Collaboration:
- Works directly with Solution Architect on complex features
- Coordinates with QA/PM on testing and deployment
- Supports designers with implementation guidance
QA / Project Manager
Dual Role: Quality Assurance + Agile Project Management
Responsibilities:
QA Functions:
- Testing strategy and execution
- Staging environment validation
- Bug reporting and tracking
- Regression testing
- User acceptance testing coordination
Project Management Functions:
- Sprint planning coordination
- GitHub Projects Kanban board management
- Daily standup facilitation
- Sprint review organization
- Retrospective facilitation
- Process documentation
Key Activities:
- Test case development and execution
- Sprint progress tracking
- Blocker identification and escalation
- Team coordination and communication
- Release coordination support
Decision Authority:
- Test acceptance criteria
- Sprint readiness
- QA sign-off for releases
Team Collaboration Model
Cross-Functional Coordination
Product → Design → Development workflow:
- Product Manager defines requirements (PRD)
- Designers create UI/UX specifications
- Solution Architect reviews technical feasibility
- Software Team implements
- QA/PM validates
- Product Manager accepts
Decision-Making Matrix
| Decision Type | Authority | Consultation Required |
|---|---|---|
| Product roadmap | Product Manager | CEO approval for major shifts |
| Feature priority | Product Manager | Software Team for effort |
| Technical approach | Solution Architect | Product Manager for business impact |
| Design direction | Product Manager + Designers | Software Team for feasibility |
| Sprint commitment | Full team consensus | - |
| Code merge | Solution Architect | Peer review completed |
| Production deployment | Solution Architect + Product Manager | QA sign-off required |
Team Evolution
Recent Changes
- Contractor Offboarding: 3 senior developers (1 frontend, 2 backend) transitioned off team
- Current Focus: Internal team ownership of codebase and processes
- Knowledge Transfer: Complete, team now self-sufficient
Future Growth (Post-Production)
Potential additions based on product traction:
- Additional developers for feature velocity
- Dedicated QA engineer (separate from PM role)
- DevOps engineer for production operations
- Support/success team as user base grows
Working Relationships
Internal Collaboration
- Daily: Software Team coordinates via standups
- Weekly: Product Manager syncs with CEO
- Bi-weekly: Full team sprint planning and reviews
- Ad-hoc: Design and development coordination as needed
External Stakeholders
Managed primarily by Product Manager:
- YHT EdTech Division leadership
- Education partners and pilot customers
- Vendors (ABP.io, Nutrient)
- Compliance and legal teams (IP governance)
Remote vs. On-Site
Work Model: Flexible (office-based with remote capability)
Office Requirements:
- Sprint planning: Preferred in-person
- Daily standups: Video call acceptable
- Code walkthroughs: Screen sharing via Teams
- AI workstation access: On-site (Ubuntu GPU workstation)
Communication Tools: Microsoft Teams primary, regardless of location
Last Updated: November 2025
Version: 1.0