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.

(For a tangible set of practices, see my Product Development Process.)

I sometimes frame this as Flow-based Product Development.

Mindset/worldview

Agility, Context, and Team Agency

ikigai

CheckList/Manifesto

mimic Agile Manifesto in structure/format

inspired mainly by

Positive

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

Product Team Members Report to the Team Leader.

Development Queue driven by BottleNeck-oriented OpportunitySolutionTree.

Lesstimating

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

Negative

Matrix management

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

RoadMap

Gantt Chart

Sprints, Velocity


Edited:    |       |    Search Twitter for discussion