Team Lead, Managerial & Agile Interview
What it is & where it is used
Managerial / techno-managerial rounds (often with a delivery manager, engineering manager, director or client) test whether you can deliver through a team — not just code. For senior developer, tech lead, team lead, project lead and engineering manager roles, expect questions on:
- Delivery: planning, estimation, sprint management, risk, deadlines, scope changes.
- People: delegation, mentoring, motivation, feedback, underperformers, conflict, hiring.
- Stakeholders: clients, product owners, escalations, saying no, status reporting.
- Technical leadership: architecture decisions, code quality, technical debt, production incidents.
- Process: Agile/Scrum/Kanban, SDLC, DevOps metrics, documentation.
| Role | Main focus |
|---|---|
| Senior developer | Complex features, quality, reviews, guiding juniors |
| Tech lead | Technical direction, design, code quality, unblocking the team; still codes a lot |
| Team lead (common in Indian IT services) | Tech + people + delivery for a small team; client interaction; task allocation |
| Engineering manager | People (hiring, growth, performance), process, delivery, cross-team collaboration; less coding |
| Project / delivery manager | Scope, schedule, budget, risks, client relationship, reporting |
| Architect | System-wide design, standards, technology choices, non-functional requirements |
Versions & history
Management and delivery methods have evolved:
| Year | Milestone |
|---|---|
| 1970 | Winston Royce's paper (commonly cited as the origin of the "Waterfall" model, though it argued for iteration) |
| 1986 | Takeuchi & Nonaka's "The New New Product Development Game" — inspiration for Scrum |
| 1995 | Scrum presented by Ken Schwaber and Jeff Sutherland |
| 1996–1999 | Extreme Programming (Kent Beck) |
| 2001 | Agile Manifesto (4 values, 12 principles) |
| 2004–2010 | Kanban for software (David J. Anderson); first Scrum Guide (2010) |
| 2009 | "DevOps" term (Patrick Debois' DevOpsDays) |
| 2011 | SAFe (Scaled Agile Framework) 1.0 |
| 2014–2018 | DORA research; Accelerate book (2018) |
| 2020 | Current Scrum Guide revision (Product Goal, one Scrum Team, "Developers") |
| 2020s | Remote/hybrid teams, platform engineering, SPACE framework for developer productivity, AI-assisted development |
Lifecycle
SDLC (Software Development Life Cycle) phases: Requirements → Analysis → Design → Implementation → Testing → Deployment → Maintenance. Models: Waterfall (sequential), V-Model (testing paired with each phase), Iterative/Incremental, Spiral (risk-driven), Agile (Scrum, Kanban, XP), DevOps (continuous delivery and operations).
Scrum lifecycle (per sprint, 1–4 weeks, commonly 2):
- Product Backlog (owned by the Product Owner, ordered by value) with refinement sessions.
- Sprint Planning — why (Sprint Goal), what (selected backlog items), how (plan/tasks) → Sprint Backlog.
- Daily Scrum — 15 minutes for Developers to inspect progress toward the Sprint Goal and adapt.
- Development work; Definition of Done applied to every increment.
- Sprint Review — demo the increment to stakeholders, adapt the backlog.
- Sprint Retrospective — improve how the team works.
- Repeat.
Scrum roles (accountabilities): Product Owner, Scrum Master, Developers. Artifacts: Product Backlog (commitment: Product Goal), Sprint Backlog (Sprint Goal), Increment (Definition of Done).
Team development lifecycle (Tuckman): Forming → Storming → Norming → Performing (→ Adjourning). A lead adapts style: directive early, coaching during storming, supportive/delegating when performing.
Incident lifecycle: detect → triage/assess severity → communicate → mitigate/restore → resolve root cause → blameless post-mortem → follow-up actions.
Tools used to develop
| Area | Tools |
|---|---|
| Work tracking | Jira, Azure Boards, Linear, GitHub Projects, Trello |
| Documentation | Confluence, Notion, SharePoint, Azure DevOps Wiki, architecture decision records (ADRs) |
| Communication | Microsoft Teams, Slack, Zoom, Outlook |
| Planning & estimation | Planning poker (story points), roadmaps, Gantt (MS Project) for fixed-scope work |
| Metrics | DORA metrics, velocity, cycle time, burndown/burnup, cumulative flow diagrams |
| Quality | SonarQube, code review policies, test coverage, defect tracking |
| Incident management | PagerDuty, Opsgenie, Azure Monitor alerts, status pages |
| People | 1:1 notes, OKRs/goals tools, performance review systems (Workday, SuccessFactors) |
| Diagrams | draw.io, Lucidchart, Excalidraw, C4 model |