Content tagged with: headline
User stories are a technique taken from the agile development playbook that can easily be applied in traditional systems development and maintenance. User stories help you document needs in a structured way, from the users’ perspective. They’re a good basis for test cases, so as to support integrated requirements management and testing. In this article, you’ll find concrete advice based on our own experiences developing the requirements and testing tool ReQtest for how you can make user stories the basis for requirements management and testing.
When you are gathering and documenting software requirements, it is not always easy to remember all the dimension that should be included in this activity. The book “Mastering the Requirements Process” proposes a template that should help you in this activity.
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 also provides some input on how to handle conflict between stakeholders.
Certification has become a mainstream feature of professional careers. Various business analysis and software requirements organizations exists that offers both a community for sharing knowledge and certifications opportunities in a similar way than the Project Management Institute provides for project management domain. This article presents a list of business analysis and software requirements certifications currently available from different professional organizations.
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.
The title of one of the initial chapters of this book is “The Big Picture of Agile Requirements”. This emphasizes that agile requirements are more than user stories on a small card. In this book, Dean Leffingwell presents the big picture of agile requirements, together with the small details that can help you write better user stories. He also discusses the interesting concept of the Agile Release Train (ART) that aggregates user stories in features set.
This article discusses the clarity of requirements for software development and explains how you can use a four step process for gathering them with the four levels of agile requirements.
This book from Henriette Baumann, Philippe Baumann and Patrick Graessle is a very good introduction to the power of modeling with UML. After an initial presentation of the basic principles of modeling and UML, the book presents the diagrams used to model both business and software views of systems. The final part is devoted to the models that can be used for system integration.