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?
The Agile Software Development Methodology has fundamentally changed how developers deliver working software to those who need it. This change has a ripple effect on how those who wear the business analysis hat need to work to support this evolving approach.
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.
To be effective, business and stakeholder requirements need to contain minimal ambiguity and subjectiveiy. Misunderstood requiremetns are one of the major cuases of IT project failures.
Confucius (or another one of the early Chinese geniuses) is credited with saying that a picture is worth a thousand words.
Are user requirements really necessary? You probably did not define the requirements for most of the software you use on a daily basis, so why bother?
Will Shakespeare has nothing on the intrepid business analyst.
