window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'G-921TFQBWCD');


Articles written mostly by the team at ScopeMaster about software requirements analysis, sizing and QA. We hope you find these articles helpful.

Software Benchmarking and Appropriate Benchmarks

Software benchmarks for project predictability You want to compare how you are doing against others, internally or against teams in other organisations.   For comparisons between internal teams you can establish your own internal benchmarks, whilst for comparing against others in the software industry, you'll be looking for industry software benchmarks. This article focusses on appropriate benchmarking [...]

Large Software Projects – Success

Large software projects are highly prone to delay and even failure.  For success, careful planning, effective communication, and a high level of technical expertise and focus on quality are needed to overcome many of these challenges. The Standish Chaos Report  and the CISQ group's Cost of Poor Quality Report 2022 both [...]

Rework on Software Projects

Software Rework Explained Software rework, is the consequential work that arises from altering requirements, designs, code and tests after some work has already been started.  On most software undertakings this represents 30-50% of all activity.  We generally exclude bug fixing from the category of software rework.  Rework generally describes the extra [...]

Requirements defects – the value of finding them early

Here are some insights into the value of finding requirements defects  before design or coding. To a software development team it is very valuable to find defects early.  Even better still, is to prevent defects altogether.  Excellent requirements are an effective form of defect prevention and rework prevention.   An ambiguous requirement [...]

Story Splitting – Guidelines and Tips

Story splitting - refinement to an optimal granularity An apparently small story may turn out to be much bigger than expected. Only by refinement or story splitting can you discover this. Story splitting can be done early or just before the preceding sprint. We recommend doing it as early as possible [...]

User Story Quality Assurance – Automated

Let us look at how and why we might want to quality assure user stories.  Poor user stories lead to unnecessary meetings, waste and rework.  Improving user story as early as possible in the development lifecycle is an effective way of minimising waste and rework. Quality assurance is a systematic [...]

Software IV & V

Independent Verification and Validation of Software Projects IV & V stands for Independent Validation and Verification. Definition: According to NIST IV&V is:  A comprehensive review, analysis, and testing, (software and/or hardware) performed by an objective third party to confirm (i.e., verify) that the requirements are correctly defined, and to confirm (i.e., validate) that the system correctly [...]

Go to Top