When developers first hear the business has decided to bring in Agile/Scrum, there is a feeling of dread. Agile methodologies are not usually brought in because the “powers-that-be” feel they are getting productive development from their coders. However, if you are an earnest developer you should welcome Agile/Scrum with open arms.
I’m glad you found a positive in what sounds like a horribly toxic environment, but what you’ve described is a long way from a Scrum environment.
A Scrum team should be assessed as a whole, based on the quality, consistency and value of the product increments they deliver, and how they improve their process along the way.
Velocity - commonly used with Scrum but not a Scrum concept - is measured at the team level, and not for any one individual.
From an Agile perspective, this doesn’t sound like an environment that “build[s] projects around motivated individuals, give[s] them the environment and support they need, and trust[s] them to get the job done.”
The real thing lacking in this environment is servant-leadership.