How AI Agents Are Changing Engineering Sprints and Product Roles

Junaid Warwani · VP of Engineering · Brellium

Nov 2026AI Engineering Product Leadership

01 — The conversation

GuestJunaid WarwaniVP of EngineeringBrelliumProfile →

Junaid Warwani, VP of Engineering at Brellium, shares how he moved away from traditional sprints at his previous company after adopting AI development tools. He explains the shift to individual engineering ownership, changing product responsibilities, and faster feedback loops, along with what did not work and what he would do differently.

Key ideas

01Traditional sprint estimates become less useful when AI changes the time required for development tasks.

02One engineering owner per priority can accelerate delivery but creates knowledge sharing and continuity challenges.

03Product managers can devote more attention to future priorities while engineers assume greater delivery responsibility.

04Faster coding makes timely feedback from engineering, product, operations, and customers more important.

05Communication, code comprehension, clear writing, and change management are increasingly valuable skills.

At his previous company, Junaid moved a senior engineering team away from traditional two week sprints to weekly priorities with one engineer responsible for each. Product and operations colleagues could join as resources for rapid feedback. The approach increased parallel work and reduced the value of established planning rituals, but created fresh coordination problems.

Junaid discusses why product managers can focus more on what comes next while engineers take greater responsibility for current delivery. He also explains how faster AI generated work can shift the bottleneck from writing code to reviewing ideas, technical specifications, pull requests, and customer feedback.

The conversation covers what the team learned about knowledge sharing, coverage when a sole owner is unavailable, and the need for organizational change beyond engineering. Junaid describes hiring for customer communication, code understanding, and concise writing, and explains why engineering leaders need to become better at managing change.