Visit the documentation wiki.
Join Gojko Adzic (author of Impact Mapping, Specification-By-Example and Bridging the Communication Gap), Chris Matts (co-author of Commitment), David Evans and Christian Hassa (Product Owner of SpecLog) in four half-days workshops to learn about Impact Mapping, Story Mapping, Feature Injection and writing good User Stories.
Further Product Owner Survival Camps across Europe: www.ProductOwnerSurvivalCamp.com
Check out our flyer that explains how SpecLog helps with iterative planning and continuous validation and how this fits into an overall delivery process.
Visit the SpecLog documentation wiki on GitHub.
Whitepaper: Supporting ATDD/BDD with SpecLog, SpecFlow and TFS.
This whitepaper provides a brief overview of a possible requirements and development flow supported by SpecLog, SpecFlow and Microsoft Team Foundation Server, in the context of agile software development and ATDD/BDD (acceptance test driven development/behavior driven development).
SpecLog client and server setup: Installation and configuration.
Specification-By-Example is a concept that helps business, developers and testers to collaboratively discover and describe domain details and building a shared understanding. It is a useful requirements analysis and engineering technique, that can be used for just-in-time refinement of user stories with acceptance criteria in agile projects. Specification-By-Example is often combined with tools like Cucumber or SpecFlow, that allow automatic validation of implemented user stories and provide a living documentation about the system. Driving development with business readable examples is often referred to as “acceptance test driven development” (ATTD), which extends the outside-in approach of TDD.
The following links provide further information on this topic:
SpecFlow is an open source BDD tool initiated by TechTalk, that allows automated validation of Gherkin based specificiations on .NET. SpecLog integrates with SpecFlow and other source code artifact based BDD tools. More information on Gherkin based automation tools can be found at:
The product backlog is more than just a priotized list of epics and user stories. There are various mapping techniques, that help with evolving and refining the product backlog as well as comprehending the scope of a system.