3 ms·
My previous jobs: What worked for X (200 people in engineering) didn’t work for Y (8 people in eng) didn’t work for Z (1600 people in eng.) What worked in iso
by dmitriid 9y ago
My previous jobs:
What worked for X (200 people in engineering) didn’t work for Y (8 people in eng) didn’t work for Z (1600 people in eng.)
What worked in isolated teams didn’t work in cross-functional teams didn’t work in cross-domain teams etc.
You find what works for your specific setup, and stick to it. If it doesn’t after a few iterations, you change it. Rinse, repeat.
Current setup that works for us:
- Company-wide broad initiatives for the coming year, prioritized.
- Quarterly planning for teams with goals and projects aligned with company initiatives.
- Our team has week-long sprints, with a retrospective every two weeks. Issues are prioritized by technical and product leads of the team, so at the beginning of the week we know what the most pressing issues are, and how many of them we can take on (and complete within a week).
- Once a month there’s an all-hands were all teams in our domain discuss their progress on their projects/goals (because that may and will affect dependent teams).
Is it perfect? No. Does it work for us? Yes. Do people question this? Yes, and we make adjustments as we go along. Is it agile/scrum/kanban? I don’t know and I don’t care :)
—————
tl;dr
- Prioritize your shit on all levels (company, department, team)
- Select whatever processes you want to go throught the prioritized list
- If processes don’t work, adjust/change them