Related Content
 |
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. |
|
 |
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. |
|
 |
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. |
|
 |
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. |
|
 |
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. |
|
 |
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. |
|
 |
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. |
|
 |
The Challenges of Multiple "Internets": Desktop, Mobile, and Apps The false existence of "Internets" might have been something to snicker at back in the day, but today, their existence is very real—and a headache for both developers and users. We take a look at how we got here and try to figure out how to return to "One Web." |
