Normal people don't look at data sets just for fun; they analyze them to make business decisions. More and more often, business analysts and product managers find themselves on strategic projects that require turning large—and often highly complex—data sets into meaningful information from which conclusive decisions and actions can be derived. In most IT organizations today, analysis of big data is a reality and will grow in significance as businesses look to better understand capturing, structuring, and learning from their data. Candase Hokanson offers advice on tackling requirements for business analytics projects. She outlines how to elicit strategic analytics decisions to help prioritize requirements work and how to prepare for the future of big data by specifying data needs. Explore examples of questions analysts can use to engage businesses to think outside the box about their requirements and consider new possibilities from analytics projects.
Candase Hokanson
.png)
Seilevel
A senior product manager at Seilevel, Candase Hokanson helps her clients clearly understand the desired business value of the projects she works on so the project team can focus on only the features/requirements that bring the most value. With this technique, Candase has cut up to 80 percent of project scope in unrelated or low priority requirements for multiple projects. She has developed requirements for a variety of products including a management accounting and profitability application for a top bank, a globally-used consolidated sales tool, and a globally-used software portal where customers can access their digital products for a multibillion dollar technology company.
Speaker Presentations
Wednesday, November 12, 2014 - 4:15pm
Business Analysis & Requirements
Big Data Business Analytics: Get Ready for Tomorrow’s Projects