From the course: Behavior-Driven Development
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Case study conclusions - Cucumber Tutorial
From the course: Behavior-Driven Development
Case study conclusions
- [Instructor] Vanguard Group was making changes to their software they weren't confident in, resulting in stress and anxiety. And there were too many moving pieces to test everything efficiently. In order to transform the way they tested and developed their code, they had to understand the problem, first. Here are some of the conclusions they came to. Problem number one: throw your problem over the wall. The organization had silos. Developers felt like their only responsibility was to create the code, and then throw it over the wall to the other teams, to find out if it worked correctly. If there was an error that ended up in production, at that point, it was someone else's problem. Problem number two: Traditional Requirements Practice. Because Vanguard Group is a financial company, they are responsible for documentation, due to regulatory requirements. At the time, they had legacy systems for documentation because they used to implement Waterfall, rather than Agile. They still had…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.