Explaining Agile - Martin Fowler and Neal Ford at USI

Information and subscription on www.usievents.com
Martin Fowler is an author, speaker, IT specialist and British consultant in the conception of companies’ software. He wrote, in particular, a reference book on refactoring and co-wrote a reference book on projects planning in extreme programming with Kent Beck, creator of the method. He is a member of Agile Alliance and is the co-author of the Manifesto for Agile Software Development.
Neal Ford is a software architect at ThoughtWorks. ThoughtWorks is a global IT consultancy company specialized in end-to-end software development and delivery. Neal Ford is also the designer and developer of applications, various materials, articles, videos and author of many books.
Martin Fowler and Neal Ford tackle the following question: Why does Agile software development work so well? They provide advice and stress the importance of communication, feedback as a crucial part of software development, the importance of boosting the creativity of developers, and how introspection is essential to continually improving the project.
Follow USI on Twitter: / usievents
Follow USI on LinkedIn: linkd.in/13Ls21Y
Subscribe to our channel: bit.ly/19sPpSp
Twitter: @martinfowler

[@suer1213]

Hi, I was captivated by the great analysis Martin made bet. Predicted Planning and Adaptive Planning. I enjoyed the first segment of Martin's talk but had few questions/concerns about the ThoghtWork's approaches due to the following points made during the talk: 1. use of elec. tool to see the task board when the team is not co-located. Yes, it is good to know that they utilize the board but shouldn't Thoughtwork help the organization setup so that team is co-located thus eliminating the use of electronic board. I believed in each team being co-located but cross-teams can be distributed. 2. In my experience, tech people love tools. so, I often find it that team members don't like using PostIts - physical board. so, i am puzzled by his remark that teams love the physical board. 3. Pair-Programming - perhaps different activities stimulate a different part of brain, but pair-programming brings collective ownership and sharing and learning. the talk started out great but fizzled into giving me some disappointment as i ponder that he might be somewhat out of touch with the real software people. Sue

[@stringlarson1247]

I love these types of talks. At ~00:09:20-00:10:00 he hits a very key point about the mgmt side of 'agile' being adopted by mgmt/companies and almost completely glosses over the design issues implicit in this 'methodology' - ok. sure he plugs his decade old book/paper . . . blah blah make sure you pay attention to these kinds of things as well blah . . . etc. Fuckin' great Martin. The real crux of the biscuit IS FUCKING DESIGN; and, not just DESIGN, but DESIGN FOR CHANGE. Mgmt doesn't give a fuck about design much less understanding that designing for CHANGE (a.k.a. Agile buzzword compatibility) requires discipline and commitment UPFRONT. This means having mgmt. that knows and is willing to accept and pay the toll upfront. It also requires engineers who plan on sticking around more than 12-18 mos. to realize this vision and benefit from the effects of having built a system that is adaptive and solid. Or, dare I say, agile.

[@matejrifelj1299]

12:50 People are not predictable (middle finger) ;)

[@shrikantdangi6064]

he really did that

[@cristianpallares7565]

🤣 🤣

[@acdcjunior]

It seems the sentence he almost said at the end is "If a team is doing extreme programming the same way they were doing it a year ago, then they are no longer doing extreme programming."

[@akiohamasaki]

LOL...Martin flips the bird at 12:51

[@tarcisiofischer]

Is there a second part somewhere? :(

[@ctelctel1937]

This video ends abruptly at 43 minutes. Can you please fix this?

[@MrLacozz]

The last part is cut out, please re-upload if possible

[@biokode]

Hwy is there no part 2?

[@MathiasDahl]

:^)

[@jhsfernandes]

Man, I really want it

[@extendetBG]

No part 2? Now I'll never know what is a plastic kangaroo. :(

[@athos604]

+Georgi Mihaylov Just google rubber duck debugging. That's my guess :)

[@shakibamoshiri2503]

It is not complete. Where is the rest? Part 2 maybe?

[@andersonmilham]

Where is the other part?

[@tuxcode7344]

Too bad they don't show the slides in a box somewhere. Anyone who knows what book Martin Fowler is referring to at 39:13? Could it be this one: Pragmatic Thinking and Learning: Refactor Your Wetware, Andy Hunt, 2008, The Pragmatic Bookshelf, ISBN 978-1-934356-05-0 ? (Reference copied from wikipedia)

[@cybernetic100]

"khu-y" is how he pronounces "why"

[@typedeaf]

How old is this? The picture at 40:20 has a computer with a CRT and a mouse w/o a scroll wheel.

[@grdalenoort]

Extreme Programming and agile are probably from around end '90-ies to 2000-nds. Same era as the scroll mouse :-) The agile manifesto came in 2001 agilemanifesto.org/history.html

[@wharup]

Plz. Where's the other part? ㅜ_ㅠ...

[@usievents]

+wharup Hey Wharup, unfortunately we had a technical problem with the end of the talk... following one of our follower, the last sentence could be : "If a team is doing extreme programming the same way they were doing it a year ago, then they are no longer doing extreme programming."

[@wharup]

+USI Events It's so unfortunate. Anyway, thank you so much for giving me the precious sentence. :-D

[@nXqd]

seriously, where is the other part ?

[@axelvanhooren6325]

Is adaptive planning not predictive as well? Uncertainty is inherent to projects. This is why any project plan, by default, is predictive and adaptive and must be treated as such. Plan first, adapt the plan during the course of the project when it is wise to do so.

[@ratsock]

cool hwhip!

[@Mbv9Firehunter]

40:15 what does he say there?

[@mvargasmoran]

martin is awesome at looking like he knows what he is talking about. which he does, but agile...

[@jollygreen63]

hand gesture at 12:50 does not seem to fit in the presentation

[@ta_trbl]

The WH sound destroyed this entire video for me...not an easy listen

[@MarkMarino10]

+Terry Ahlander But wuh-hy?

[@SebastianSkadisson]

+Terry Ahlander I find the "wh" pronounciation very interesting. It shows where the US american english language came from in the first place, and how much and rapidly it changed to become the world's most flexible human language.

[@hadiagha2155]

Mark Marino iarNi manq st

[@hadiagha2155]

Sebastian Schulz fas bok

[@smukkepiien]

@@SebastianSkadisson I can tell you, this is NOT how British English sound...

[@JonasErik]

Oh holy shit! Video was cut!

[@usievents]

+Jonas Erik Barreto yes, we know and that's a shame... sorry for that, we had a problem.

[@sinister266]

Giving you the finger at 12:51

[@pureabsolute]

Newman!

[@Cur8or88]

Hard cut at the end there. Always leave them wanting more...

[@administratorpoletusa3758]

if can't make requirements, don't start project. how could anyone program anything for what is not possible to make requirements.. writing requirement is more easy than actually programming. so, just do it.. and for communication part, specification is communication, it takes one to write it, and it takes one to read it

[@rwoz]

hhhhhwaiii

[@shashank.c]

How does that end? 'If a team is doing Extreme Programming...' then? Don't upload videos that

[@floverdevel]

I see what you

[@mvargasmoran]

Huaiiii xD

[@kittyschooley]

I believe he in incorrect on the account of not being able to use both halves of the brain. 1) We use both halves of our brain when listening to music, playing music. 2) Women (so I've heard) are able to use both halves of their brains as there are more connections between the two halves in a female brain. Perhaps an argument for more women software developers?