Clik here to view.
3 Reasons to Use State Models to Derive Software Requirements
When eliciting software requirements, there are a few major models that I primarily fall back on to help visualize the process, the system and the requirements: cross-functional process flows, use...
View ArticleClik here to view.
Incorporating the Software Test Team into the Software Requirements Creation...
A lot of the popular literature, training, documentation and processes related to the management of Software Requirements in an organization are typically focused on two constituencies – Users and...
View ArticleClik here to view.
Incorporating the Software Test Team into the Software Requirements Creation...
This is the second post in a series on “why incorporate the test team into software requirements creation earlier” – for the first post, click here. The downsides to not integrating the Test...
View ArticleClik here to view.
Incorporating the Software Test Team into the Software Requirements Creation...
This is the last post in a series on “why incorporate the test team into software requirements creation earlier” – for the first post, click here; for the second post, click here. In the first part of...
View ArticleClik here to view.
Product Managers and Business Analysts: Meet Aadhaar
If your IT projects and requirements elicitation processes seem a little overwhelming, consider what it would be like to be a product manager on Aadhaar. A few months ago, a friend referred me to this...
View ArticleClik here to view.
Business Analysts: Don’t ignore the non-functional requirements
An important lesson for business analysts about non-functional requirements follows… After several months of configuring a core system upgrade for a health insurance company, it came time to test EDI...
View ArticleClik here to view.
Defining Software Requirements to Handle Data Errors – Part 1
“The expected always happens.” Benjamin Disraeli, via Bram Stoker’s Dracula. As software requirements analysts, we have crucial decisions to make regarding those errors often considered rare. In this...
View ArticleClik here to view.
Defining Software Requirements to Handle Data Errors – Part 2
“To not anticipate is already to moan.” Attributed to Leonardo da Vinci As software requirements analysts, we have crucial decisions to make regarding those errors often considered rare. This is part 2...
View ArticleClik here to view.
Defining Software Requirements to Handle Data Errors – Part 3
“Anticipate the difficult by managing the easy.” – Lao Tzu As software requirements analysts, we have crucial decisions to make regarding those errors often considered rare. This is the last in a...
View ArticleClik here to view.
Measuring the Effectiveness of a Feature
There are two possible outcomes: if the result confirms the hypothesis, then you’ve made a measurement. If the result is contrary to the hypothesis, then you’ve made a discovery. Enrico Fermi There are...
View ArticleHow Do You Approach an Analytics Project?
Business Analytics projects – where do you begin? In a previous post, Joy mentioned using decisions to prioritize requirements for business analytics projects. Beginning your project by identifying...
View ArticleIncorporating the Software Test Team into the Software Requirements Creation...
This is the last post in a series on “why incorporate the test team into software requirements creation earlier” – for the first post, click here; for the second post, click here. In the first part of...
View ArticleProduct Managers and Business Analysts: Meet Aadhaar
If your IT projects and requirements elicitation processes seem a little overwhelming, consider what it would be like to be a product manager on Aadhaar. A few months ago, a friend referred me to this...
View ArticleBusiness Analysts: Don’t ignore the non-functional requirements
An important lesson for business analysts about non-functional requirements follows… After several months of configuring a core system upgrade for a health insurance company, it came time to test EDI...
View ArticleDefining Software Requirements to Handle Data Errors – Part 1
“The expected always happens.” Benjamin Disraeli, via Bram Stoker’s Dracula. As software requirements analysts, we have crucial decisions to make regarding those errors often considered rare. In this...
View ArticleDefining Software Requirements to Handle Data Errors – Part 2
“To not anticipate is already to moan.” Attributed to Leonardo da Vinci As software requirements analysts, we have crucial decisions to make regarding those errors often considered rare. This is part 2...
View ArticleDefining Software Requirements to Handle Data Errors – Part 3
“Anticipate the difficult by managing the easy.” – Lao Tzu As software requirements analysts, we have crucial decisions to make regarding those errors often considered rare. This is the last in a...
View ArticleMeasuring the Effectiveness of a Feature
There are two possible outcomes: if the result confirms the hypothesis, then you’ve made a measurement. If the result is contrary to the hypothesis, then you’ve made a discovery. Enrico Fermi There are...
View ArticleHow Do You Approach an Analytics Project?
Business Analytics projects – where do you begin? In a previous post, Joy mentioned using decisions to prioritize requirements for business analytics projects. Beginning your project by identifying...
View ArticleAligning User Expectations with Business Objectives
Projects with clearly defined business objectives can and do fail even if they deliver functionality that syncs closely with the business objectives defined for the project, but do not meet user...
View Article
