A look back at the best from a year ago.

Each Friday, we highlight some of our favorite articles, bundles or reviews that people have submitted to nexus. Check out this week’s Friday Favorites…

We’ve written in the past about why it is important to gather and manage requirements. In short, you avoid some costly mistakes, and fix others before they become too expensive. We’ve also started exploring how business requirements and business rules live and play together. But why should we bother to separate business rules from requirements? One reason is to increase your company’s agility.

Do you think the product managers at 3M ever expected people to make a mosaic of Elvis Presley out of Post-It Notes?

We had a great interview with James Taylor a couple weeks ago, where we talked about his new book, Smart (Enough) Systems.

James is an expert on decision management systems. I spent the late 1990s working on “rules-centric” software systems that allowed us to isolate rules and manage them seperately from other software requirements.

Traditional structured requirements approaches focus on the gathering and management of software requirements, but they gloss over the gathering and management of business rules.

James and I are exploring the best ways to bring these two points of view together.

Change is a reality of our businesses and our customer’s businesses. Without change, there would be no need to purchase new software. Yet many teams seem to both resist and embrace change at the same time. They embrace change because change leads to demand for new software products. And they resist change because it makes it harder to create new software products.

A look back at the best from a year ago.

Each Friday, we highlight some of our favorite articles, bundles or reviews that people have submitted to nexus. Check out this week’s Friday Favorites…

There are at least 7 ideals to keep in mind when designing a user interface. Shmula tells us about them.