QA/DEV Protocols - Opening high quality bugs
Opening high-quality bug reports is a skill — protocols for writing bugs that developers can act on without back-and-forth and that keep the flow moving.
Read more →Making sense of agility, scaling, OKRs, product operating models, and leadership — written from 15+ years in the field.
Opening high-quality bug reports is a skill — protocols for writing bugs that developers can act on without back-and-forth and that keep the flow moving.
Read more →Documentation of process flow patterns for issue tracking — early thinking about how work flows through software teams before Kanban made this thinking mainstream.
Read more →Patterns for tracking issues across multiple concurrent releases — early thinking on how to manage parallel streams without losing visibility or introducing conflicts.
Read more →After evaluating options, JIRA was an easy decision for issue tracking — a post-migration look at what made the difference and what lessons apply to tool selection in general.
Read more →Update on multiple fronts: JIRA migration, Aqua tool evaluation, organizational changes, and the challenges of keeping up with tooling decisions in a growing software team.
Read more →Building a test case management solution using agile practices: iterative development, continuous feedback from QA teams, and evolving the tool alongside evolving testing needs.
Read more →