Month: January 2013
Business Requirements Document
This short video discusses what the content of a business requirements document should be and provides ten tips on how to create the perfect business requirements document.
Read MoreCo-making Great Products
“Co-making great products” should be the tagline for most of the processes we use today, but sadly the opposite is true. Software development’s an expensive risky business. To deal with the risk, the players involved adopt a client-vendor model where those in the client role give requirements and those in the vendor role estimate time […]
Read More
The Business Analyst Role in Agile Software Development
As companies transition to Agile and Scrum to manage their software development projects, how does this affect the work of business analysts? Nancy Nee, VP Global Product Strategy at ESI International, shares her opinion on the role of business analysts in Agile software development projects and how this approach impacts the requirement gathering activity. She […]
Read More
Asking Open-Ended Questions
Getting the important business needs out of the requirements gathering process should be the goal of every business analyst. In this article, Karl Wiegers discusses the benefits of asking open-ended questions during requirements specification. They are especially useful to discover exceptions to the normal process behaviour. You are then able to determine and describe how […]
Read More
Writing Better Requirements with Examples
Gathering requirements for software development is not always easy and IT guys will often complains that customers have difficulties to express what they want to achieve with a new development project. In this blog post, Lars Hoidahl discusses this topic and explains how examples and screen sketches can help to write better requirements.
Read More