#Agile is basically project management esotericism.
The smartest people have managed to build processes on top of it that work, the same way that some churches have worthwhile charities that do good work, but that doesn't mean the core of the methodology isn't mumbo jumbo.
(ah yeah, going for both developers AND the faithful today in one fell swoop, what am I even thinking?)
every anti-agile post ever seems to go like "fuck #agile, we just need to communicate more effectively instead of blindly following this longwinded process"
Ist es nicht witzig, dass der volkswirtschaftliche Produktivitätszuwachs in den letzten 10 Jahren trotz der ganzen #Agile-Initiativen nicht einmal 1% gewesen ist?
Könnte es sein, dass das ganze Zelebrieren von #Methoden und das Hinterherhecheln nach #Innovationen vielleicht mehr Produktivität kostet als bringt?
Was wäre, wenn man Leute einfach in #Ruhe arbeiten ließe und sich keine Gedanken mehr um #Kultur macht?
If Agility is the ability to respond to changes in a meaningful way, a huge part of that consists of the time it takes until this response is in the hands of the customer so that a feedback loop can form.
If that's true, what's the value of Discovery Epics or Stories, Spikes, Dual Track whatever...
@daverooneyca and I are doing a public AMA (ask-me-anything) on all things Agile on May 1 (next week). Bring your questions and get the perspective of two coaches who each have 25+ years of experience.
As I mentioned last week, I have seen hundreds of people looking for work through LinkedIn. The post is intended to 1) help people find work that is well suited for them 2) become a place where I can add additional sources for people to read.
Every book on #agile methodology: "Story points represent complexity, not time. In fact you should probably use T-shirt sizes instead of numbers to reduce the temptation to assign time values, because associating story points with time is a very bad thing and if you do it you are not agile and might as well just be doing waterfall, you agile-hating dinosaur."
Every single agile team made of humans on planet Earth: "So, a one-point story means it should take about a day..."
Also, same company: “For our recruitment process, you will have three initial interviews, five technical interviews, a duel to first blood with HR, attempt a mind meld with a C-suite executive, present five two hour sessions to a team of 18 sharpshooters, and then if you are deemed a worthy applicant, move on to the second interview round.”
Hi folks! I have a new post up on Embracing Agility:
No Points for You!
A specific topic regarding Story Points from my AgileAI experiment was whether we should estimate work on defects & tech debt using story points. Read on to find out!
#Influence without Authority. To overcome the Endowment effect, it helps to highlight the cost of inaction. In the #Agile world, we often deal with teams that say, we too rushed or busy to improve. Consider showing them cost of not doing anything. Not refactoring and improving engineering practice? Highlight the increase of chaos in their code. Not improving flow? Consider measuring # of days items are stuck waiting to be worked on. Show the failure to act is already harming the team.