Archive for the ‘Sue Burk’ Category
Friday, March 16th, 2012
My experiences working with agile teams have taught me that agile analysis and testing ski
lls are truly synergestic.
So much so, that I put together a tutorial for the April 2011 Quest Conference (Quality Engineering Software & Testing) entitled, “Requirements Exploration with Tester Collaboration”. Subsequently, I had the honor to work with agile testing guru Janet Gregory to present this at Agile 2011.
Next month, EBG’er Sue Burk will co-present this tutorial with Janet at Software Testing Analysis & Review (STAR) conferences. So, you might be wondering, what are those synergies?
The Testing Mindset
Product needs evolve into requirements that define what will be built, what will be tested, and how the product needs will provide value for the organization. People with testing skills need to be involved in requirements for the same reason the other product stakeholders need to be involved: to boost the team’s ability to deliver a high-quality product. Continue reading
Tags: Agile, Agile analysis, Agile BA, Agile Business Analysis, Agile Business Analyst, agile requirements, Agile tester, Agile testing, ATDD, BDD, Business Value, collaboration, Facilitation, leadership, Planguage, Product Owner, requirements, Specification by Example, Tester Mindset
Posted in Agile, Agile Business Analysis, Agile Business Analyst, agile requirements, Agile tester, Agile Testing, Books, Business Analysis, Business Analyst, collaboration, ellen gottesdiener, mary gorman, Product Owner, requirements, roles and responsibilities, Scenarios, Specification by Example, Sue Burk | No Comments »
Thursday, February 2nd, 2012
Over the past few years, I’ve spoken to user groups to share my experiences working with use cases, scenarios, and user acceptance tests in support of data warehousing and Business Intelligence (BI) BI analysis. Afterwards, many people ask me to summarize my recommendations. In response, I wrote a short article – Requirements Tips for Data Centric Projects. You can access it here (note: you may have to register).
In my article, I focus on analyzing the context of usage. In addition, remember this: to elicit, analyze, and specify requirements in this space, almost all of the time-tested data-centric techniques are still necessary.
People often asked me for additional tips and advice. What additional considerations for business analysis for BI? Continue reading
Tags: Agile, Agile Business Analysis, Analytics, BABOK, Books, Business Analyst, Business Intelligence, Data Modeling
Posted in Agile, Agile Analytics, Analytics, BABOK, Books, Business Analysis, Business Analysis Training, Business Intelligence, Data, Data Modeling, iiba babok, Sue Burk | No Comments »
Tuesday, December 13th, 2011
Security requirements are a difficult quality attribute to elicit and specify. (Quality attributes are one the three types of nonfunctional requirements—along with interfaces, and design & implementation constraints*). Distinguishing can help. So too, it helps to
Sue Burk distinguishes between security requirements and security controls, shares four categories of security requirements, provides suggestions for eliciting security requirements, and explains why making them testable is important in her expert response. Continue reading
Tags: BABOK, Business Analyst, Business Value, Elicitation, Planguage, Quality attributes, requirements, Security Requirements
Posted in BABOK, Business Analysis, Documentation, Elicitation, iiba babok, requirements, Security Requirements, Sue Burk | No Comments »
Tuesday, June 21st, 2011
Are you working on data-centric software products? For example, ones that involves building a data warehouse, using extract-transform-load (ETL) and getting the gold—delivering business intelligence and analytic reports and queries for business decision makers?
Sue Burk shares the value of scenarios to define acceptance tests, and other practical techniques to improve your success with these data-centric projects in her expert response. Continue reading
Tags: Analytics, BABOK, Business Analyst, Business Intelligence, Data, Documentation, Elicitation, requirements, Scenarios
Posted in Analysis, Analytics, BABOK, Business Analysis, Business Intelligence, Data, Documentation, iiba babok, requirements, Scenarios, Sue Burk | No Comments »
Tuesday, March 15th, 2011
Have you been in a situation where there’s no documentation, yet you’re expected to understand functionality?
Trial transactions and observing behavior is one answer. But understanding context is also important.
Sue Burk suggests creative solutions in her expert response.
Tags: Business Analysis, Business Analyst, Documentation, Elicitation, product needs, Product requirements, Product stakeholders, requirements, Requirements Management, Software Requirements, Stakeholder Analysis
Posted in Agile, Agile Business Analysis, Business Analysis, collaboration, Discovery Workshop, Documentation, Elicitation, Elicitation Workshops, Facilitation, Process Modeling, requirements, Requirements Analysis, Stakeholder Analysis, Sue Burk, Workshops | No Comments »
