In our previous blog “Using Technology Readiness Levels to Manage Risk” we introduced the concept of Technology Readiness Levels (TRLs). In that article, the basic descriptions for TRLs as used by NASA and the Department of Defense (DOD) were presented. We also mentioned that TRLs descriptions have have been developed for all types of products: […]
Tag: risk management
Using Technology Readiness Levels to Manage Risk
In a previous blog “Are the Requirements Attainable?”, we mentioned that one reason requirements may be not be attainable was because the ability to meet a given requirement was based on an immature technology. Engineers, scientists, and marketing personnel often tend to be overly optimistic as to their ability to meet performance requirements that go […]
Developing Agile Systems
In previous blogs we talk about Why do my requirements keep changing and Controlling and Managing Change during product or system development. Change can also be addressed from the perspective of change that happens after the product or system is put into operations. From this perspective the question to be addressed is: “Can the product […]
Software Requirements and M&A IT Integration
The IT side of M&A integration involves much more than an integration of IT systems; due to the business risk involved, and in the effort to create value from the M&A, it will demand complete, accurate, consumable software requirements. Done properly, it should really start with a negotiation of business needs, with the system integration […]
5 Reasons Software Projects Fail (Hint: It’s Often Due to Incomplete, Incorrect Requirements)
Business analysts are the link between the business stakeholders, an organization’s goals, and the IT teams responsible for software project success. As such, BAs can have a significant impact on whether software projects succeed or fail. According to recent research by Project Management Solutions, the five reasons software projects fail are the following, and all […]
INCOSE 2008 – How to Deal with Vague Software Requirements
Mary Bone presented a paper “Cyclone Process: Dealing with Vague Requirements” at INCOSE 2008 in the technical track. I’m going to try to summarize her work here. Her premise is that existing requirements models do not deal with vague requirements, but rather they specifically aim to remove any vagueness from requirements. However, she contends that […]