Yagni A Definition by Martin Fowler martinfowler.com Yagni originally is an acronym that stands for "You Aren't Gonna Need It". It is a mantra from Extreme Programming that's often used generally in agile software teams. It's a statement that some capability we presume our software needs in the future should not be built now because "you aren't gonna need it". A late change in requirements is a competitive advantageRequirements proliferation softwareagilefeaturesplanning
The State of Agile Software in 2018 A Talk by Martin Fowler martinfowler.com On the surface, the world of agile software development is bright, since it is now mainstream. But the reality is troubling, because much of what is done is faux-agile, disregarding agile's values and principles. The three main challenges we should focus on are: fighting the Agile Industrial Complex and its habit of imposing process upon teams, raising the importance of technical excellence, and organizing our teams around products (rather than projects). How we can do betterTaylorism in software A late change in requirements is a competitive advantageMake the change easy agilesoftware
Narrative Strategy An Article by Tom Critchlow tomcritchlow.com An unfolding network of associations
An unfolding network of associations We know strategy is an unfolding network of associations: The evidence from the case suggests that the concept of strategy can be reappraised. From strategy as a static set of choices made at a specific point in time to strategy as an unfolding network of people, shared experiences and artifacts that is constantly being remade. And we know that only 30% of employees can articulate a company’s strategy. And I believe in the hyper-connected age we live in both of these things are becoming more true - that strategy is increasingly “in motion” and that most organizations are realizing their OODA loops are too slow for the modern world. This causes the articulation of strategy to stall and get left behind - how do you articulate something in motion? It’s easier to write strategy down when it doesn’t change right? As a result - there’s a widening gap between the perspective on strategy that the executive team has and the received ideas of the company’s direction that teams and employees have. work