Posts Tagged ‘Business Value’
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, 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 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 »
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 »
Friday, July 30th, 2010
By Mary Gorman
In my Stickyminds.com column “Playing at Work: Agile Games Deliver Value” I share game ideas and experiences – the benefits games can provide, selecting an appropriate game, facilitating a game, and designing a winning game.
Designing and Facilitating Agile Games
When writing the column I got to thinking how agile principles could provide a basis for good game design and facilitation. I reflected on a recent experience I had at Deep Agile 2010: Empowering Teams with Agile Games. Working in a small group we created a new game, tested it, and retrospected both the game and our design process in less than half a day. We consciously (and some times unconsciously!) were being agile! (To see and learn more about our game, read Michael Sahota’s summary at The Backlog Is in the Eye of the Beholder.)
Games and The Agile Manifesto
To clearly communicate the agile-ness of our work and what we learned I did a quick mapping to the Manifesto for Agile Software Development. Continue reading
Tags: Agile, Agile Business Analysis, agile manifesto, agile requirements, Agile Workshops, Business Analysis, Business Analysis Training, Business Value, collaboration, Deep Agile, Deep Agile Games, Facilitation, games, Learning, retrospectives, Workshops
Posted in Agile, agile manifesto, Analysis, Business Analysis Training, Business Value, collaboration, Deep Agile Games, Facilitation, games, Learning, mary gorman | No Comments »
Thursday, June 24th, 2010
b
y Mary Gorman and Ellen Gottesdiener
We liked it when a good thing took on a life of its own.
We learned that it really resonated with many folks.
We lacked sharing the full understanding of the technique.
We longed for more sharing.
Liked – Learned – Lacked – Longed For
At the recent Deep Agile event, Mary briefly mentioned a 3Ls’ technique she used in a recent retrospective (Liked, Lacked, Longed For). A few folks tweeted about it, and it took off in the web’o’sphere
To fulfill our longing to share and provide some background, keep reading to learn how we use this technique.
Many moons ago… Continue reading | 8 Comments
Tags: Agile, Agile Planning, Analysis, Business Analysis Training, Business Value, collaboration, Deep Agile Games, Facilitation, Learning, mary gorman, retrospectives
Posted in Agile, Agile Business Analysis, Agile Planning, agile requirements, Agile Workshops, Business Analysis, Business Analysis Training, Business Value, collaboration, Deep Agile, Deep Agile Games, Facilitation, Learning, retrospectives, Workshops | 8 Comments »
Friday, June 18th, 2010
Adult children. Jumbo shrimp. Seriously funny. I’m sure you recognize these expressions as oxymorons—self-contradictory phrases, often with an ironic meaning.
Should we add “agile requirements” to the list? Does agile development fit in with traditional requirements practices? And if so, how?
Once More into the Breach
Traditionally, defining requirements involves careful analysis and documentation and checking and rechecking for understanding. It’s a disciplined approach backed by documentation, including models and specifications. For many organizations, this means weeks or months of analysis, minimal cross-team collaboration, and reams of documentation.
In contrast, agile practices—leanLean, Sscrum, XP, FDD, crystalCrystal, and so on—involve understanding small slices of requirements and developing them with an eye toward using tests as truth. You confirm customers’ needs by showing them delivered snippets of software. Continue reading | 1 Comment
Tags: Agile, Agile Planning, agile requirements, Analysis, Business Analysis Training, Business Value, collaboration, Dependencies, Facilitation, requirements, roles and responsibilities
Posted in Agile, Agile Business Analysis, Agile Planning, agile requirements, Agile Workshops, Business Analysis, Business Analysis Training, Business Value, collaboration, Facilitation, requirements, roles and responsibilities, Workshops | 1 Comment »
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
