Blog
Government interest in automated functional sizing
June 17th 2019. We are delighted to have been invited to present the value and power of ScopeMaster at a forthcoming western government conference to be attended by software acquisition specialists from a spectrum of public sector departments. The event takes place later this summer. ScopeMaster's unique ability to automate functional size estimation has caught the eye of government specialists who are challenged to achieve reliable estimation and fair cost of software acquisition. We will let you know more details as soon as we can.
ScopeMaster Finalist for Four Industry Awards
We are very proud to be shortlisted as finalist in four categories of this new industry award. At the heart of ScopeMaster is Natural Language Processing, a branch of AI. We are using NLP to solve the specific problem of poor quality software requirements. And it works very well, successfully improving the quality and measurability of software requirements or user stories. It's never been done before, and the benefits of using ScopeMaster early in a project are substantial. We, and our growing client base, are delighted with the value it is bringing to their software work.
Benchmarking and Estimation
Notorious for costly delays, large software projects cost billions of dollars more than they should. ScopeMaster's upgrade today delivers more predictability and transparency for executives. ScopeMaster Ltd is a new company with a unique and carefully-researched approach to solving the problems of large software project delays, cost overruns and failures. ScopeMaster uses AI to analyse and measure software requirements. Today, ScopeMaster Ltd announces the availability of an enhancement that brings even greater predictability to software projects cost, and schedules. Reliable Software Development Estimates The new capability can help CIOs, software project managers and bid managers estimate projects faster. It is now possible to reduce [...]
Lessons for all Software Endeavours
"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. [...]
Static Requirements Analysis
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 [...]
Better User Stories – 10 tips
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 [...]
