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
Ensuring Excellence An Article by Marty Cagan www.svpg.com …in so many of the best product companies there is an additional dimension that goes beyond individual empowered product teams, and even goes beyond achieving business results. It has to do with ensuring a level of what I’ll refer to here as “excellence” although that is clearly a very ambiguous term. Over the years, this concept has been referred to by many different names, always necessarily vague, but all striving to convey the same thing: “desirability,” “aha moments,” “wow factor,” “magic experiences,” or “customer delight,” to list just a few. The concept is that an effective product that achieves results is critical, but sometimes we want to go even beyond that, to provide something special. Maybe it’s because we believe this is needed to achieve the necessary value. Maybe it’s because the company has built its brand on inspiring customers. Often this dimension shows up most clearly in product design, where functional, usable but uninspiring designs can often achieve our business results, but great design can propel us into this realm of the inspiring. Do they really need it? qualitycraftproductssoftware
Do they really need it? Does Google really need playful doodles to deliver the value they consistently provide in search results? Does Stripe really need to spend so much energy on the design of its site and SDK’s, which after all, are primarily for the developers that use their API’s? Does Apple really need to sweat the literally thousands of very subtle and often not consciously noticed interactions on its devices? On Taste