Requirements discovery is also often referred to as requirements elicitation, requirements gathering, requirements analysis, and requirements definition. We prefer to use the term because it’s a little less high-brow, more meaningful, and more app…

How well is the Business Analyst’s role defined in your organization? The Organization Needs a BA Role At a recent Business Analyst World conference in Toronto, it was not a surprise to hear many of the speakers lamenting about projects that continue to roll in late...

Small application development projects are lighter and usually don’t require such extensive process standards, advanced methods, governance, documentation, planning and management that larger IT projects do. But don’t make the mistake of skipping …

What do you need the most when eliciting requirements? Face-time with Subject Matter Experts and their Managers. As a Business Analyst employed in a typical organization, what is the thing you get the least of? Face-time with Subject Matter Expert…

Four simple tests to assess if requirements are not done These are Business Requirements level tests that work and will improve your requirements quality irrespective of delivery methodology: If the requirements lack context: Requirements always e…

Tip 1: Treat RDM software selection as any other project. Follow your project lifecycle and requirements definition and management (RDM) process—as you would for any other project. Apply sound project management and business analysis practices to assure that the...

As a facilitator of Requirements Discovery Sessions, one of your primary skills is questioning. Here are the fifteen types of questions you should be using when you are facilitating a requirements discovery session on your projects. Type Explanati…

We’ve been in the business of helping companies improve their requirements definition and management (RDM) maturity for over 13 years. One thing I’ve noticed is that companies that have made significant improvement in RDM tend to believe they are …