Blog

ScopeMaster Signs Agreement with Metri Group, Netherlands

9th March 2021, Marlow UK Benchmarking and consultancy organization Metri (Amsterdam, Netherlands) and ScopeMaster Ltd (Marlow, UK)  have entered into an exclusive collaboration for the Dutch market.  Companies that are seeking to reduce risk on large software projects, and wanting to achieve cheaper, better, faster software development, can now benefit from the combined experience and wisdom of Metri and the hyperautomation of requirements analysis and measurement from ScopeMaster®. Recent research by Accenture shows that 35% of production disruptions originate from incomplete or unclear requirements. Finding and repairing defects in the User Stories as early as possible therefore saves a lot of money and effort.  ScopeMaster [...]

March 9th, 2021|Categories: Press Releases|

ScopeMaster Hyperautomates Software Requirements Analysis in French, German and Dutch

ScopeMaster Hyperautomates Software Requirements Analysis in French, German and Dutch 4th March 2020, Marlow UK.  Scopemaster Ltd announces it has successfully automated the analysis of  software user stories  (written software requirements) in French, German and Dutch. ScopeMaster is a tool for teams who are defining software specifications and for agile product owners.  ScopeMaster is a SaaS analyser of requirements that brings AI (Natural Language Processing) to the work of requirements analysis.  It helps companies improve their requirements significantly faster than doing so manually (as much as 20 times faster).  Gartner refers to the work being done by ScopeMaster as hyperautomation.  This ground breaking text [...]

March 4th, 2021|Categories: Press Releases|

User story testing – manual or automated

User story testing may sound like a strange idea, but it's not.  In fact its one of the most productive things that you can do on a software project.  It's the epitome of extreme left testing.  If you want to become a more successful product owner, start testing those stories as early as possible.  User stories are an expression of requirements on agile software endeavours.  Like other software development deliverables, they too are also prone to errors.  The particular challenges with user stories is that they can very easily be misinterpreted, which can lead to a lot of wasted work.  In fact they are [...]

January 23rd, 2021|Categories: Blog|

Cost of Delay and WSJF

All software work is time sensitive and there is a real cost of delay.  The speed at which new or improved software is implemented matters. Always. Being the first to implement an innovative capability can be be the competitive edge that makes one company thrive leaving its competitors to struggle. "speed and security are the keys to remaining competitive in the banking space" Saul Van Beurden, Head of Technology of Wells Fargo The business impact of getting some functionality delivered quickly (and safely) is significant - and usually dwarfs the cost of doing the software work. Most businesses have plenty of ideas but insufficient [...]

January 10th, 2021|Categories: Blog|

Work Breakdown Structure – for software

What is a work breakdown structure (WBS)? A work breakdown structure or WBS is a charting technique used in project management for describing the work packages needed to deliver the project.  It includes the sum of the all of the activity required to deliver the project. .   (For a more detailed explanation follow this link to the PMI website). What is a product breakdown structure (PBS) A product breakdown structure, or PBS, is a hierarchical diagram of the what has to be delivered by the project.  A PBS describes the resulting product, whereas the WBS describes the work to create the product(s). What is [...]

January 1st, 2021|Categories: Blog|

Trace Value of User Stories to Business Outcomes

Can you trace the value of your user stories back to business outcomes?  If not, you may be wasting valuable team time on your software projects.  Follow this simple technique to ensure that all your user stories are delivering a valuable contribution to business benefit.    This is an excellent way to prioritise your backlog. Identify the quantifiable business outcome of your software endeavour in business terms. Determine the high level capabilities needed to deliver that business outcome. Finally break down your user stories into bite size pieces of functionality that are needed to deliver each capability. Once you have finished this exercise, you [...]

December 31st, 2020|Categories: Blog|
Go to Top