A lot of books and blogs and experts tell us to use “The System shall…” when writing requirements. Read on to find out why that’s not a very good idea.
Business Analysis / Prioritization / Product Management / Requirements / ROI
Posted on:
Product Growth Strategy
Growth is a make or break measurement for products and companies. Investment is often determined by expected value, which is based (in part) on expectations of growth. When you create a product, there are aspects of growth – how many people can use your product, and how many people do […]
Business Analysis / Interface Design / Marketing / Product Management
Posted on:
Freemium Business Model
Ever scratch your head and wonder why you can use your favorite application for free? How can a business actually make money (and stay in business) when they offer their product for free? This article looks at the freemium business model, to see when it makes sense for a company […]
Agile / Business Analysis / Product Management / Requirements / Requirements Models / Software development / User Stories
Posted on:
Agile Non-Functional Requirements
Just because your requirement is not a user story does not mean you have to throw it out when planning your next sprint. See one way (that is working) for managing non-functional requirements with an agile team.
Agile / Business Analysis / Product Management / Requirements / Requirements Models / Software development / User Stories
Posted on:
User Stories and Use Cases
User Stories are one of the key agile artifacts for helping implementation teams deliver the most important capabilities first. They differ from use cases in some important ways, but share more commonalities than you might think.
Business Analysis / Product Management
Posted on:
Inspired By Your Customers
Should your products be designed by your customers, or inspired by your customers?
Agile / Business Analysis / Business Rules / Communication / Consulting / Product Management / Software development
Posted on:
Simple Agile Model Example
A picture is worth a thousand words. Agile values working software over comprehensive documentation, and it values customer collaboration over contract negotiation. With that in mind, how much is a picture of a model worth? Check out a simple example, how it helped, and what we didn’t do.
Business Analysis / Business Rules / Communication / Process Flow / Process Improvement / ROI
Posted on:
The Impact of a Hidden Decision
Business rules are often hidden in processes as hidden decisions. Once you discover that hidden decision, how do you communicate the impact of exposing and managing the decision?
Business Analysis / Business Rules / Process Flow / Process Improvement / Requirements / Requirements gathering
Posted on:
Hidden Business Rule Example
A business process is not just a sequence of steps. A business process is a series of decisions and actions. Some decisions are obvious and can be actively managed. Some decisions are hidden, and until you discover them, you can’t manage or improve them. Here is a real-world example of […]