Category: Requirements Gathering (aka Elicitation)

A question file is one of the simplest tools for keeping track of what you know you know, what you know you don’t know, and what you don’t know that you do know to contain what you don’t know you don’t know.

Business Analysis Question: What Do You Know? Ben Franklin once observed, "... the more we know, the more we feel that we don't know." Actually, I’m going out on a limb here and assuming that he was neither the first nor the last to voice that thought, albeit he did...

JRP sessions are a viable option for getting to business and stakeholder requirements in a hurry, whether the project that implements the requirements follows an Agile or a traditional software development methodology.

Getting stakeholders together for a requirements discovery meeting is a phenomenal tool for collaborative development, one of the cornerstones of the Agile philosophy. Holding these sessions in the cloud can further improve the ROI while improving the outcomes.

Listening is onve of the critical skills that anyone whearing the business analysis hat needs to master. There is more to this simple action than meets the ear.

The difference between problems and opportunities is primarily one of perspective. Some people see problems in opportunities, others see opportunities as problems. What’s your take?

Business requirements exist in the wilds of organizations around the world, The challenge is to capture, clarify and confirm them as early as possible.

Many different roles are involved in delivering working IT soluitons. From the business community to the IT community, the players may wear many different hats throughout the project. It is important that each hat is a good fit to ensure project success.

Time-boxed requirements discovery sessions have been around since 1979 under a variety of acronyms. They are as germane to the challenge of enhancing communicaiton between IT and the business community today as when they were first conceived.

Examples of good versus bad business requirements anno 2006

Where is the Challenge with User Requirements? User Requirements are obviously very elusive little things. They seem to be extremely difficult to capture and, once captured, seem to be brilliant at hiding and escaping. It would appear that they have an uncanny ability...

The general idea of JAD was to assemble a cross-functional team consisting of subject matter experts and systems analysts/developers. Put this group off-site under the direction of a skilled and motivated facilitation team, this group could define high-quality business and stakeholder requirements in a week.