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. In the same intent, a “value spike” is time that the Product Owner takes to assemble the right Subject Matter Experts (SME) for a meeting to determine the authorship and impact of a requirement whose value seems questionable. The PO can come bakc with a fresh view of the value of the feature and perform a new cost/benefit analysis.
Just In Time Software Requirements
Modern software development approaches like Agile and Scrum support a strong collaboration between all member of the software development team, software testers and business analysts included. Even if you don’t use a method like Behavior-Driven Development (BDD) or Specification by Example, checking the fact that you will be able to actually test your requirements is […]Read More
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, […]Read More
This article is an extract of the “Complete Systems Analysis” written by James and Suzanne Robertson. It explains the basics of analysis models and emphasize that the important thing to remember is that modeling tools are complementary. Each shows one aspect of the system. Together, they make a complete working model of the system.Read More