This Agile Method GUARANTEES Results

[@MikeStock88]

Totally agree I cannot imagine developing software without agile, not the process the concept I think how badly most companies implemented and still implement agile shows they don't understand why agile works We should work like startups, keep iterating an idea and stop if it's either not financially valuable to improve or its finished

[@MikeStock88]

@pm4rcin Nornally if that happens it's a failure of planning or they gave the employees an impossible task If you Always deliver customer value each time, it's usually the best possible job you could have done Anything else is unicorn thinking

[@Sergio_Loureiro]

Dave Farley never disappoints in his channel. Everything I see here I put a like. I wish I knew about this goldmine before.

[@gewusst-vim9583]

Just continued to read the book "the beginning of Infinity" (btw. Many thanks for the recommendation in one of your older videos) chapter "dream of sokrates". Then i watched this new video about modern software development in a iterative way... ...and I'm really thrilled that the mindset of both stories/ideas is very much the same. It's like using waterfall is a little bit like the culture of the Spartans. "Knowing" everything from the beginning, no self criticism, no way of changing the direction. While continuous delivery is more like the Athenes. Searching for knowledge, always knowing that there are mistakes in the current wisdom. But iterative finding some of the issues and improving the knowledge.

[@mikemegalodon2114]

what a coincidence, I'm also reading Beginning of infinity now and just wanted to watch another great video from Dave! have a nice time of the day everyone :)

[@JayJay-ki4mi]

I want to read it now.

[@dlabor1965]

I'm reading "Modern Software Engineering -- Doing What Works to Build Better Software Faster" by David Farley. Like it. Next in the pipeline is "Continuous Delivery Pipelines -- How To Build Better Software Faster". Thanks, Dave!

[@SolidousMdz]

Nice tshirt.

[@addcoding8150]

I just finished reading this chapter in the book. This video is a good summary of the content and ideas in that chapter imo.

[@robwatson826]

Fantastic t-shirt Dave! Oh, and good video as well - always interesting hearing your thoughts and ideas

[@jukkanikki3395]

Thanks. Great closing sentence.

[@kikyadryan1625]

Great Video Dave ! Next event storming please :)

[@MrStefanica]

Totally agree! Iteration is the mother of evolution :-) ! Thanks Dave! Very useful, as always... Keep on the very good work !

[@ContinuousDelivery]

Thanks, will do!

[@1981ilyha]

Thank you for these very simple things, that are suddenly very hard to accept.

[@dinoscheidt]

Yup. And all of them result in „no, I don‘t have a 🔮“ conversations with - management, clients, founders, users, ourselves….

[@martinnyolt173]

Great video that hits the nail. With that learning and iteration in mind, what's your stance on the statement "developers don't write user stories"? I love all of your content, keep up the great work!

[@ContinuousDelivery]

I think that's wrong. I think developers should create stories when they see gaps, or come up with good ideas.

[@Bisadi]

Food for thought: I think fitness defines the goal. We must stop the process if the product is perfectly fit even thou it is not the same as the goal. In other words, there shouldn’t be a final goal or destination as illustrated to be changed midway.

[@ContinuousDelivery]

Yes, fair comment!

[@andrewharpin6749]

Good video, but [Pedant mode] it's kw, not kwh, charge rate is measured in kw, kwh is used as a measure of battery capacity (even though it is not wholly accurate) [/Pedant mode]

[@ContinuousDelivery]

Yup, I misspoke and then compounded the mistake by repeating it in the text in the video.

[@alexandrutoma9187]

You are very good sir ! Your videos bring a lot of value to the community .

[@ContinuousDelivery]

Thank you.

[@jimiscott]

Just read the chapter!

[@jacmkno5019]

Linode! That's good company dude....

[@smid5y]

Is there a source for the "two thirds of ideas produce zero value" quote?

[@ContinuousDelivery]

Sure, here it is: ai.stanford.edu/~ronnyk/2013%20controlledExperimentsAtScale.pdf

[@Sergio_Loureiro]

In the case of Skype, nearly 100% of ideas Microsoft had on it returned zero value.

[@M0rd7ust]

Well, are _you_ embracing change? You better be because the video contains a bug or two. ;-) Charging power is measured in kW, not in kwh. The 250 kW charge rate is only the _peak_ rate under ideal conditions, the user-relevant _mean_ rate is much lower.

[@ContinuousDelivery]

Thank you for the feedback.

[@LPFan33]

I brought it up to the product owner and he has neatly thrown your suggestion onto the "nice to have" pile, you know, the one that is rotting away somewhere in the corner. Thanks for the feedback!

[@justintomlinson9311]

yields (measurable) results. ;^) - Nice thanks Dave

[@ericblankenburg]

Unfortunately, in today's offshoring model the offshore teams often want all of the requirements, architectural designs, and technology choices made upfront and backed up with voluminous documentation before development will start. Then they might use sprints to develop the software, but that's not really Agile. I've run across this at two different companies over the last several years. In both cases, the results were not good.

[@ContinuousDelivery]

Yes, and this is the one of the key reasons that this didn't work out well in the examples that you saw. It doesn't work out well as long as it is structured as you describe. I agree that this is how many firms organise things, but they are wrong when they do.

[@martinbakker7615]

KWh is not a rate ,it is an amount.

[@ContinuousDelivery]

Yes, I miss-spoke, then we copied what I said in the graphics, sorry for the mistake.

[@adambickford8720]

If you're 5x smarter but I can iterate 10x faster i'll still be twice as valuable to the company... AND the jr devs understand my solution ;)

[@philthompson2239]

I disagree, you will just produce far more code that I, as the smart one, will bin later... Every iteration in the wrong direction has no value at all. You cant equate code quantity to code quality.

[@adambickford8720]

​@@philthompson2239 Who said more code? It'll just take more iterations to reach an acceptable solution that doesn't require a savant to maintain. Given you missed the entire point your self compliment of 'as the smart one' is pretty suspect.

[@philthompson2239]

@@adambickford8720 your comment placed you in the role of 10x producer, I merely assumed the other role to illustrate an alternative view of your assertion that iteration count is more valuable than intelligence. A point that you entirely missed. Then you reply with personal insults while not refuting the point at all. You did, however, remind me why I stopped participating in these sorts of discussions with peers. Its a pointless exercise so I will bid you farewell.

[@adambickford8720]

@@philthompson2239 I did not, they are all relative values meant to illustrate the power and value of fast iteration and short feedback loops. We might be duking it out for the bottom 2 producers in the org, only one is half the value of the other. It's not the flexing contest you seem bent on winning. The entire point is no matter your ability level the ability to iterate quickly will lead you to better designs and higher productivity. It can actually be a great asset to the less innately gifted and of enormous value in large teams of disparate abilities. I can't make you smarter but I can make you more efficient. I refuse to believe you're unaware of your aggressive tone. I hope you feel as foolish as you look trying to 'take the high road' now.

[@brownhorsesoftware3605]

Writing is revision.

[@BorisGligorijevic]

Great videos, but your fascination with Tesla / Musk is not justified. There are many, many better tech companies, the quality of Tesla‘s cars, their tech and the processes is way overhyped. Musk is just a good salesman.

[@ContinuousDelivery]

Sure he's a good salesman, but his companies practise and demonstrate the principles that I discuss and, wether you like Musk or not, they do push the boundaries of engineering, so I think they are a fair, and good example.