The 3-Step Guide to Documenting Requirements with Use Cases

The 3-Step Guide to Documenting Requirements with Use Cases

I was once part of a project team that employed use cases to identify which developer was working on the different software modules. We had different colour codes for each developer, so we could easily see at a glance who was working on what functionality and what level they had reached. Most analysts see the use case as a communication tool in holding discussions with stakeholders and for validating requirements. Here are the 3 major steps to applying the use case technique to your project.

Read More

Proof of Concept: Benefits & Risks of Prototyping in Business Analysis

Proof of Concept: Benefits & Risks of Prototyping in Business Analysis

I once worked on a project that involved a series of discussions and consultations on whether to build or buy software. After extensive analysis, the decision was made to build the system in-house. To get started however, we had to prove that it could be done. We did this through a proof of concept (POC).

Read More

Applying the Kano Analysis Model to Requirements Identification & Prioritization

Applying the Kano Analysis Model to Requirements Identification & Prioritization

Because stakeholders make decisions both at conscious and unconscious levels, they are unable to express everything they want in a solution. The Kano Model is a technique that allows the analyst elicit and categorize requirements along two axes: How well requirements are executed and the level of customer satisfaction.

Read More