I was twelve years old when I first watched Star Trek: The Next Generation. I do not remember much of my first exposure to this seminal piece of television, but I do remember that I did not like the character Wesley Crusher, who was portrayed by Wil Wheaton. As Dr. Sheldon Cooper aptly put it „[He is] the Jar Jar Binks of the Star Trek universe“. However, I do enjoy what Wil Wheaton is doing nowadays, especially with his board game show TableTop on Felicia Day’s Geek & Sundry YouTube channel. Watching an episode of the show Star Fluxx sparked the idea for this column.
Star Fluxx is a science-fiction-themed version of Fluxx, „a card game [that] is different from most other card games, in that the rules and the conditions for winning are altered throughout the game, via cards played by the players.“ (Wikipedia) When I heard the description of the game on the aforementioned episode of TableTop it reminded me of software development projects. Changing business rules and requirements (rules and the conditions for winning), probably sounds familiar to you, too.
When you continuously develop new features and deploy new code to production frequently, quality must not be an afterthought. Today, the Agile style of software development is all about short and iterative sprints, but as a result quality can no longer be taken care of at the end. It has to be addressed throughout the software development process. Quality includes, but is not limited to, assuring that the code works correctly while ensuring that it can be changed with ease when the business rule it implements changes.
THIS IS A PREVIEW. DOWNLOAD ISSUE 9 TO READ THE FULL ARTICLE.