product development

Books, MPD

Beware of Scams for Writing and Otherwise

While a pandemic might bring out the best and the worst of us, scams persist. I received an email this morning from a so-called “self-publishing” company. They are quite happy to help me get my book to traditional publishers. They didn’t say what it would cost, but they wanted the pdf of the interior and

MPD, project management

Create & Manage the Project’s Bounds, Part 1

Do you know your project’s bounds? Do you know what your sponsors want from your project? For many years, I heard about the “iron triangle.” Sometimes, the triangle was “Scope, Quality, Cost.” Sometimes, it was “Scope, Date, Cost.” It was always three things out of a minimum of four possibilities. I never saw a triangle

Books, MPD

Announcement: Conference Proposal Book is Available

I’m delighted to announce I published the Conference Proposal book! I collated all the conference proposal posts into a book. And, I added more content only available in the book. The book is through copyediting. You can buy it on Leanpub now in all electronic forms. Yes, I will upload the book to all the

agile, MPD

Create Feedback Loops (Agile Approaches) for Hardware Products

In Costs of an Agile Approach for Hardware Products, I suggested that an iteration-based approach for hardware was too expensive. I focused on the actual development costs. Let me talk a little about the team and alternatives here. What Does a Hardware Team Look Like? Agile software teams are cross-functional and interdependent. The team is

agile, MPD

Costs of an Agile Approach for Hardware Products

I had a conversation with a hardware engineer whose organization got the mandate, “Go agile or bust!” They’re attempting to manage their technical and schedule risk with two-week iterations. And, they’re trying to show finished product, not simulations. And, even though they work independently, they’re supposed to have a standup every day. None of that makes

MPD, product ownership

Minimum Requirements Documentation: A Matter of Context

A colleague asked me about the kinds of documentation the team might need for their stories. He wanted to know what a large geographically distributed team might do. What was reasonable for the stories, the epics, and the roadmap? How little could they do for requirements documentation? I start with the pattern of Card, Conversation,

Scroll to Top