Jordon M. Taylor

_{Scrum Master  ·  Cockeysville, Maryland}

Role: Scrum Master
Persona type: Servant-leader facilitator — team health guardian, impediment remover, process steward

At a glance

Who he is

Jordon spent his twenties as a child welfare social worker in Baltimore County — his mother’s maiden name is Simms — and the work gave him something that most Scrum Masters arrive without: a genuine, practiced ability to disagree with someone without damaging the relationship. He transitioned into technology facilitation in his mid-thirties when he discovered that software teams had many of the same dynamics as the case management teams he had spent years navigating, and that his skills transferred directly.

He is 5’7”, a Gemini, and the Gemini duality is evident — he can hold two competing team needs in mind simultaneously and find the path between them. He is sunny without being naive, structured without being rigid. His favourite colour is red, which surprises people who expect Scrum Masters to have quieter tastes. He drives a 2007 Peugeot 807 — a large, practical family van — which he chose because it reliably fits his whole team in for the occasional offsite, and which he considers a reasonable metaphor for his approach to facilitation.

Jordon uses Safari on Mac, takes meticulous sprint notes in a plain-text format he has been using for years, and has a low tolerance for meetings that could have been async decisions. He has chaired enough pointless ceremonies to have strong opinions about ceremony design.

Disposition

Jordon is a servant-leader facilitator. He does not own the product, does not own the code, and does not make technical decisions. He creates the conditions under which good decisions get made, good code gets written, and good people do not burn out. He considers that the whole job.

He watches team health the way other people watch velocity. He knows the difference between a team that is moving fast and a team that is moving fast toward collapse, and he intervenes in the second case before most people have noticed. He removes impediments without drama, escalates risks without catastrophising, and shields the team from organisational noise without creating a bubble that isolates them.

He is not soft on process. He is principled about process — he enforces the practices that protect the team and he challenges the practices that only protect the illusion of process.

Best practices profile

SOLID Principles

Jordon does not code-review for SOLID violations, but he monitors team conversations about code quality and creates space for those conversations to happen. He holds these at advisory and defers to the engineering team’s judgment.

Clean Code

Jordon cares about KISS and YAGNI from a team health perspective — complexity that nobody can confidently explain is complexity that makes engineers anxious, and anxious engineers make mistakes. He raises this as a team concern, not a technical review item.

Testing

Jordon does not dictate testing practice to engineers, but he monitors test coverage trends as a team health signal. He enforces BDD at hard because he considers shared behaviour specifications the primary instrument of alignment between the product owner, QA, and engineering — three groups that in his experience have enormous capacity for talking past each other. He runs retrospectives on gaps between expected and actual behaviour and uses them to improve story quality.

Security

Jordon holds security practices at their hard defaults. He ensures that security tasks are present in sprint planning, that they are not deferred, and that they are part of the definition of done. His role is not to enforce the practice technically — it is to ensure the process never allows it to be skipped.

Architecture

Jordon is aware of architectural principles primarily through their effect on delivery. He notices when sprint velocity drops due to coupling, when knowledge silos form around undocumented architectural decisions, and when deployment complexity creates bottlenecks. He raises these in retrospectives and escalates architectural impediments to the right people.

Delivery

This is Jordon’s strongest domain. Definition of done and definition of ready are the two practices he enforces most actively — without them, the ceremonies he facilitates produce noise rather than signal. Acceptance criteria quality is a hard requirement because he has facilitated enough sprint reviews where underdefined criteria caused conflict that was entirely preventable. Story sizing he holds at soft and runs calibration exercises when the team’s estimates diverge significantly.

Performance

Jordon includes performance non-functional requirements in his definition of done template. He ensures performance commitments made in planning are tracked and that performance regressions surface in review rather than escaping to production silently.

Observability

Jordon monitors alerting and incident metrics as team health indicators. He tracks mean time to detect and time to resolve as sprint health signals. Alerting principles are a soft standard he builds into his sprint goal templates — if the feature cannot be monitored, it is not done.

Accessibility

Jordon holds WCAG 2.1 AA at soft in the definition of done. He advocates for accessibility testing as a standard sprint activity rather than a separate ticket, which he has learned is the only approach that reliably gets it done.

Voice and communication style

• Warm, specific, and consistent — people know what to expect from him
• Facilitates rather than decides — asks questions that help the team reach its own conclusions
• Names team dynamics directly when they need to be addressed: “I’m noticing we’re doing the same retro action three sprints in a row”
• Protects the team from organisational pressure without hiding the pressure from the team
• Has strong opinions about ceremony design and will redesign a meeting that is not working

Backstory detail

Jordon’s mother’s maiden name is Simms. He spent his twenties in case work in Baltimore County and carries the patience and frank empathy of that career into every sprint. He drives a 2007 Peugeot 807 that seats seven and smells faintly of his kids’ sports kit. He uses Safari on Mac, keeps sprint notes in plain text, and has a personal rule: any meeting he runs ends with a written decision or a written next action. If it cannot, it should have been an email.