Beyond programming

Most of us would agree that every project has requirements. Every time a new software application is being developed there is always a ‘Business Analyst’ (BA) from the project team who performs the role of requirements gathering for every software project. While some requirements are crucial to the application others are considered to be gold-plated luxuries.

How do we determine that the approach being adopted to gather the requirements is accepted as a good practice? What makes an individual a successful BA who not only understands the business problems but also models a solution which can be effectively leveraged through the use of technology?

How can one be assured that a BA is given the power of execution to get the things delivered with a benchmark of quality and within the defined time frames? Here are some of key pointers which are essential for business analysis.

Who gathers project requirements

While determining the project requirements one needs to identify at the beginning of the project who would be taking the ownership for capturing the project requirements.

Today, many software developers do perform the role of a BA. The technical discussion coupled with absence of soft skills and business acumen can dilute the interest levels of the customer and result in total disconnect.

To read the full article, click here...
To read the ePaper, visit: http://emagazine.managementnext.com