Is my team too small for scrum?
· 2 min read
Scrum imo has a laser-focus on a very particular niche type of work - short to mid term projects with requirements changing often where you hire a group of top notch developers that need to do the work.
Why it's not working long term?
- you'll need to cut OPEX costs at some points in time as a manager
- if you hire juniors/mediors to cut costs then in turn you actually raise costs as people would need more time to learn the domain, the product, so on
- if you hire cheap programmers then they may treat this project as a trampoline of sorts, to get more EXP to jump off to a better paying job - bye bye team stability
- you don't want to end up with mediocre people who are "just doing their work"
- if development is eating most money, then maintenance will need to go towards cheaper paid operations personnel
- anyways the team stability is a problem and can influence your work in a bad way due to budgetary constraints - let's say that fishing for seniors who price themselves as mediors is not a pleasant thing to do and what you get is mostly people who could not find a work for a higher pay-grade
- be prepared for a situation where people say they are happy with the job, but they have been sending their resumes for other higher paying jobs since day 1 just in case
Also from my POV Scrum is a nightmare of never-ending sprints, with no time to take a breath due to an overarching project being managed in a push-mode way so push new features to production, withouth really thinking about stability of the solution.
No thanks, I'll pass if I have a say as a manager.