Quote:
Originally Posted by suzzer99
At my old job - if we didn't have QA we'd be much slower. They allowed the devs to focus mostly on golden path and not spend a ton of time testing for every edge case. Which is very time consuming due to stuff like setting up test users - which has to be done with a bunch of hairy back end systems we don't control.
I also like the primary detailed domain knowledge of *what* the system does residing with people who know nothing about *how* it works under the covers. Feels cleaner to me.
I think the first part is maybe very company/product specific. My general feeling is that developers should be able to automate and do all the things that you're talking about because thats the best way to actually test stuff (which they should be doing!).
I disagree with the *what* and *how* comment. It does feel cleaner, but it feels like a "false win" in the sense that those two are so tightly interconnected in practice that its going to be way more efficient to expect people to know both of those things. For any sort of complex system I don't see how developers can add new features without a good understanding of the existing features and how/what they're suppose to do.
Quote:
Originally Posted by goofyballer
Situation B: on a much larger team, forget if it was daily or 3x/week but there'd be a morning standup for the whole team of ~30-40 producers + engineers. Worthless, total waste of time, I very quickly figured out I could avoid it because I didn't sit in the same area as the rest of the team so I peaced the **** out of that one
I remember getting to this point (~20-25 people in the all-company scrum). We switched it to a monthly (optional) demo where people could show what they're working on. Easy way to still showcase what you're doing to everyone without being a giant waste of time.
Quote:
Originally Posted by Victor
ya this is super important. most of the reports from devs should just be "no update". they should only be commenting if they need help with something, need to communicate something important that may effect others, or need to set up a meeting later for deeper discussion. its absolutely not a time to rattle off all the work you are doing. no one curr.
A few years ago I switched from doing standup with individual updates and instead go through Trello. We have a list of QA tasks and a list of In progress tasks and we just go through those and whoever has anything to say, says it. Often the update it just "Working on it" or "Didn't work on it".
Then at the end I ask if anybody has anything to add or anything we missed.
I actually like it way better than the personal updates because its less opportunity to ramble off topic or list out all the non team things they did.