
If we are trying to improve a business practice, then the user must be involved from the start, That didn’t happen in this case and we paid the price.
If we are trying to improve a business practice, then the user must be involved from the start, That didn’t happen in this case and we paid the price.
Johnny tells us why his job is like being thrown into a battlefield with no weapon. Why? Welcome to Johnny’s blackest requirements documentation nightmare.
An edit of this article originally appeared on Konsultbolag1 Agile methods are often described as if they were from a completely different world when compared to traditional development. However, a…
How to use interviews to gather requirements. The hardest part is often to come up with bright questions to ask. This article will help in exactly that.
Use user stories to help you write clear and testable requirements. If your documentation is measurable or actionable you can focus on the user’s needs.
We develop and maintain ReQtest use the agile method Scrum, which we supplement with some elements of Lean methodology. In our toolbox we use a number of scrum techniques to…
How to be bipedal in requirements management and testing so as to be more more sought after within your organization as well as on the job market.
7 more common requirements which you should never ever forget about or overlook.
A guide on making sure you’re doing requirements management right, from start to end of a project, without wasting time and money. Who does what, why?
Some additions to your requirements template which will ensure that your requirements are correctly understood and no time and money are wasted.