4 ms·

Precisely. I worked in a dev org with under 100 devs/dev managers, which had 0 budget for project managers, QA, (or a DR plan for that matter) but did have budg

Precisely. I worked in a dev org with under 100 devs/dev managers, which had 0 budget for project managers, QA, (or a DR plan for that matter) but did have budget for no less than an entire team of 3 fulltime "agile" coaches/consultants for upwards of 4 years or more. The word has been stolen by the worst charlatans who are enriching themselves on the back of our industry.

rightbyte 3y ago
Ye why is this. How can it be so easy for management to get permission to hire a Scrum Lord but not a designated QA dev? Like, in big projects I would like one QA for every 5 programmers to keep us from building backwards.
- steveBK123 3y ago
  Precisely. Incentives. CTO can pitch "going agile" and how its the latest & greatest, and they are going to get more output out of the dev org more quickly. "Hiring some QA" is not nearly as sexy.
  - rightbyte 3y ago
    Which is funny since the QAs would actually pay their wages in savings (to some number of QA devs) or increase speed while e.g. a Scrum master in my experience increases admin burden for the devs.
- jasonwatkinspdx 3y ago
  In my experience management has a lot of anxiety over long term planning for software teams. What are we going to get built by when? Are we focusing on the right things? How do I keep things from falling apart because one key team member leaves? Scrum et all offer what looks like systematic answers to these understandable concerns.
  - steveBK123 3y ago
    Yes but near-zero tech management / stakeholders pay any attention to the metrics that come out of say, Jira which would help them understand that. So you end up spinning up a dozen different manual reports at different granularity levels that take all Friday afternoon to do.. mostly in excel/outlook, and.. so again its just manual grind work and qualitative fluff.

4 ms·

Precisely. I worked in a dev org with under 100 devs/dev managers, which had 0 budget for project managers, QA, (or a DR plan for that matter) but did have budg

by steveBK123 3y ago

rightbyte 3y ago
Ye why is this. How can it be so easy for management to get permission to hire a Scrum Lord but not a designated QA dev? Like, in big projects I would like one QA for every 5 programmers to keep us from building backwards.
- steveBK123 3y ago
  Precisely. Incentives. CTO can pitch "going agile" and how its the latest & greatest, and they are going to get more output out of the dev org more quickly. "Hiring some QA" is not nearly as sexy.
  - rightbyte 3y ago
    Which is funny since the QAs would actually pay their wages in savings (to some number of QA devs) or increase speed while e.g. a Scrum master in my experience increases admin burden for the devs.
- jasonwatkinspdx 3y ago
  In my experience management has a lot of anxiety over long term planning for software teams. What are we going to get built by when? Are we focusing on the right things? How do I keep things from falling apart because one key team member leaves? Scrum et all offer what looks like systematic answers to these understandable concerns.
  - steveBK123 3y ago
    Yes but near-zero tech management / stakeholders pay any attention to the metrics that come out of say, Jira which would help them understand that. So you end up spinning up a dozen different manual reports at different granularity levels that take all Friday afternoon to do.. mostly in excel/outlook, and.. so again its just manual grind work and qualitative fluff.