4 ms·
That's actually a quite good ratio:). When I deal with our IT, it's usually 1 or 2 line managers, 1 business analyst, 1 or 2 project managers and 2 architects.
by maxxxxx 9y ago
That's actually a quite good ratio:). When I deal with our IT, it's usually 1 or 2 line managers, 1 business analyst, 1 or 2 project managers and 2 architects. Double this up if two groups are involved. None of them is involved in doing the work. The work goes to India and then if you want to get the work done right you try to schedule night late meetings with the one or two people there and explain everything from scratch.
From the outside it looks like they have a rigorous process of estimating, evaluating, writing requirements and stuff but it's almost pure overhead.
- nulagrithom 9y agoUgh, pure overhead, exactly... Apparently someone produces some technical looking but actually vague document every week as a result of these meetings. Some date is thrown out, and _something_ is always deployed by that date, albiet buggy and destined to get rolled back. Eventually, someone figures out that the implementation doesn't actually work at all, and we go back to the weekly meeting with the "new requirements", and repeat until the thing actually works in some semblance of the manner that we need -- or run out of time, scrap it, and move on to more pressing things. Maybe I should try scheduling some late-night meetings with the senior guy... He's sharp as hell, but we never get too technical during the meetings because that would just confuse people.