Blog

"Technologists have a responsibility to ensure that technology not only does what it should but it doesn’t do what it shouldn’t." I write this as the details of the cause of the Boeing 737 Max air crashes are just starting to appear in the media. I hope that those of us involved in technology will be stimulated by this tragedy to raise our level of professionalism. Two planes crashed before the pattern was observed and the majority of the world's 737 Max fleet was grounded. The Ethiopian Airlines flight eight days ago and the Lion Air aircraft in October both crashed within minutes of take-off. [...]

Definition:  Static Requirements Analysis is the automated testing of software requirements for quality and measurement. Background Software requirements, or user stories, are written statements describing the functional need and purpose of software to be developed.  Authors of these user stories will typically write them from the perspective of a business user.   It is then the job of the developer to read the user stories, and design and code to meet these needs.  The user stories are therefore a means of communication.  With poor choice of wording, communication can become mis-communication.  Poor wording leads to misunderstandings that lead to design and coding mistakes.  These mistakes [...]

Having examined and analysed over 10,000 user stories from different sources we have built up some insight into what represents a good user story.  If you would like to learn to write better user stories, you should find this article useful. What is a user story? Before we start on the 10 steps, let us revisit the question of what is a user story.  A user story is typically described as a placeholder for a conversation about a user need.  Typically we refer to the three C's:  Card, Conversation and Collaboration.  In many organisations however, the user stories ARE the list of requirements. Agile [...]

With our latest version of ScopeMaster, you can now create and apply labels to your user stories.  This can help you get the job done of creating great user stories. Remember that ScopeMaster is still doing the heavy lifting: analysis, interpretation, defect detection and size estimation of your user stories. By creating and applying labels that are meaningful to you and your team, you can organise and filter your user stories to get the refinement work done more easily.