Who is responsible for the product backlog? For many Agilists, there is only one answer - the Product Owner (PO), and by definition, that's correct!

Behavior Driven Development, also known as BDD, is a software development process that can be utilized to help your team deliver value and build more reliable software. As you may have guessed, BDD incorporates various aspects from Agile and lean practices, and more importantly, TDD and DDD.

Have you ever felt like you are so involved with your work that you are losing control of your personal life? Have you ever seen yourself delivering all your work right on time but then forget to pay a bill or buy your wife's birthday gift? Well, let me tell you: you are not alone! What you might not have considered is that, as an enthusiastic Agilist professional, the same good practices that you utilize with all your work can also be very helpful with your personal daily life. But how?

How many times have you come across a story that is ready for testing, but does not fit all the acceptance criteria? Did you know that a majority of cases are related to bad feature file writing? In this snippet, I am going to present some standards and tips on feature file writing. These tips will help prevent late and bad outcomes, as well as endorse software quality using techniques and approaches that will help the Agile team to accomplish a better outcome for the stories within the project.

Agile Trends is an event that aims to push the boundaries of the Software Industry with modern themes, trends and real-world use cases. And of course, Avenue Code was there to sponsor it. In addition to sponsoring, we sent some of our best and brightest to learn from the speakers and fellow attendees. Here's what we learned.

Compared with other leading professions, the software industry is still in the early stages of development.  As in any field, software developers are constantly attempting to identify practices and principles to develop better and faster software. As we've grown up as an industry, we've created resources such as Software Architecture and the Agile Manifesto, the importance of which is clear and well-established. 

The software development industry is still in its early days. Compared to other industries with centures of history and evolution behind them, software development is only beginning to mature. One of the consequences of that relative immaturity is that we still have many recurring problems to solve. In this article, I'm going to talk about one of the most important ones: communication.