This video presents a set of process patterns that facilitate change in software products to ensure that the right product is delivered efficiently with short iterations. Agile projects require that the specifications and testing processes fit into short iterations, which is a challenge for business analysts and developers when they start using an Agile approach.
Watch this video from http://ndc2011.macsimum.no/mp4/Day2%20Thursday/Track5%200900-1000.mp4
This video is a high level introduction into agile requirements traceability. It demonstrates an example of agile requirements traceability. We discuss an example user story and show how detailed requirements captured as test tables can be used to build executable specifications and aid the design process. Finally we wrap up by a brief example of how we would track the progress of multiple user stories across our scrum or kanban wall.
The technique of expressing requirements as user stories is one of the most broadly applicable techniques introduced by the agile processes. User stories are an effective approach on all time constrained projects and are a great way to begin introducing a bit of agility to your projects. In this session, we will look at how to identify and write good user stories. The class will describe the six attributes that good stories should exhibit and present thirteen guidelines for writing better stories. We will explore how user role modeling can help when gathering a project’s initial stories. Because requirements touch all job functions on a development project, this tutorial will be equally suited for analysts, customers, testers, programmers, managers, or anyone involved in a software development project. By the end of this tutorial, you will leave knowing the six attributes of a good story, learn a good format for writing most user stories, learn practical techniques for gathering user stories, know how much work to do up–front and how much to do just–in–time.
Eric Evans advocates on gradual blending of modeling and design into iterative development based on a correct and deep understanding of the domain, avoiding both “analysis paralysis” and the “easiest solution” for a user story, in an attempt to create a solution that expresses the domain and is flexible enough to support future variations of the model.
Behavior-Driven Development is more than a technique for creating and organizing unit tests. It is also a wonderful way to communicate with customers and users about the software being created. This video demonstrates some techniques and tools you can use to start delivering software with BDD. : Using Behavior-Driven Development frameworks, this session explores ways to create software starting with solid Agile requirements, moving all the way through automated testing. We use .NET in C# and Visual Studio ALM, although none of these exact tools are required to accomplish the goals we set forth.
A small video on to share ideas on how business analysts should participate in the Agile development process.
Related article: Agile Requirements
You will learn the basics of Behavior Driven Development (BDD) and Acceptance Test Driven Development (ATDD) as well as how to use these concepts to bridge the gap between requirements and implementation ? on .NET platform with SpecFlow. SpecFlow is an open source project inspired by Cucumber aiming at bringing pragmatic BDD to .NET.
How does a team make sure they don’t lose sight of “non-functional requirements”? Are user stories of any use to make infrastructure more visible in the product backlog? This video presents how teams attempted to resolve these concerns. Discover patterns and anti-patterns of non-functional requirements in an agile world.
This video demonstrates an example of agile requirements traceability. We discuss an example user story and show how detailed requirements captured as test tables can be used to build executable specifications and aid the design process. Finally we wrap up by a brief example of how we would track the progress of multiple user stories across our scrum or kanban wall.
Ruby’s testing culture goes way back, and has been a force for making many Ruby projects a showcase for solid, maintainable code. That said, within a business an exclusive focus on TDD and BDD can easily miss the bigger picture and drive optimizations in the development process that negatively impact the business as a whole. Part business talk and part technical talk, we’ll discuss what “Experiment Driven Development” is, why you should be doing it from day 1 (probably even before writing tests!), and what cool Ruby tools you can leverage to make it happen.keep looking »