Ever wondered how to write requirements for UI when writing user stories?
Rupi talks about how to include UI requirements without overloading your user stories
Ever wondered how to write requirements for UI when writing user stories?
Rupi talks about how to include UI requirements without overloading your user stories
During the past six months we have been fortunate to be part of the project team executing on Medibank’s Reinvent project to reposition the ahm business to broaden their appeal and reach new market segments.
When using a new way to document requirements, it can be easy to fall into pitfalls on ‘what not to do’. Ryan will be taking you through practical examples of what to look out for when using BDD, in order to provide a starting point for writing good requirements.
Learning how to write Scenarios can be tricky to pick up. This is why Ryan has decided to write a practical blog on how to write Scenarios using BDD. The aim is to start with the basics of a Scenario using Given… When… Then… and build from there.
Warren reviews Trello as part of our series of Agile Tool Reviews.
Paul introduces a series of Agile tool reviews by discussing some of the ways in which story management software can help.
Warren discusses some of the considerations that you need to take into account when you’re considering using Cucumber with other requirements methodologies, using UML as an example.
Paul introduces Cucumber (and Gherkins), and discusses techniques for developing executable acceptance criteria using a domain specific language. Cucumber is a tool that is frequently used in agile environments and Gherkins are feature files.
Paul discusses the problems with over-specification with regards to common problems and proposes some solutions.
Andrew discusses some of the challenges with eliciting Availability requirements, and begins to propose a framework.
Andrew discusses how global changes in the IT Consulting landscape are affecting the way that software is delivered.