Our company is changing its Software Development Lifecycle (SDLC). Curious to hear from others what theirs looks like overall + bottlenecks. Ours:
- 1 week planning/retro, 6 weeks implementation (basically six 1-week sprints).
- Standup now mainly demoing what Engineering/Design is working on, getting quick feedback from teammates.
- Meetings are recorded/transcribed. Agents generate Product Requirement + System Design docs from those meetings.
- Push to have non-engineers be able to commit code, but engineering still responsible for shipping it.
Unsolved issues/bottlenecks:
- Ephemeral test environments (per PR test environments) aren't 100% reliable yet.
- No longer doing capacity planning, but it feels like we need to go back to it.
- Code reviews. They're longer and there's more of them. Even more with non-engineers being able to @Cursor on Slack.
- Design used to have Figma as the source of truth; now that they're heavily leaning on Claude Design, we don't get the linkage of Figma components to code components. We might solve this by moving from Cursor to Claude Code.
- 1 week planning/retro, 6 weeks implementation (basically six 1-week sprints).
- Standup now mainly demoing what Engineering/Design is working on, getting quick feedback from teammates.
- Meetings are recorded/transcribed. Agents generate Product Requirement + System Design docs from those meetings.
- Push to have non-engineers be able to commit code, but engineering still responsible for shipping it.
Unsolved issues/bottlenecks:
- Ephemeral test environments (per PR test environments) aren't 100% reliable yet.
- No longer doing capacity planning, but it feels like we need to go back to it.
- Code reviews. They're longer and there's more of them. Even more with non-engineers being able to @Cursor on Slack.
- Design used to have Figma as the source of truth; now that they're heavily leaning on Claude Design, we don't get the linkage of Figma components to code components. We might solve this by moving from Cursor to Claude Code.