When introducing the Manifesto to new Agile practitioners, its outdated language often got in the way of conversations around more interesting points. So I’ve freshened it up taking inspiration from Kent Beck (talk ‘Beyond Agile Programming’ at Startup Lessons Learned Conference, 2010), Dan North (talk ‘Agile Revisited’ at GOTO conference, 2015) and Joseph Pelrine (ebook on Agile teams and self-organising systems, 2011).
The three pillars of Agile answer briefly and clearly two of the most important questions people are asking since the beginning of Agile and before: “Why Agile works?” and “What’s the essence of Agile?”
Nowadays challenges span complicated and complex situations that require a leadership style and tools that go beyond traditional leadership.
Here you find reading suggestions to find inspiration as well as practical advice.
#Agile #Lean #Leadership
What is lean-agile coaching? Let’s find out with the two “equations” at its root.
A flawed idea, from a big consulting company, is a poisoned seed that once planted in the mind of inexperienced practitioners can spread misinformation and distort people’s understanding.
Let’s turn this poisoned seed into an opportunity to reflect on the foundations of lean and agile, and deepen our understanding.
You are trapped in the black and white room of agile’s rainbow. And you cannot be sure you are not, until you find out and conquer your qualia.
Given the complex nature of the problems we try to solve and the solutions we try to envision, there’s no surprise the devil is in the details.
Sometimes we have to be highly intelligent and well-informed just to be undecided about them.
These seven principles are seven chances to spot the complexity hidden in the details.
You often think there must be a better way of getting stuff done,
while at work you spend your time working around obstacles created by the very same processes put there to help you. Meanwhile, you build meaningful relationships, based on professional respect and trust, that span well over the boundaries of the formal hierarchy.
These books are for you.
#CodeQuality: a definition unknown or misunderstood by most, that goes beyond #SoftwareCraftsmanship.
Given that software is eating the world and IT *is* becoming the business, it do matters.
This post gives a pragmatic definition valuable and meaningful for both IT and the business.
This post explores the skills that make a great CTO. It also provides a tool to self-assess current strengths as CTO, and identify areas that can be targeted next for improvement.
What are the fundamental building blocks of software development done right? Are you observing them? Check with this booklet that includes references to conclusive scientific research studies, and industry opinion.