Holly Bielawa explains that being a a requirements craftsman means that you need to test your assumptions in real time while developing a product. Then you pivot as needed, change your business model as you learn, and constantly get out of the building and gather data to determine your minimally marketable product.

Software development can often be a very complex endeavor, so it is no wonder that important details can sometimes get lost in the process. Here, Bob Aiello discusses how to implement configuration management (CM) and traceability in a practical and realistic way.

When designing software, you must look beyond simply knowing the goals of your users. It's far more useful to understand the context in which the product will be used.

Release management is a complex function that involves many essential technical tasks that must be completed in a very specific way. At first glance, one might think that Release Management has little or nothing to do with personality and psychology. In the book Configuration Management Best Practices: Practical Methods that Work in the Real World, Bob Aiello and I focused three of our fourteen chapters on the people side of CM. The fact is that people skills play an essential role in release management. Read on if you want to improve your ability to get the job done and achieve success in release management!