Comments by "Cees Timmerman" (@CTimmerman) on "Why Does Scrum Make Programmers HATE Coding?" video.

  1. Instead of forcing them into useless meetings and activities, have you tried asking them what the problem is?
    2
  2. Any interruption does that to me. That's why i tend to start my day with the standup as i hate getting into the zone and interrupted because some sociophile thinks issue trackers aren't bodylanguagey enough or whatever.
    2
  3. I feel your pain. Status is available 24/7 in the issue tracker. Unfortunately some micromanagers want to to break down a simple API into one ticket per endpoint.
    1
  4. Bosses used to just ask you to build stuff. Now they've outsourced that to a Project Manager, and a Scrum Master to supply reports. In theory it's nice to not be bothered with new issues or status updates randomly, but in practice you have to listen to and share a status update every day and get bothered about refining and planning the next block of work ("sprint") while you're in the middle of the current one, and get told off for fixing little bugs you find along the way because "that's not in the sprint".
    1
  5. The point of agile is to adapt. Next sprint should have fewer story effort points.
    1
  6. Just keep hiring temps until you get bought out.
    1
  7. Those managers' garbage should not be collected.
    1
  8. Working on the same thing would make daily syncs useful, but that's already done by git and the issue tracker.
    1
  9.  @julianospald6133  If it's not clear, comment on the PR or issue. Also prevents "he said she said" corporate backstabbing.
    1
  10. And syncing work leads to bore/burn outs.
    1
  11. How did Scrum make people cooperate?
    1
  12. Autonomous dev team? Who sets the sprint goal and feature priorities?
    1
  13. You have to love Scrum because the company uses it. If you don't, you get rejected for lack of experience and not being a team player.
    1
  14. Kanban is a good alternative to Scrum. Each dev has one issue they work on, and when done pick up the next. No time wasted on Tetrising issues into weeks-long sprints.
    1
  15. Great to hear. What do the standups add over the issue tracker status and comments?
    1
  16. The PO is responsible for the product, so should share the pain of the process he chooses to complete it with.
    1
  17.  @DauntingGecko  Doesn't QA just run its test suite on the Acceptance server? Why not have the devs manage the test suite and automate that? Would've saved me a last minute rollback of 50+ changed table headers that were ready over a week.
    1
  18. If dev A gives a story 1 point because he literally just did the same thing last month, i'd give it to dev A instead of dev B who gave it 10 points because he never heard of the library.
    1
  19.  @jacoberinc  And yet the manager with a steady job for the past 20 years gets to kick out a dedicated Python dev after a couple of months due to there not being enough Python work left.
    1