Avoiding Superficial Development Methodologies

Key Insight

Many development efforts fall into a 'cargo cult' trap, imitating superficial artifacts of popular methodologies without internalizing the underlying working principles. This can be seen when teams claim to use a method like Scrum but only superficially adopt elements such as daily stand-ups and iterations, often failing to achieve true agility or benefits, much like islanders building a fake airport from coconut shells and vines hoping planes will return.

The success of a development method depends heavily on context; blindly adopting policies and processes from successful companies like Spotify or Netflix without considering differences in market, constraints, expertise, organization size, management, culture, or user base is misguided. Instead of following fads, teams should pilot ideas, retain what genuinely works, and discard waste, understanding that successful companies continuously adapt their own processes. No single methodology provides a universal solution, and certification programs that emphasize memorization over adaptive problem-solving are counterproductive.

The true objective is not merely to 'do Scrum,' 'do agile,' or 'do Lean,' but to consistently deliver working software that provides new user capabilities on demand. This requires continuously shortening delivery cycles from years to months, weeks, days, and eventually to an on-demand model, enabling releases when users genuinely need them. Achieving this demands a robust infrastructure and a willingness to adapt best practices from various methodologies, while cautiously avoiding over-investment in any single one to prevent calcification and maintain adaptability.