How to Keep a Scrum Developer
The idea behind every framework is to implement recognizable and consistent workflows and processes, identify a common vocabulary and theme, and establish a set of understood rules and boundaries. Scrum, as an Agile development process framework, provides great transparency in the development process and can help teams communicate more effectively and gain trust in each other. However, things can get frustrating when team members violate the very basic principles and try to make their own 'flavor'.
We've all seen it. And if you haven't seen it, image playing a game that your friends call football but instead of using the pigskin, you must ride around on bicycles and try to throw a giant hula-hoop around the uprights. Sure, that game might be fun, but it isn’t football and trying to call it football will only tick off those who really understand what football is.
This talk is going to explore 7 ways of misusing Scrum, violating principles, changing rules and being just plain wrong that will tick off other Scrum developers and leave them looking for greener pastures.
Manager, IT Analysis - Nationwide - Application Development Center
Steven Coleman is CSTE certified and has over ten years of experience within the quality assurance field. Steven works for Nationwide Mutual Insurance Company, where he has led several Tier 1 testing projects and has spent the last eight years honing his abilities within the test automation space. During that time, Steven was influential inestablishing Ruby as a test automation standard within the Enterprise. Steven is an Agile, Lean, and Automation enthusiast and enjoys sharing his experiences with the industry