Behavior-driven development, or BDD, has been a buzzworthy term in the testing and development community for several years. At first glance, the elements of BDD seem simple: Testing scenarios! Living documentation! Automation! Reports! That sounds great, so why isn't everyone doing it? Upon a deeper dive, the implementation of BDD needs a lot of forethought and planning, and teams must approach it for the right reasons. Christine Ketterlin Fisher will detail the evolution of one team in its shift to BDD. BDD was selected to help modernize the work that the business analysts, manual...
Christine Ketterlin Fisher
NAIC
Christine started her career as a high school history teacher, but a switch to software training got her started on a career path in technology, where she has held various positions in professional services and development over the past 15 years. Currently managing a team of business analysts and software quality engineers at the National Association of Insurance Commissioners, she has found that her roots in teaching are still important to help build and develop a strong team. She's passionate about ensuring functional teams are equal members of the development team and helping define those roles as they change in a DevOps culture.