Requirements Management – I’m embarking on a journey to help several teams manage their requirements with their existing systems and tools. This is the first in a series of articles, where the rubber meets the road. I’ll look at both the theory and the realities of what works (and doesn’t) in practice. I hope you’ll come along for the ride.
Read the rest of the article …
Tag Archives: requirements management
Requirements Management Journey – Part 0
User Goals and Corporate Goals
When defining requirements, you always start in the context of a goal – either a user goal or a corporate goal. You need to be aware of both. Having a positive user experience is important, and requires a user-centered understanding. Achieving your corporate goals might be in conflict with some user goals.
Read the rest of the article …
Global Actor Hierarchies and Personas
We use actor hierarchies to organize the different users of a system. Different people play different roles, and thus do different jobs. We use different actors to identify and organize those people. When deploying a system globally, we usually discover people that do the same jobs, but do them differently. Incorporating the notion of personas lets us deal with this.
Posted in Business Analysis, Interface Design, Product Management, Requirements, Requirements Models, UX, Usability
Tagged actor hierarchies, actor hierarchies and personas, actor hierarchy, actors, actors and persona, actors and personas, global actor hierarchies, global actors, global hierarchies, global personas, managing data, managing requirements, persona, personal goals, personas, Requirements, requirements management, use case to actor, use cases
2 Comments
Separating Business Rules From Requirements Increases Agility
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.
Read the rest of the article …
Business Rules And Requirements – Early Thoughts
We had a great interview with James Taylor a couple weeks ago, where we talked about his new book, Smart (Enough) Systems, co-authored with Neil Raden.
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.
Latest Articles
Comments on all Articles
