We had a great year in 2013. Thank you to our members for suggesting the topics, facilitating and presenting, and participating in DFW Scrum month after month. Our goal is to help you do better today than you were doing yesterday, and the best way to do that is through the collective wisdom and experience of the crowd (sprinkled with some industry experts). Our last three meetings of the year exemplified our goal and values.
September: DEV+QA in the same sprint – how’s it possible?
Dave Nicolette led the group in a discussion of how the magic of getting dev and QA to work close together and complete their work within the sprint happens. Challenges can come from large stories, unclear or missing acceptance criteria, multiple product owners, and a lack of automated testing. These challenges are quite common, and the beauty of our user group is that we can rely on the wisdom of the folks in the room to share their experiences and successes! Spending time refining or grooming the backlog so stories are smaller, the requirements and acceptance criteria are better understood, and even writing the acceptance criteria to be testable can be helpful. Teams that move to behavior driven development (BDD) do all of that while also building automated tests. The magic is that QA spends time helping to clarify or reveal the acceptance criteria, which the developers need to know in order to write the software—the relationship between dev and QA becomes closer with this mutual need, and the delivery of stories within a sprint becomes easier. That’s the magic.
October: The Science Behind High-Performance Teams
Peter Saddington, CST, visited us from Atlanta to talk about the behavioral science, neuroscience, and psychology behind high-performance teams. Self-organizing teams are made up of individuals, and each individual has certain behavioral patterns. These behavioral patterns can be identified using various assessment tools, and knowing the behavior patterns of individuals can be extremely helpful in forming teams because they contribute to the team dynamics. What does someone love to do? What types of problems do they enjoy solving? How do they know they’ve done a good job at something outside of work? The answers provide insight into a person. A strong team includes diversity. Teams should also have fun together. Executives don’t ask to increase fun in their organizations, but happier people are more productive and innovation increases. The biggest obstacle to fun in most organizations is multitasking or context switching. And if you require your team members to work on more than one project at a time, you put quality, speed, and value at risk. Leaders should be “lovers of people” and “inspiration starters.” Slides are available here.
November: Using Agile Outside of IT
We had 3 of our user group members share stories of how they use agile frameworks and practices outside of IT—Jennifer Nusbaum in an educational registrar environment, Tony Akins at home to write a book and mow his lawn, and Ty Crockett at home with his family to do household chores and his son’s school project. Each presentation reminded us of some of the core concepts behind agile and scrum: how a backlog provides visibility and focus, how iterative and incremental work can get the job done, and the importance of reflecting back on how we can improve for future projects. It was our first time having multiple presentations at one meeting, and it was quite successful! We would love to have more members volunteer to share their experiences like this.
What did we forget to say about these meetings? Comment and let us know.