Development Agile Test & Quality Assurance Project Management Requirements
CM & ALM Devops Cloud Mobile People & Teams

By Topic

Requirements

Requirements and Business Analysis Stories
Are You Experiencing Product Manager Insomnia?

What should be keeping you awake is what keeps your customers awake. Remember to be market-driven and to focus on the problems that your customers value—and are willing to pay to solve.

Scott Sehlhorst's picture
Scott Sehlhorst
Clean Language in Business Analysis

Clean Language originated within the discipline of therapy and focuses on understanding other people’s personal metaphors. It can help business analysts to form better questions and prevent inadvertently leading or pre-supposing a solution.

Adrian Reed's picture
Adrian Reed
The Right Way to Split User Stories

One of the key techniques in the mechanics of agile software development is the splitting of epics into stories. Scott Sehlhorst highlights examples of ways to split user stories and discusses the debate between breadth-first and depth-first development.

Scott Sehlhorst's picture
Scott Sehlhorst
Dodging the Requirements Hazard

Tacit knowledge includes the knowledge that business stakeholders possess that isn’t codified or written down anywhere—and information they don’t even know they possess. The challenge for business analysts is that it is essential to get at this type of information in order to write requirements.

Adrian Reed's picture
Adrian Reed
Hiring Technology Product Managers: The Latest

Scott Sehlhorst looks at an analysis of how companies are posting requirements for hiring new technology product managers in the US—including the trend of placing more importance on domain experience than product management experience.

Scott Sehlhorst's picture
Scott Sehlhorst
Business Analysts—Don't Hide from the Data Model

Among business analysts, there is often a real reluctance to model data as it is seen as a technical activity rather than a business-focused activity. Adrian Reed explains why data models are important, and how they can help map out and understand the problem domain to avoid misunderstandings.

Adrian Reed's picture
Adrian Reed
Don't Let "Good" Ideas Go Bad!

Organizations need new and innovative ideas to solve complex problems. However, sometimes "good" ideas can be the very reason behind problems. Systems thinking and following the Golden Circle can help.

Sameh Zeid's picture
Sameh Zeid
How to Write Good Software Requirements

Even in 2013 software professionals are still having difficulties getting good software requirements. Joe Townsend lists several handy resources on how to finally start writing quality software requirements.

Joe Townsend's picture
Joe Townsend