Weekend Reader, Week 46
The big news of this week is of course Microsoft open-sourcing .NET:
Microsoft commits to making .NET cross-platform and to build a stronger ecosystem by adopting open source development. They will develop completely in the open and accept commits from the community.
What does change? Some predict the death of Java… but I don't think that much will change after a short hype: Enterprises that bet on the Microsoft Stack will still use Windows, I don’t think that .NET on Linux/Mac will be a relevant scenario in the enterprise any time soon. Since VisualStudio still only runs on Windows, mainstream .NET development will still happen on Windows.
.NET for Mac Desktop, iOS or Android development will remain a niche, as it its now with Xamarin.
I guess the one place where this move makes .NET a more attractive development platform are cloud scenarios: .NET becomes a more attractive platform, when there is no vendor lock-in to Azure.
While there is a general disillusion about Scrum, the topic of scaling Scrum to the enterprise is still thriving… there must be money in that!
LeSS: Large Scale Scrum is the latest manifestation of "Enterprise Scrum” I have come across.
Welcome to the family of methodologies promising Agility to the enterprise:
- SAFe: Scaled Agile Framework
- DAD: Disciplined Agile Delivery
- Enterprise Scrum
- L.A.F.A.B.L.E: Large Agile Framework Appropriate for Big, Lumbering Enterprises
OH: “How big is that org? Small, medium, or dysfunctional?"— Rob Myers (@agilecoach) November 11, 2014
if you replace trust with process, you’ll rip the heart right out of your company
Maybe instead of focusing on how to scale Agile to the Enterprise by introducing processes and ceremonies, we should remember what Agile is all about: Its about trust!
Hierarchical coordination fails when manager decisions depend on specialist knowledge:
Often the best code you can write now is code you'll discard in a couple of years time.
Martin Fowler writes about the idea that maybe code is not meant to last. Throwing away code and rewrite applications might often be a good option. If we embrace this idea, then we should focus everything around the software delivery process to enable such rewrites efficiently. This is a radical change to the traditional approach of software creation.
The only way for businesses to consistently succeed today is to attract smart creative employees.
I see a lot of parallels with the book "The New Kingmakers"