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
The reason for developing a product is so the customer’s organization can address a problem (issue or threat) or take advantage of an opportunity. Defining the problem/opportunity needs to be
An assumption that is often made by many people is that if the proper training is provided, an organization will be able to produce winning products – products that deliver
It was exciting and an honor to attend the 25th Anniversary annual INCOSE international symposium in Seattle, WA. It was great connecting with old friends and clients as well as
ArgonDigital is offering a Requirements Jumpstart Program. We start by training your team on the process, practices, tools and techniques for defining and managing requirements. We then partner with your
Drop by our booth while you are at the 2015 INCOSE International Symposium Lou Wheatcraft and Layne Simmons, both senior consultants with ArgonDigital, will be in our booth (C4) to
In my blog: INCOSE Guide to Writing Requirements updates made at IW 2015, I mentioned the concept of layers of requirements above the system level and provided the following diagram
In this blog, I conclude my discussion on requirement attributes that can be associated with each requirement statement by addressing attributes that help to identify the applicability of the requirement
In this blog, I continue my discussion on requirement attributes to focus on those attributes that help you to maintain your requirements. In Part 1, I covered attributes to help
In this blog I discuss attributes that can be associated with each requirement statement. A requirement expression consists of both the requirement statement plus its attributes. I have organized requirement
This question was asked recently on a popular discussion group. Maybe a better question to ask: “How do I know when the requirement set for the system of interest is
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
Don’t miss out on this opportunity
and request a conversation today!
