Cracking On

We were just a team of four when we started, and we had to wait a few days before the two new members could jump on board. Eldon and I decided to split the job and tackle the two most critical tasks – one task each.

While he was setting up the walking skeleton and finding the best way to seamlessly integrate our new REST API with the legacy system that we were constrained to talk to for authentication and login purposes, I took the job of taking care of the requirements with the goal of building a proper acceptance test automation suite. That involved also coaching a BA and tester – this was the most delicate part of the job, in my point of view. I had already committed on it with them, and I couldn't let them down.

Typical discussions about Behavior Driven Development (BDD) frameworks arose, but the process to use a new framework for the team would have to go through bureaucracy and middle management – something we wanted to avoid because...