Year: 2011
Non-Functional Requirements in the Context of SOA
This article presents new concepts to formalize and apply non-functional requirements (NFR) for business processes in the context of Service-Oriented Architectures (SOA). Today, popular languages for modeling business processes do not support the specification of NFRs in a systematic manner. However, there is a strong demand to explicitly address such requirements when designing and deploying […]
Read More
Measuring the Success of Requirements Gathering
The best metric to measure the success of business analysis is to evaluate if business objectives for each project were achieved. This is however not always easy to do and this blog post proposes other metrics to get good indicators of success of the business analysis efforts.
Read More
The Value of Business Analysis in Scrum
Hhow can a business analyst contribute in a Scrum Project? This article discusses the fact that producing a business analysis in Scrum is a goal and not a role. The possible contribution of the ScrumMaster, delivery team and Product Owner, the three Scrum roles, are described. It is often the Product owner that is held […]
Read More
Just In Time Software Requirements
Elena Yatzeck shares in this blog post her thoughts about “value spike”. A “spike” is a short piece of work within an agile project in which one or two programmers may be assigned to do outside of the iteration structure. The goal is to investigates unknown technology problems well enough so you can estimate them. […]
Read More
Does Formal Requirements Documentation Have a Place in Agile?
One of the first questions Business Analysts ask when confronted with an agile method is “How agile method cant incorporate our documentation.” And sometimes it is not a question, but an affirmation. This article provides good framework for integrating agile and formal documentation.
Read More
Building the Right Scope
In this article from chapter 4 of Specification by Example, author Gojko Adzic explains how to work together with business users to come up with the right stories and that the key idea to achieve that is not to start with user stories but with business goals and derive the scope from that.
Read More