Wednesday, July 9, 2014
Are you headed to Agile 2014 this year? We are—and we are eager to introduce audiences there to our unique approach to agile requirements.
You’ll find EBG’s Nanette Brown and me speaking in the Working with Customers track, as we explore ways to discover a product’s quality attributes—things like performance, usability, robustness, and more. EBG’s VP of Quality and Delivery Mary Gorman is co-presenting with Terry Weigmann in the Testing and Quality Assurance track on the topic of test analysis and how it enables teams to strengthen and produce higher quality requirements on agile projects.
In this blog post, we want to offer you a sneak peak into these sessions, both in terms of how crucial they are for success with agile and also in regard to why they were chosen for this year’s program. Oh, and if you can’t make it to Orlando, we’ll be tweeting throughout the conference, so follow us (@ellengott, @mbgorman, @nanettebrwn) the week of July 28th! Continue reading
Sunday, April 20, 2014
Last month I presented a webinar to the PMI® (Project Management Institute) Requirements Management Community of Practice: “Do the Right Thing: Adapting Requirements Practices for Agile and Traditional Projects.”
The Requirements Management CoP has grown exponentially and will continue to do so, especially since the PMI recently announced the new Professional in Business Analysis certification (PMI-PBA). This growth was reflected in the full webinar room during the live event. During the webinar, I shared requirements discovery and delivery principles and practices along a gradient from traditional to agile.
As you review the deck, there are some key points to know: Continue reading
Friday, February 21, 2014
Whether you are agile or more traditional, your challenge is the same: In order to remain relevant in today’s market, you have to discover and deliver the right thing at the right time. To do this successfully, you need to elicit customer needs and quickly choose from among many competing voices and options to determine what is truly essential and what can wait for a future release. That means selecting the requirements development and management activities that are most effective for your particular situation–whether those practices are in your current toolbox or not.
To understand this mindset shift, it might help to think of requirements activities in terms of the ShuHaRi progression, with a learning stage (shu), a breaking away stage (ha), and a transcendent stage (ri).
Tuesday, January 28, 2014
“Fast, easy, free/cheap…” That’s what we heard about publishing an eBook edition of a paper book. After all, people said, how difficult can it be to take a PDF and make it digital? Quite difficult, actually.
Ellen Gottesdiener and I should have anticipated that publishing eBook editions of our paper book Discover To Deliver: Agile Product Planning and Analysis would be a complex endeavor. In our careers, we have been involved in re-platforming software products (applications)–and we’ve rarely encountered a re-platforming project that is straightforward. Our eBook editions were no exception.
To eBook or Not to eBook
Even before we published the paperback version of Discover To Deliver, folks requested a digital version. We analyzed the profile of our primary readers. Challenges in converting the book’s visual language, illustrations, models and examples for a virtual reading audience worried us. Other concerns included the evolving eBook industry, its splintered standards, and the end-product usability issues driven by the increasing variations in devices (tablets, readers, smartphones) on which people access books. Weighing the value proposition of paper vs. digital, we decided to initially go paper. Continue reading | 4 Comments
Tuesday, November 5, 2013
We’re launching something new at next week’s Building Business Capability Conference (BBC): An Open Jam on Agile Analysis and Product Management. Whether you are new to agile or have been on your agile journey for a while, this Open Jam offers you a chance to exchange experiences, explore new ideas, and share struggles with like-minded colleagues. The best part? You don’t have to miss the regularly scheduled sessions to attend and you suggest and participate in the topics that interest you. Let me explain. Continue reading
Wednesday, October 23, 2013
For the past several years, I have had the privilege of chairing the Agile Summit portion of the Project World/World Congress for Business Analysts. I hope you were able to join us last month in Orlando. We had a tremendous turnout and enjoyed our time learning and networking with each other.
Since then, I’ve had several requests for a summary of my half-day tutorial with Ainsley Nies, “An Agile Approach to Project and Products” as well as the Agile Summit presentation “Got Value? A Practical, Sustainable Value Model for Making Agile Product Decisions” and the track session I gave: “It’s the Goal, Not the Role: The Work of Agile Project Management and Business Analysis.” I wrote up a quick synopsis of all three, along with some suggestions that you can try in your next planning or retrospective session. Continue reading
Monday, September 9, 2013
As I prepare to deliver my tutorial (“The Essential Product Owner”) and presentation (“Product Roadmaps: Collaborating to Deliver Value”) at Product Management Festival in Zurich later this month, I wanted to share with you an excerpt of an interview with Mary Gorman and me that was recently published on their blog.
During the interview we talk about what inspired Mary and I to write our book, Discover to Deliver, what problems this book intends to solve, target audience, the background on the 7 Product Dimensions, how structured conversations are different from normal elicitation conversations, and more.
Check it out here: http://www.productmanagementfestival.com/interview-with-ellen-gottesdiener-ebg-consulting/
Friday, July 26, 2013
We talk a lot in the lean/agile community about the crucial importance of the “product owner”—the Scrum term for the person who has ultimate responsibility for the product. Indeed, this person is the champion of the product—and that’s why I prefer the role name “product champion.” You need this person for any type of product (software, system, service, or a combination) and for any context of usage (whether your product is sold commercially or is used for internal IT). Continue reading