Agile Product Development

Traditional "management", even most software product management, is Industrial-Age Command-and-Control thinking that is net-negative for managing creatives. We need a re-framing of Agile Software Development with a business-building software Product Development mindset. Rapidly Iterative based on FeedBack. A bit post-Lean-Startup.

Related pages: (note they overlap and aren't fully consistent, I have to do some refactoring!)

Context/disclaimer: this focuses on internet-software products. I'm confident it scales up to 10 teams, I'm not as confident above that. Most pages are a better fit post-Product-Market Fit.

Short version

I sometimes frame this as Flow-based Product Development.


Agility, Context, and Team Agency



mimic Agile Manifesto in structure/format

inspired mainly by

The bits below which I've structured as Patterns (or Anti-Patterns) are in bold.


Mission/Vision/Lean Canvas -> Product Vision/Product Strategy (Market Segment) -> OKR (see Strategic Context)

Product Team Members Report to the Team Leader.

Development Queue driven by BottleNeck-oriented OpportunitySolutionTree.


Agility: Every team can deploy multiple times per week. Near-Continuous Delivery.


RoadMap: Project-oriented Roadmaps are counter-productive for Software Product Teams

Big Projects ("Product Projects should be Cattle, not Pets") (hah note "Pet Project" AntiPattern)

Sprints, Velocity

Matrix management

Gantt Chart

Edited:    |       |    Search Twitter for discussion