I notice that in your section on “Development Team Feedback Loop”, you’ve myopically missed one of the most important practices that good agile teams take advantage of: Pair Programming.
Even for so-called solo development, for folks that worked remotely; they paired “over the wire” for a good part of the day.
It’s a skill that takes getting used to and requires the same single-minded attention to craft and purpose that you’ve described for the rest of your “better practices”.
Try it, you might see how useful feedback can really be.
/h
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I notice that in your section on “Development Team Feedback Loop”, you’ve myopically missed one of the most important practices that good agile teams take advantage of: Pair Programming.
Even for so-called solo development, for folks that worked remotely; they paired “over the wire” for a good part of the day.
It’s a skill that takes getting used to and requires the same single-minded attention to craft and purpose that you’ve described for the rest of your “better practices”.
Try it, you might see how useful feedback can really be.
/h