Normal people don’t look at data just for fun; they analyze it to make business decisions. Implementing analytics in your organization is not as simple as dropping a packaged solution in place and hoping for the best. You still need requirements, just like any other project.
The strategic decisions business stakeholders make form the basis for these requirements. Using examples, let’s explore how to elicit and model business decisions, prioritize requirements, and specify business data requirements. We’ll also discuss investigating the “unknown unknowns” and using requirements to identify new possibilities in analytics.
Joy Beatty is a Vice President at Seilevel, a business analysis consulting firm whose mission is to redefine the way software requirements are created. Joy implements new methodologies that improve requirements elicitation and modeling. Her team provides assessments, mentoring, training and consulting services for companies across the US.
Joy graduated from Purdue University with Bachelors of Science degrees in both Computer Science and Mathematics, and is actively involved as a leader in the requirements community. She is on the IIBA core team writing version three of the BABOK, and also authoring sections of PMI’s new initiative for business analysis certification. She also writes about requirements methodologies in journals, white papers, and blog posts. She co-authored Visual Models for Software Requirements with Anthony Chen, and Software Requirements, 3rd Edition with famed “father of software requirements” Karl Wiegers.