3 ms·
We had a similar experience at my last company, and we tried a few ways to get around it, eventually landing on a workable solution. We started to allow devs t
by grecy 12y ago
We had a similar experience at my last company, and we tried a few ways to get around it, eventually landing on a workable solution.
We started to allow devs to do story cards on their own, for easy stuff (like you said - colors, alignment fixes, CRUD, etc.)
This worked for a while, but we found the number of dev/bug/fix/bug/etc cycles on those stories was waaaay higher than cards done "properly" with pair programming (even big architecture cards).
So then we made the rule that a dev could do a card on their own, but just before committing they would sit down with another dev and show and explain it to them, thus helping to catch any little "gotchas".
This works really well. i.e. the whole point of Agile is there are no rules, you're supposed to come up with your own based on what works best for you and your org.