5 ms·

I agree. Looking at the "final practices" of a well-oiled team and just picking them up without any of the context about "why" they work "for that team" is half

• rtkaratekid 6y ago
  As an anecdote of this, I'm in an R&D department of a small company. I'm basically a team of one with an intern (which is its own challenge because he likes to be somewhat micromanaged). My manager just recently was finally convinced to shift from a waterfall module to something agile, except now it's just becoming a micromanagement tool... for a team of essentially 1.5. We had a conversation the other day in which I was given to understand that if we thought some documentation was finished, but had to go back and make a tweak with no more than 15 minutes spent on it, we should be creating a ticket in Jira to do so. I'm currently cursing all the people who've sold agile because this is insanity (imo). Feels good to get that off my chest haha.
  • noir_lord 6y ago
    I have multiple juniors but you just described my life and it makes me want to literally scream.
  • joopxiv 6y ago
    There's few things that are more mind boggling to me than a very rigid interpretation/implementation of agile.
    • charwalker 6y ago
      That's literally not how it works too. Agile has a robust and rigid structure that you then pull from and adapt to make your team and processes better. Few teams have the same implementation. It's important to understand the full scale of agile practices and tools but do not try to do it 100%, that's not the idea at all.
  • SaltyBackendGuy 6y ago
    Just sounds like overkill for a team of 1.5.