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 re-framing of Agile Software Development with a business-creating software Product Development mindset. Rapidly Iterative based on FeedBack. Part of Strategic Agility. A bit post-Lean-Startup. This is my Product Development Process.
I sometimes frame this as Flow-based Product Development.
- But that's not like Principles Of Product Development Flow, more about maximizing Flow State.
- Though there's a risk of being biased toward incrementalism within a mis-designed product focus.
- So it has to be reflective (reflective thinker).
CheckList/Manifesto
compare to Agile Manifesto?
inspired mainly by
Positive
Lean Canvas -> OKR
Product Team Members Report to the Team Leader.
Development Queue driven by BottleNeck-oriented OpportunitySolutionTree.
Continuous Discovery for OODA for Compounding value.
Every team can deploy multiple times per week. Near-Continuous Delivery.
Negative
Big Projects ("Product Projects should be Cattle, not Pets") (hah note "Pet Project" AntiPattern)
Sprints, Velocity
Edited: | Tweet this!
