I was excited for the opportunity to be involved in leading our client’s Infrastructure team in their agile effort, which is what led me to the CST class. The manager had heard stories of the gains in productivity from teams on the Application Development side of their business' Technology Services, and wanted the same for his team. Both of us had a foundational understanding of Agile, but we would be the first team on the Infrastructure division side of the house to implement some form of Agile, so while we had plenty of experience to reflect upon from the AppDev side of the business, it quickly became obvious we weren’t really tapped into the cultural change that appears to be happening across the fence.
As part of our preparation I attended the Scrum Alliance Certified Master Training (CST), and having exposure to the agile happening around me, I can say that understanding Scrum is fairly straightforward. A Scrum Team consists of a Scrum Master, Product Owner, and the Development Team. The Product Owner uses a Backlog to collect, prioritize, and manage the team work. A Sprint is the duration of time, usually 2-4 weeks in length, where the Development Team devotes it’s time to accomplishing the work the team pulls from the Backlog.