Tag: scope

What is the difference between verification and validation? Part 1

What is the difference between verification and validation? Part 1 ArgonDigital - enterprise automation experts

A question we are often asked is “What is difference between verification and validation?” This two-part blog answers that question.  In part 1 we discuss the basic concepts of verification and validation in terms of the context in which they are used within the system development lifecycle.  In part 2 of the blog, these concepts […]

Baseline Your Scope Before Writing Requirements

Baseline Your Scope Before Writing Requirements ArgonDigital - enterprise automation experts

A major issue that contributes to cancelled projects is a failure to establish a shared vision of the final product at the beginning of the project. The reason for a new product or upgrade must be clearly understood before writing requirements, or divergent requirements will be written and important requirements will be missed. This vision […]

Agile and Requirement–Driven Product Development

Agile and Requirement–Driven Product Development ArgonDigital - enterprise automation experts

My previous blog described “Requirement-Driven Product Development” (RDPD). One of my readers asked a very important and well-formed question: “Lou, nice article. Are there any specializations to the approach for software systems? Would you say that Scrum process is consistent with RDPD? I expect that everyone agrees that requirements must drive development. The controversy is […]

Medical Device Development and ArgonDigital

Medical Device Development and ArgonDigital ArgonDigital - enterprise automation experts

We are frequently asked whether or not the training we offer is specifically geared to the medical device industry or if our training is generic.  The short answer – our instructors have extensive experience in providing training for the medical device industry.  We have taught both our standard courses as well as tailored classes for […]

Why are we doing what we are Doing?

Why are we doing what we are Doing? ArgonDigital - enterprise automation experts

A common problem we see on new projects is people jump into writing requirements without first answering the question “Why are we doing what we are doing?”  Many challenged projects (e.g., over budget, behind schedule, not meeting quality standards) can trace their difficulties to the very beginning of the project where there was a failure […]

Importance of Doing the Upfront Work Before Design

Importance of Doing the Upfront Work Before Design ArgonDigital - enterprise automation experts

We were recently asked by one of our clients about some methods that can be used to help drive home the importance of developing proper requirements at the right time…namely at the beginning of the project. Convincing those with whom we work the importance of doing the upfront work…the importance of defining scope and defining […]

Role of the Business Analyst and Requirements

Role of the Business Analyst and Requirements ArgonDigital - enterprise automation experts

We recently received the following question via our Ask the Experts page:  “How much has the role of a Business Analyst changed or affected the gathering and structuring of requirements”. The short answer to this question:  The Business Analyst (BA) has added structure, discipline and knowledge of steps , tools and techniques to effectively execute […]

How do you know your requirements are complete?

How do you know your requirements are complete? ArgonDigital - enterprise automation experts

The bottom line is the set of requirements is complete when all the stakeholders have approved the set of requirements. Define Scope before you write your requirements. From Requirements Expert’s viewpoint, it is that, but more.   What we advocate in our classes is the importance of clearly understanding and defining stakeholder expectations before writing requirements.  This […]