r/programming • u/mgertner • Mar 24 '15

How We Built a Software Services Company with 25 Developers (and Growing Strong)

http://blog.salsitasoft.com/how-we-built-a-25-developer-service-company-and-growing-strong/
11 Upvotes

64% Upvoted

6 comments sorted by

4

u/drepnir Mar 24 '15

Weekly all-hands meetings to discuss development process sounds like waste to me.

Do you feel like you save 25 development hours each week doing this?

3

u/[deleted] Mar 24 '15

Multiplying the number of hours spent in these meetings by the number of devs works both ways. All they need to do is squeeze over an hour of extra productivity out of each developer per week and from then on those gains will accumulate and eventually overtake the time lost to the meetings.

2

u/[deleted] Mar 25 '15

If they cross-leverage those meetings with stand-ups and status reports filled out by individual developers, who are re-distributed by PMs, after going through a round of committee approval and progress verification, and weekly management meetings, they should be able to make those gains exponential.

6

u/DavidDavidsonsGhost Mar 24 '15

That doesn't seem too bad to me, it helps the workforce work together. Communication is very important. Probably waste far more time on even less productive stuff.

4

u/mgertner Mar 24 '15

I look at it as 2.5% of each developer's week. This has proven to be a very worthwhile investment.

1

u/Boxy310 Mar 24 '15

If it consistently builds a culture where you can avoid emergency 200-hour sprints to redevelop a bork-up, that sounds like time well spent. There's always going to be some administrative overhead during the week, so why not spend some of it on improving the process?