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
Why Scrum is killing your product An Article by Henry Latham uxdesign.cc Product owner vs. product managerWe optimize what we measure Beware SAFe, an Unholy Incarnation of Darkness agilemanagementsoftwareproducts
Product owner vs. product manager A Product Owner is focused on output i.e. how quickly can we build these features? Product Management, on the other hand, is focused on outcomes i.e. why are we building these features in the first place? agileproducts
We optimize what we measure Scrum does not say “only focus on output”, but, unfortunately, humans will optimize for what they measure. If you worry about story points & hitting your estimations, that’s what is going to consume your attention. That is what you and your team will optimize for. And that is the core critique of Scrum as it is practiced: That it focuses a product team’s attention so heavily on delivery — on building lots of features quickly & efficiently — that teams fail to focus on spending time to discover what the right thing to build is. optimizationagilefeatures