Writing Product Velocity #4. Publishing Product Velocity required balancing reputation, collaboration, and intellectual control.
Nobody gets rich publishing a technical book, and that’s not my goal here. Now that I have the first offer, I started to outline criteria that are important to me. These include:
Writing Product Velocity #1. Defining the core problem behind slow product development was harder than writing the proposal itself.
Writing Product Velocity #9. What writing the Product Velocity manuscript revealed about engineering, flow, and organizational learning.
Before Product Velocity existed, the challenge was finding language for high-velocity product development.
MIT Press was first on my list. Is it wise to send the proposal to them first, without trying some 2nd choice publishers? Too late it’s out.
Knowledge Flow #1. The first Product Velocity Mastermind showed that the bottleneck is rarely missing knowledge. The bottleneck is getting it to flow.
Writing Product Velocity #5. Why Product Velocity communicates the problem and solution more clearly than Lean Systems.
English English
German English English German