Requirement engineering

Requirements engineering is a systematic and disciplined approach to identify, specify and manage requirements with the following goals:

1. Understanding and documenting the stakeholders’ desires and needs, specifying and managing requirements to minimize the risk of delivering a system that does not meet the stakeholders’ desires and needs.

2. Knowing relevant requirements, achieving a consensus among the stakeholders about them, documenting them according to given standards and managing them systematically.

Requirements engineers analyze and synthesize information provided by customers, staff, IT professionals and executives. They elicit the actual needs of stakeholders, not simply capture their expressed desires. Requirements engineering activities may be performed in many job titles or organizational roles.

Requirements engineering practitioners include requirements engineers, business systems analysts, systems analysts, product managers, product owners, enterprise analysts, business architects, management consultants and interaction design professionals.
Need for good requirements engineering
As per a study by TechRepublic (http://www.techrepublic.com/blog/tech-decision-maker/study-68-percent-of-it-projects-fail/), it is estimated that around 68% of projects fail due to poor requirements engineering. Majority of customer expectation mismatches can be attributed to poor requirements.

Hence, it is extremely essential that we focus on identifying and documenting complete requirements for all projects.
As per the TechRepublic study mentioned above, two third of system errors in production are due to requirements errors.
Developers develop solutions as per their understanding of requirements. Unclear, incomplete, or wrong requirements lead to development of wrong solutions.
Complete and correct requirements are the basis for successful system development. Discovering gaps in requirements early avoids tedious change control processes.

Business analysis estimation – Theory vs. Practice

 

 Business analysis estimation is a bit of a strange topic for most BAs. We do study 8 to 10 techniques mentioned in various sources. Most common techniques mentioned are: Top-down estimation Estimate efforts for components using hierarchical breakdown. Typically done when the budget is fixed. Bottom-up estimation Uses WBS to estimate deliverables, activities, tasks, and …

Business analysis estimation – Theory vs. Practice Read More »

Business analysts – How to learn a new domain in less than 30 Days

 

 Business analysts – How to learn a new domain in less than 30 Days I had a very Interesting experience in my Business Analysts consulting career. About 7 years back, I was conducting a public workshop on business analysis. 2 managers from a large multinational corporation attended the BA workshop.  After about a week, one …

Business analysts – How to learn a new domain in less than 30 Days Read More »

10 Never Miss Sources of Requirements

 

 10 Never Miss Sources of Requirements Let me describe a very interesting situation that happened to one of our projects.  We were modernizing one of our legacy systems developed 15 years back. The system could not fulfill changing business needs and was expensive to maintain. Our system was supposed to handle requests which were originating …

10 Never Miss Sources of Requirements Read More »

100 Re-usable Requirements for Most Enterprises

 

  All of us realize the value of re-use. Re-use saves cost and improves quality.   But when it comes to reusing requirements, I hardly hear any organization making a planned effort to re-use requirements.   In this regard, I felt, let us start with set of requirements which are highly likely to be re-used. …

100 Re-usable Requirements for Most Enterprises Read More »

5 Brain Twisters for Expert Agile BAs

 

 Over the last two decades, most organizations have moved away from the waterfall approach to the Agile approach. The agile approach allows us to develop things in an incremental way, allows us to experiment and seek constant feedback from our stakeholders. Agile business analysis is definitely a quite interesting topic to discuss.   Let me …

5 Brain Twisters for Expert Agile BAs Read More »

Smart way to manage parallel operations during system transition

 

   When new systems get deployed in any organization, we continue to operate both new system and old system together for some period. Sometimes, this could be a year.   Now if we ask end users to enter data on both system, it is going to cause huge dissatisfaction. This also is clearly a non-value …

Smart way to manage parallel operations during system transition Read More »

How to make a 46 year old lady look like 16

 

   Just to clarify, this article is all about business analysis. I am still a practicing BA and I have not changed my profession.   2nd point – Please do not make it a gender issue – we men would also like to look younger.   Now you must be wondering how this article relates …

How to make a 46 year old lady look like 16 Read More »

Stakeholder groups vs. UN Security Council – What’s the commonalities?

 

    You must be wondering how can there be any similarity between our stakeholder groups and UN security council?   Indeed there exists a beautiful co-relation.   United Nations as a well-known organization to which most sovereign countries are member nations.   However, 5 countries (US, UK, China, Russia and France) are permanent members …

Stakeholder groups vs. UN Security Council – What’s the commonalities? Read More »

Scroll to Top

Please furnish the following details for us to provide a budgetary quote

 

CBAP CCBA ECBA AAC CPRE