Career Store Research Materials Training Community Register Sign In

Our mission is to strengthen the careers of software leaders by sharing as much software management theory, research and knowledge as humanly possible. We encourage you to join the mission by using our materials for personal growth, sharing among friends, and mentoring within your company; however, commercial training use must be licensed.

Our Funding model is to: provide certification and live training services as desired and requested by our community. We do this so that our staff can buy pop tarts, pay their bills, and produce more career boosting content, research and tools.

We require that our copyright notices are left in place.

Classically Coerced Project Execution

Classically Coerced Project Execution. Mandates come from desperate executives attempting to hit revenue targets without respect to current project loading, demanding new product in a compressed timeframe:
Strong Attractors are replaced by Executive Man[date]s 
Project Management empowered to drive date
Timeline is re-estimated until it matches desired date
Strong Deterrents push team to hit Delivery Date
Intangible constraints that gate monetization are quietly ignored in order to hit date without working excessive nights and weekends
Quality, Stability and Scaling are Deferred
Discovery, Creativity, Truth, and Dissent are Squashed
The Project is birthed to the slave gallery cadence of: PLAN, Plan, plan, Status, Status, Status, date, Date, DATE!
Technical Debt is accumulated and, instead of monetization, you get an emergency mitigation plan, ironically characterized by reactive characterization with a highly constrained attempt to address neglected constraints
.

Click slide to see in context of slide deck