3 ms·

Before Scrum we had 3x 1-hour team meetings a week to talk about what we're on and what we might need help with. After we went "agile" we moved to having 3x 1-h

by rr808 4y ago

Before Scrum we had 3x 1-hour team meetings a week to talk about what we're on and what we might need help with. After we went "agile" we moved to having 3x 1-hour team meetings a week with the same. Power to the developers. :)

khazhoux 4y ago
Ha, I remember the first project I encountered that "went Agile." The weekly team meeting (which everyone complained about) was replace with daily standups (30 minutes), a two-hour retrospective (useless) every 2 weeks, and a 2-hour sprint planning every 2 weeks. Power to the developers indeed.
- IMTDb 4y ago
  So basically, you are able to find the time to criticise your team process in a completely unrelated HN post. But when there is dedicated time for that - in the process itself - you call it "useless" ? ;-)
  - khazhoux 4y ago
    Not unrelated: the entire comment thread is about developer process. And retrospectives were useless in the most literal way. The time spent every week going over "What worked well? What could have gone better?" did not materially improve the team's effectiveness.
    - IMTDb 4y ago
      The next retro is the place to discuss why these retro do not yield to any measurable improvement, and agree on a better process/schedule that works for your team. If your point is that your team processes are sooo perfect and sooo amazing that there is nothing to criticise, review or change, I'll have a hard time believing that. If your point is that no matter how much time you spend on these meetings, nothing changes, I'd argue that you need to spend even more time and energy on them on them as you clearly haven't figured out how to efficiently gather, analyse and act on self-reflection of you team processes. The retro itself might be the starting point of your thought process since it seems so "useless" and yet is absolutely essential if you don't want an external "manager" to do that job for you.
      - khazhoux 4y ago
        The team was not particularly more effective after doing the Retrospective ceremonies for many months. The themes that emerged on day one were the same every sprint and the same as for any software org: more communication needed with users, more alignment with stakeholders, faster feedback helps, etc. Every team I’ve worked with has strived to improve on these, but I never saw any actual improvement that I could trace back to the Sprint Retrospective.

by rr808 4y ago

khazhoux 4y ago

Ha, I remember the first project I encountered that "went Agile." The weekly team meeting (which everyone complained about) was replace with daily standups (30 minutes), a two-hour retrospective (useless) every 2 weeks, and a 2-hour sprint planning every 2 weeks. Power to the developers indeed.

IMTDb 4y ago
So basically, you are able to find the time to criticise your team process in a completely unrelated HN post. But when there is dedicated time for that - in the process itself - you call it "useless" ? ;-)
- khazhoux 4y ago
  Not unrelated: the entire comment thread is about developer process. And retrospectives were useless in the most literal way. The time spent every week going over "What worked well? What could have gone better?" did not materially improve the team's effectiveness.
  - IMTDb 4y ago
    The next retro is the place to discuss why these retro do not yield to any measurable improvement, and agree on a better process/schedule that works for your team. If your point is that your team processes are sooo perfect and sooo amazing that there is nothing to criticise, review or change, I'll have a hard time believing that. If your point is that no matter how much time you spend on these meetings, nothing changes, I'd argue that you need to spend even more time and energy on them on them as you clearly haven't figured out how to efficiently gather, analyse and act on self-reflection of you team processes. The retro itself might be the starting point of your thought process since it seems so "useless" and yet is absolutely essential if you don't want an external "manager" to do that job for you.
    - khazhoux 4y ago
      The team was not particularly more effective after doing the Retrospective ceremonies for many months. The themes that emerged on day one were the same every sprint and the same as for any software org: more communication needed with users, more alignment with stakeholders, faster feedback helps, etc. Every team I’ve worked with has strived to improve on these, but I never saw any actual improvement that I could trace back to the Sprint Retrospective.