Thursday, May 9, 2013
Recently I worked with a project team developing a software product under grant from four entities, with a government agency as their ultimate customer. They called me in because, three months into a four-month project, they were desperately behind. Why? They’d been spinning in circles, trying to satisfy diverse stakeholders who had overlapping as well as conflicting requirements. The funding was split among several competitors, each with its own competencies, and there was a sense that the government agency was playing favorites based on its own preferences in the domain. Continue reading
Saturday, April 13, 2013
Curated by Ellen Gottesdiener
The twitter-verse was recently ablaze with an informal playful contest: rename well-known movies using common agile terms and expressions (see my short list of those terms, below*).
It’s the month of and for April Fools, so join me for some fun.
I’ve assembled the best of the best of “agile movie” – with credit to its originator (and his or her twitter handle). Continue reading | 1 Comment
Tuesday, March 5, 2013
If you’re on a team that’s transitioning to lean/agile, have you experienced troubling truths, baffling barriers, and veritable vexations around planning and analysis? We work with many lean/agile teams, and we’ve noted certain recurring planning and analysis pain points.
Mary Gorman and I shared our top observations in a recent webinar. Our hostess, Maureen McVey, IIBA’s Head of Learning and Development, prompted us to begin by sharing why we wrote the book Discover to Deliver: Agile Product Planning and Analysis and then explaining the essential practices you can learn by reading the book. Continue reading | 2 Comments
Wednesday, February 6, 2013
Impact Mapping: Making a Big Impact with Software Products and Projects, by Gojko Adzic, explains how to use an efficient visual modeling technique to ensure that project partners build the right products—or, as the author says, products that have impact. Impact mapping, the subject of this lithe, approachable book, is an adaptation of visual mapping techniques (effect mapping). Continue reading
Monday, January 7, 2013
I love books, and I read a lot of them.
Books help me learn about new tools and techniques to add to my toolkit. I also read books to reinforce and confirm practices that work, to challenge my thinking, and to discover new colleagues to connect with.
The problem? So many books, so little time. So I’ve curated a short list of five 2012 lean/agile books that I’ve found valuable, challenging, and useful.
[Oh… and did I mention my own new book, written with Mary Gorman: Discover to Deliver: Agile Product Planning and Analysis. ] Continue reading
Sunday, December 9, 2012
By Mary Gorman and Ellen Gottesdiener
In our book Discover to Deliver: Agile Product Planning and Analysis we discuss the usefulness of the “Given-When-Then” technique to explore (discover) and confirm (validate) product options. Here we summarize the technique*, brainchild of Dan North.
What it Is
Given-When-Then (GWT) is a structured format for expressing scenarios with example data, including pre- and post-conditions.
GWT helps project stakeholders (business, customer and technology partners) communicate using business domain language. You can use GWT to explore product options and confirm selected options and confirm selected options, in a concrete, tangible way. Often called “specification by example,” GWT provides living documentation for your delivered product. It simultaneously specifies requirements while identifying acceptance tests, thereby streamlining discovery and delivery. Continue reading | 8 Comments
Sunday, November 18, 2012
It continues to baffle me.
Clients share their struggles managing three, four, or five different product owners (or, as we refer to them, product champions). Delivery teams end up abandoning deployable software right before the end of an iteration or release.
It’s because the product champions can’t agree among themselves, or with the delivery team, on what to ship. As a result, the team members spend too much time in ineffective meetings and not enough time building high-quality software that delivers value. Continue reading
Tuesday, November 6, 2012
In October, we wrote about big concepts for delivering an ever-evolving, high-value product. These Agile/Lean concepts are used in your daily work to rapidly discover product needs and deliver valued products:
* The Product, and the 7 Product Dimensions
* The Structured Conversation metaphor (explore-evaluate-confirm)
* Product Partners
* Planning Views
Tuesday, October 23, 2012
How do you rapidly discover product needs and create a practical plan for delivering high-value products? How do the people on your product development team collaborate as partners to explore and evaluate which work to deliver next? How do you confirm that you’re building the right product in the first place? How do you incorporate Agile/Lean practices into your daily work?
Our newly released book, Discover to Deliver: Agile Product Planning and Analysis (two years in the writing) addresses these tough questions.
Here’s a quick tour of the big concepts. Continue reading
Tuesday, September 25, 2012
by Mary Gorman and Ellen Gottesdiener
We are pleased to announce our book Discover to Deliver: Agile Product Planning and Analysis is now available.
Discover to Deliver provides the essential planning and analysis practices you need to collaboratively deliver high-valued products. It gives you a visual language to streamline and simplify your planning and analysis. You and your team get practical guidance in how to collaborate continually to discover and deliver an evolving product. Continue reading | 4 Comments