At the time of writing I've a fair few years of working in a SCRUM environment under my belt and have been involved in 2 transitions from traditional approaches to SCRUM. The first I was heavily involved in having completed the PSM1 training and leading a newly formed SCRUM team into the unknown. At this time I was duel rolling as SCRUM master and QA engineer. AS well as setting up the team to follow the SCRUM style SDLC and flows I used my newly found servant leader "power" to bring quality front and centre and build it into the way we as a team delivered software. Additionally we used metrics such as release cycle times and ticket time in status to hone in on where our bottlenecks existed so we could target these areas to deliver software quicker. These will be explored in later posts. You might have looked at the Scrum Guide and be thinking, hey, there's no mention of QA. That's because SCRUM is largely agnostic. You'll see the development team mentione...