Project Management
Agile Practices
Scrum, Kanban, and Continuous Delivery
Scrum
- Sprint Planning: Before each Sprint, the team plans what to accomplish together
- Sprint Review: After the Sprint, demo completed work and gather feedback
- Sprint Retrospective: Review the Sprint's collaboration process and identify improvements
- Recommended Sprint cycle: 1-2 weeks, adjusted to the team's rhythm
Kanban
- Visualize the workflow with a board (To Do → In Progress → Review → Done)
- Set WIP (Work In Progress) limits to avoid multi-tasking that reduces efficiency
- Continuously optimize the process, reducing bottlenecks and wait times
- Best suited for maintenance projects or scenarios with frequently changing requirements
Continuous Delivery
- Deliver in small batches — keep each change as small as possible
- Iterate quickly to get user feedback early
- Automate testing and deployment pipelines
- Use Feature Flags to control the release cadence
User Stories
- Describe requirements from the user's perspective: As a [role], I want [feature], so that [value]
- Define clear Acceptance Criteria
- Use story points to estimate effort and help with Sprint planning
- Split stories: Break stories that are too large into ones that can be completed within a single Sprint