Top Business Analysis Trends of 2013: Forget Consensus, it's About Collaboration and Convergence

Requirements in the form of a user story are all about the business analyst focusing on delivering convergence vs. collaboration and consensus. The new trend of collaboration and consensus is a way to get everybody on the same page, but it takes a long time to be able to get those requirements developed.

“Remember, in agile from a BA’s perspective user stories are supposed to be there to deliver value that provide a way for everybody to converge on the same path so that you can deliver every four to six weeks. That’s the package and the focus of what agile is all about,” said Nancy Yee, vice president of Global Product Strategy, ESI International,.

In 2013, Nee thinks we will begin to see that the BA’s are going to need to focus their elicitation skills more on convergence than on consensus. To get there, BAs can focus on collaboration and choosing the elicitation methods that will bring everybody into that convergence path.

Check out Nee’s full video below:

Nee is presenting a webinar next week entitled, "Developing Effective Agile Requirements." To register, click here! 

Related articles

• User Stories in Practice
• The Role of a Business Analyst in an Agile Project
• Ensuring Client Collaboration Through Agile Marketing
• Story Mapping in a Nutshell

Top Business Analysis Trends of 2013: Strong User Stories Will Drive Effective Requirements Analysis

Now more than ever, businesses of all shapes and sizes require effective business analysis to be successful in this highly competitive business world. Business analysis involves taking information gathered from a variety of sources and analyzing to forecast future trends, finding ways to make improvements in business strategies, improving operations, and making strategic decisions to improve the overall bottom line.

Moving through 2013, according to Nancy Yee, vice president of Global Product Strategy, ESI International, there are key business analysis trends that will be prominent and that businesses should embrace this year. The second significant business analysis trend of 2013 is strong user stories will be the force driving effective requirements analysis and product backlog prioritization

If the BA is already working with the product owner the BA needs go back to the roots of what they know, being able to elicit and analyze requirements in the form of a user story.

In 2013, BAs must return to the grassroots of what you know in requirements management development and get in sync with your inner elicitation and analysis requirements, focusing on the perspective of developing user stories.

“Using what you already know from an analysis standpoint, you will create successful user stories that will help your product owner prioritize their product backlog and deliver value at every iteration,” she commented.

Be sure to register for Yee’s upcoming webinar, Developing Effective Agile Requirements. Click here for more information:  http://bit.ly/10haSfj

Related articles

• Treat Technical Stories as User Stories
• Agile Scenarios and Storyboards
• Organizing Project Requirements

Top Business Analysis Trends of 2013: BA and Product Owner Roles are Solidified

Today, businesses require effective business analysis in order to be successful in a competitive business world. Business analysis involves taking information gathered from a variety of sources and analyzing to forecast future trends, find ways to make improvements in business strategies, improve businesses operations, and make smart business decisions to improve the bottom line. Understanding key marketing areas is essential to helping a business generate revenue and cut down on excess waste. 

According to Nancy Yee, vice president of Global Product Strategy, ESI International, there are some key business analysis trends that will be prominent in 2013. The first significant business analysis trend of 2013 is the roles of the BA and product owner will be solidified and respected.

In an Agile environment, the BA and the product owner have very different roles. The BA works with the product owner to identify what exactly they need, help them understand how this is going to help them achieve the values that they are looking for. The product owner, on the other hand, is responsible for understanding exactly what the business needs.

“They are there to talk about how, where and when they need to improve their businesses, which translates into the product backlog,” said Yee.

In 2013, there is going to be a stronger relationship with the product owner and the BA together in order to create a stronger foundation of understanding of what they need to be able to deliver value when it comes to priority of the product background.

Check out the full video here: 

Be sure to register for Yee’s upcoming webinar, Developing Effective Agile Requirements. Click here for more information:  http://bit.ly/ZXGbaa

Related articles

• So You Want to be a Business Analyst...Or Perhaps You Already Are (Part 1 of 3)
• The Role of a Business Analyst in an Agile Project