Wonderful Existence

Is this what I leave behind? A broken systemic cycle that perpetuates those at the bottom will stay at the bottom. Feeding a time machine where every moment is accounted for, but that no longer keeps…

Smartphone

独家优惠奖金 100% 高达 1 BTC + 180 免费旋转




Agile Development and the role of a Business Analyst

Business Analysts are a vital part of any agile team. They liaison with all the key project stakeholders and help projects run smoothly in an agile environment.

Business Analysts facilitate dialogue about the customer value with the team, prioritize the key slices of value and help the agile teams embrace the value-driven development of the product. At the end of the day delivering a product that fulfill all the customer needs and is built in a timely fashion.

Agile embraces change and BA’s (Business Analysts) bakes agility into the product development cycle ensuring a smooth flow of product development.
BA’s also helps in making the product owners role more efficient and reliable. A BA analyzes product owner priorities and works to decompose them into small pieces. Each piece delivers value to the customer and is small enough to be accurately estimated.

BA’s initiate correct conversations to get the correct understanding of the requirements. One way an agile BA differs from traditional BA is that agile BA does not work on detailed requirement analysis document. Something that people coming from traditional waterfall method of development finds extremely odd. The truth is we all live in an agile environment and requirements of the business keeps on changing with the changing environment, the waterfall model was static, clunky, slow and it often missed out on a lot of requirements. Still, the use case of waterfall mode should not be entirely ruled out, there are situations where waterfall model suites well than the agile model and sometimes even a hybrid approach turns out to be the best-desired model.

Not having a detailed requirement analysis document does not means that there is no documentation but rather the documentation is of different kind. It serves as a communication ignitor or a record of a conversation, instead of having detailed diagrams the BA’s usually takes the photographs of the whiteboard directly, record key points of the conversation or just write down key questions. Approach differs from BA to BA but one thing is common not a lot of time is spent on creating and managing a requirements document.

Add a comment

Related posts:

A fine corsa

Un effetto che lascia a bocca asciutta nonostante il tutto sia comunque chiaro. E la fine del periodo estivo è un po’ questo. In città c’era la solita calura di giugno quando abbiamo buttato fuori il…

Fashion Buyer.

Fashion tells our story. It gives us a creative outlet where we are able to express ourselves through our clothes in order to contribute to an extension of who we are. It’s a magical, extravagant…

The Reasons Why Gamification Works

It seems that in the past few years every company that has an app or is looking into including one into their business strategy has only one word in mind — gamification. The competition for mobile…