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|

Test User Stories with these 10 Tests

How do I test user stories? On most software activity the user stories are a terse reminder of the conversations between product owner, developer and tester. Although user stories are very short, the form is commonly misused and this leads to ambiguity, unnecessary discussion and rework.  In this article we set how to test user stories so that you can ensure that your user stories are high quality and will reduce rework and shorten timelines. I have enjoyed considerable debate online about the validity of even thinking about user story quality.  If you accept that clear user stories are helpful to a project, then [...]

December 27th, 2020|Categories: Blog|

Gartner Points to ScopeMaster as a Leader

24th December 2020.  ScopeMaster is featured by Gartner in a research paper on emerging technology in AI-Augmented Software Development. In their recent research paper on AI-Augmented Software Development,  senior researchers Neil Barton and Arun Bachu, highlight ScopeMaster as a significant emerging technology that can help automate as much as 70% of software development work. "It (ScopeMaster) saves a product owner effort, and eliminates problems that can cause delays and rework during coding..." The paper is available via the link above to all Gartner subscribers. ScopeMaster is a tool that analyses the written text to help software requirements.   ScopeMaster performs the heavy lifting of [...]

December 25th, 2020|Categories: Press Releases|

Computing DevOps Award for best Cloud Product 2020

16th October 2020. Marlow, UK We are delighted to have been awarded the best DevOps cloud product of 2020 by the Computing DevOps awards judges.  ScopeMaster helps DevOps teams deliver better quality software faster and with less rework, which means at less cost. ScopeMaster integrates with existing development tools such as Jira, Azure Devops, PivotalTracker and many others via its REST API and can provide continuous feedback on user story quality for CI/CD environments.   ScopeMaster's brings comprehensive automated requirements analysis to DevOps teams.   ScopeMaster avoids a lot of time wasted by working to ambiguous and poor quality requirements.  Most customers see a 10x - [...]

October 16th, 2020|Categories: Press Releases|

Shift Left Testing

Shift left - defined Shift left or shift left testing is the concept of performing quality assurance work as early as possible in the software development cycle to reduce the overall work required to deliver high quality software. Even in Agile there is a sequence that is followed in software development which is typically as follows: Requirements Architecture Design Coding Release It is has been found that the cost of fixing a defect increases 7-10 times as it moves from the stage in which it was created to the subsequent stage.  For example a requirements problem found within the requiremetns phase might cost $50 [...]

September 13th, 2020|Categories: Blog|
Go to Top