By Mary B. Gorman
“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.
Customer demand is a powerful force, though. Wherever we went, people would ask us when our eBook was coming out, even people who already had a paper copy of the book. We got emails from around the world asking for an e-version. After months of such requests, we decided we couldn’t put off it any longer. It was time to tackle converting our Discover to Deliver print-ready PDF.
The question was, how to begin. We felt overwhelmed by all our options and the endless string of challenges. All at once, we realized that the answer was right in front of us: Open the book and take our own advice. After all, what better way to get a handle on our project than to use Discover To Deliver’s practices and techniques?
Value Is in the Eyes of the Beholder
First step—use Discover To Deliver’s big concepts of Partners and Value. We know from experience that delivering a successful product requires a partnership. For example, the Discover To Deliver eBook product partnership included the readers (customers), the eBook development team (technology), and the authors and publishers (business).
No surprise, everyone didn’t share the same value considerations! The readers wanted an eBook edition for their existing devices, as we imaged they weren’t prepared to buy a new device just to read DtoD. The development team was invested in their current technology and methods.
From a business perspective we valued:
- Iterative development to minimize rework and control costs
- Minimum amount of our involvement in the development process
- Quick delivery and time to market
- Maximizing digital features for high eBook usability
- The integrity of the paper book’s rich visuals
Our expectation was the project would take 3-4 weeks. (Spoiler alert: It took months!)
Gaining Perspective with the 7 Product Dimensions
What at first blush appeared to be a limited, controlled scope (converting the print-ready PDF to eBook formats) was actually chock full of requirements. Here’s where Discover To Deliver’s 7 Product Dimensions saved the day, helping us to elicit and analyze the eBook requirements options. (The 7 Product Dimensions are User, Interface, Action, Data, Control, Environment, and Quality Attribute. For a quick introduction to the 7 Product Dimensions, you can view our two-minute animated video.)
Below, you can see how our eBook requirements options mapped to the 7 Product Dimensions. Notice that our typical eBook reader profile served as the basis for developing a persona of the User of our product. You can also begin to see how organizing our requirements across the Dimensions helped us balance tradeoffs. For example, analysis of the Environment Dimension’s options forced a number of tough decisions. Readers wanted support for their eBook formats and many associated releases, yet we needed to control costs and get to market as quickly as possible. Additionally, some of the book’s visual content displays better in one edition, while the other environment has more desirable navigation features that the other doesn’t support.
Exploring and evaluating the requirements within and across the 7 Product Dimensions helped pull us out of the quagmire of options and on to a successful release. We also used the 7 Product Dimensions to run our tests as we iterated through production of both book editions.
Delivered by Discovery
Our experience creating the eBook editions of Discover to Deliver was definitely not as fast, nor as easy, as advertised. The 7 Product Dimensions helped us look at the effort holistically and enabled us to make decisions based on value. Ellen and I are pleased with the final DtoD eBook editions. But of course the most valuable feedback will come from readers like you.
Topics: 7 Product Dimensions, Agile Planning, agile requirements, Agile Workshops, Books, Discover to Deliver, eBook, ellen gottesdiener, mary gorman, Value Considerations