Archive for the ‘requirements’ Category
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 »
Friday, November 18th, 2011
I’m pleased to share my podcast with Jochen (Joe) Krebs*, Founder of Agile NYC. The podcast was recorded on October 11, 2011, just before my presentation to the Agile NYC group.
The presentation, entitled, Power Up Your Agile Planning and Analysis:
Deliver Value via Structured Conversations describes how product stakeholders partner to develop a shared understanding of the product needs. I discuss how the partners gain a focused yet holistic understanding of the highest-value requirements and plan the project so that the delivery team builds the right product, at the right time. Continue reading
Tags: Agile, Agile Business Analysis, Agile Planning, agile requirements, Business Value, Elicitation, product needs, Product Partnership, Product stakeholders, requirements, Stakeholder Analysis, Stakeholders, Structured Conversation
Posted in Agile, Agile Business Analysis, Agile Business Analyst, Agile Planning, agile requirements, Agile Workshops, Analysis, collaboration, Discovery Workshop, Elicitation, Elicitation Workshops, ellen gottesdiener, Facilitation, lean, mary gorman, Product Partnership, requirements, Stakeholder Analysis, Stakeholders, Structured Conversation, Workshops | No Comments »
Wednesday, October 26th, 2011
I’m honored to share my podcast with Yaaqub (Yamo) Mohamed of The BACoach. We discuss ingredients for effective requirements workshops described in my first book, Requirements by Collaboration: Workshops for Defining Needs.
Tags: Agile, Agile Business Analysis, agile requirements, agile team, BABOK, Books, Business Analyst, Business Value, collaboration, Elicitation, Facilitation, requirements
Posted in Agile, Agile Business Analysis, Agile Business Analyst, agile manifesto, Agile Planning, agile requirements, Agile Workshops, Analysis, Books, Business Analysis, collaboration, Communication Skills, Discovery Workshop, Elicitation, Elicitation Workshops, ellen gottesdiener, Facilitation, requirements, Requirements by Collaboration, Workshops | No Comments »
Tuesday, September 6th, 2011
The tenth anniversary of the international Agile 20xx conference, Agile 2011, returned to its inaugural location, Salt Lake City, Utah. The attendance set a record for being the largest agile conference in the world! This year’s conference, held August 9-12 2011, was attended by 1,600+ people. It was jam-packed with morning-to-night activities. The conference also included events to reflect and celebrate on the 10th anniversary of the Agile Manifesto.
We at EBG Consulting were pleased to have been selected (from over 900 submissions) to present three sessions. Here are some of highlights and trends: 
Tags: Agile, Agile Business Analysis, agile requirements, Business Rules, Product Partnership, Product stakeholders, requirements, Structured Conversation, Tester Mindset
Posted in Agile, Agile Business Analysis, agile manifesto, Agile Workshops, Analysis, Business Analysis, Business rules, collaboration, Continuous delivery, ellen gottesdiener, lean, Lean startup, mary gorman, Product Partnership, requirements, Structured Conversation, Tester Mindset | No Comments »
Tuesday, August 23rd, 2011
I’m pleased to share with you an “author cast,” a podcast interview of me by Yaaqub (Yamo) Mohamed of The BACoach.
Yamo’s interview got me thinking and reflecting on my own professional learning journey and dig into the two books I’ve written (so far 
). Continue reading | 1 Comment
Tags: Agile BA, Agile Business Analysis, agile requirements, Books, Business Value, Elicitation, Product Owner, requirements, Workshops, Writing
Posted in Agile, Agile Business Analysis, Agile Business Analyst, agile requirements, Agile Workshops, Analysis, Books, collaboration, Communication Skills, Discovery Workshop, Elicitation, ellen gottesdiener, Facilitation, leadership, lean, Learning, requirements, Requirements by Collaboration, retrospectives, The Software Requirements Memory Jogger, Workshops, Writing | 1 Comment »
Thursday, July 14th, 2011
I’m thrilled to be collaborating with Janet Gregory, co-author with Lisa Crispin of Agile Testing, on a workshop entitled “Agile Requirements Exploration with Tester Collaboration” at Agile 2011 Conference and STARWEST.
I believe that there is a lot of cross-fertilization benefit to be gained when people with skills in different disciplines collaborate closely toward shared ends. This is very true for the disciplines of testing and business analysis. The tester mind-set is crucial for verifying requirements. The business analysis mind-set is crucial for validating requirements. Continue reading | 1 Comment
Tags: Agile, Agile BA, Agile Business Analysis, Agile Business Analyst, agile requirements, agile team, Business Analyst, Business Value, Elicitation, product needs, Product Owner, Requirements by Example, Scenarios, Specification by Example, Structured Conversation, Tester Mindset
Posted in Agile, Agile Business Analysis, Agile Business Analyst, agile requirements, collaboration, Elicitation, Elicitation Workshops, ellen gottesdiener, Facilitation, iiba babok, Product Owner, Product Partnership, requirements, Structured Conversation, Tester Mindset | 1 Comment »
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, June 7th, 2011
I was recently interviewed by SearchSoftwareQuality editor Yvette Francino about this week’s Business Analysis and Requirements Workshop at the Better Conference/Development Conference this week in Las Vegas, Nevada (6-7 June, 2011).
Yvette asked me to explain the logistics, if we would be emulating gathering requirements for a particular project and if the workshop be relevant regardless of domain area. Here are my answers: As conference chair, Continue reading | 1 Comment
Tags: Agile, Agile BA, Agile Business Analysis, Agile Business Analyst, agile requirements, BABOK, Business Analyst, business analysts role, Business Value, Documentation, Elicitation, Product Owner, requirements, Stakeholder Analysis, Stakeholders
Posted in Agile, Agile Business Analysis, Agile Business Analyst, agile requirements, Agile Workshops, Analysis, BABOK, Business Analysis, Business Analysis Training, Business Analyst, Business Value, collaboration, Communication Skills, Documentation, Elicitation, ellen gottesdiener, Facilitation, iiba babok, lean, Learning, requirements, retrospectives, Stakeholder Analysis, Stakeholders, Waste, Workshops | 1 Comment »
Saturday, May 14th, 2011
In a prior blog post, you learned about the in-progress book Mary Gorman and I are writing. We are thrilled to have our workshop proposal for the Agile 2011 Conference accepted. The workshop will incorporates elements of our book. Here’s our YouTube video on The Product Partnership submission. Continue reading | 1 Comment
Tags: Agile 2011, Agile BA, Agile Business Analysis, Agile Business Analyst, Agile Planning, agile requirements, agile team, Books, buisness analyst, Elicitation, product needs, Product Partnership, Product stakeholders, requirements, Stakeholders, Structured Conversation
Posted in Agile, Agile analysis, Agile Business Analysis, Agile Planning, agile requirements, Agile Workshops, Books, Business Analysis Training, Business Value, collaboration, Discovery Workshop, Elicitation, Elicitation Workshops, Facilitation, mary gorman, Product Partnership, requirements, Structured Conversation, Workshops | 1 Comment »
Thursday, April 7th, 2011
By Ellen Gottesdiener and Mary Gorman
In September 1977, the TV sitcom Happy Days had über-hip Fonzie, clad in leather jacket and swimshorts, water ski over a shark to prove his mettle—and at that moment even diehard fans knew that the show was past its prime. They were right. After that episode, ratings plummeted, and the expression “Jumping the Shark” was born. When a TV show, or anything else, jumps the shark, you know it’s on its way out.
Our question this month: have any of your software development practices jumped the shark?
For example, are there boundaries around people’s roles? Some organizations tend to confine people to roles such as developer, architect… Continue reading
Tags: Agile, agile team, Business Value, Documentation, leadership, product needs, Product Partnership, Product stakeholders, requirements, retrospectives, Stakeholders
Posted in Agile, Agile Business Analysis, Agile Business Analysis Flow, Agile Business Analyst, agile games, agile manifesto, Business Analysis, Business Value, collaboration, Communication Skills, Documentation, ellen gottesdiener, heavyweight team, leadership, lean, mary gorman, Product Partnership, requirements, retrospectives, roles and responsibilities, Stakeholders, Waste | No Comments »
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
