Yves Hanoulle, Author at Yves Hanoulle

#Interview with Faye Thompson, JD for the #video edition of Who is #agile (#WIa061)
Faye was invited by Esther Derby

We talked about:
– Growing into business roles and then into #coaching
– Writing #documentation and move on before developers started
– Having to argument to be allowed to be able to talk to actual users.
– Having a career as an #attorney
– Thinking about post work life
– The only thing left is for me to die….
– I want that the things I’m doing matter
– What do I want to leave behind
– Loving the job as a #coach
– #Immigration system is broken in the USA
– Wanting to explore something more
– There is no one size fits all in agile
– Cleaning up the mess
– #ChangeFatigue
– We tried it, and it doesn’t work
– We stick around when things go bad and then we leave when things go better
– Bringing her whole self to work
– That is not how humans work
– Optimising the results instead of the use of her time
– A development team is always going to look for the most efficient way to do something.
– Giving guidance for managers…
– Reaching out years later to people that had impact on us.
– Dealing with #Cancer
– Whoever show up are the right people
-I can’t chose what happens, yet I can chose how to react to things…
– Being #angry for 15 minutes
– When one person is remote, be all remote
– Have separate facilitators for remote an in-room
– thought limiting cliché’s

Books we talked about :
– You are not so smart ( David McRaney)
– You are now less dumb (David McRaney)
– How minds change (David McRaney)

Faye invited
– Mark Kilby
– April Jefferson “Soul Craftswoman”
– Diana Larsen – Leadership Agility Advisor
– Esther Derby
– Johanna Rothmann
– PSL

Faye invited Tammy Gretz

#Interview with Chris Lucian & Austin Chadwick for the #video edition of Who is #agile (#WIa060)
Chris & Austin were invited by Patrick Debois

We talked about:
– #Mob Mentality
– A tight coupling by having fun and #effectiveness
– Merging aspects from different parts of life and integrating them
– Austin being influence by his partner.
– Tight feedback loops with #children
– Talking about how #ComputerScience was almost an accident
– Starting IT for #money and liking it
– Valuing a #worklife balance
– The worklive balance in the #gaming industry
– Mob programming influence a low bug count and build in knowledge sharing
– Worklife aspect is much better in a team that mobs
– No one can stay on the same product for more then 2 years
– #chaosengineering at team level
– Communicating outside a group so that management is aware and wel understand the financial – impact on mobbing
– Mob programming for a decade
– 3 to 5 people mobs
– Providing space for experiments
– #PromiscuousPairing (from Arlo Belshee)
– Daily swapping the mob
– Unconscious dependance when people stayed for 5 years instead of documentation or automation
– Being prepared for turn over, also at budget level
– Mobbing helps skyrocketing developers
– Every 5 years all people have a life changing event.
– Average level of happiness
– Marketing competition spreadsheet
– Total nr of people on your team divided by 5
– Is your turn over under or over that number?
– Discussions in a mob with different world view.
– Automating
– Learning by having models around you
– Nono Donsa experience of body language was different at school and at home
– Nina Derwael Olympic medals
– Satir model of change
– Tuckman team model
– #psychologicalsafety
-The world is my #Kanban
– Learning loop
– #Kaizen Habits instead of trying to be the best …
– Draw separately and then compare
– People learn when they are wrong
– #uml diagram of whet you just discussed
-What is the learn effect
– Difference between #introverts and #extraverts and their differences between in person-remote
– Measure the impact of the life of your employees
– Dora metrics

Books we talked about :
– Dynamic retiming (Heidi Helfand)
– Grit book (Angela Duckworth)
– How emotions are made (Lisa Feldman Barrett : learn about how you are wrong about reading body language)
– Mob programming (Woody Zuill )
– Thinking fast and slow ( Daniel Kahneman)
– Reality is broken (Jane McGonigal)
– Accelerate (Nicole Forsgren)
– Atomic habits (James Clear)

They invited
– Woody Zuil
– Joe Justice (Wikispeed)
– Colleen K.
– Mike Clement

#Interview with Emily Bache for the #video edition of Who is #agile (#WIa059)

Emily was invited by Clare Sudbery (she/her)

We talked about:
– Working with #legacy code
– How her husband influenced her #career.
– Going to #conferences as a couple
– Finding coding fun
– She does not want to stop coding as that is the fun part.
– Doing co-presentation
– Having children that are not interested in programming
– #Singing in choirs
– Working as a musicians
– Comparing #codingdojo and musical
– How do you show progress when you start with something ?
– #Teaching
– You can’t learn a skill from reading
– you can learn the theory, yet not the skill
– Trying the examples in the books
– Being the most passionate
– Being an inspiring choir leader
– There are so many fun tings to do
– Emily has got options
– Building her carreer in a way that she always has avenues to move to, if the current one does not turn out to go somewhere.
– Understanding quickly the problem a team has
– it’s rewarding when you work hard get good grades and teachers appreciate you.
– She does enough to get the results she wants,
– She wants to make a difference
– Making the software better to change the world

We talked about
Kent Beck
Samman Technical Coaching
Dion Stewart & Joel Tosi
Vladimir Khorikov

Books:

Extreme programming (Kent Beck)
– Emily’s books:
Coding Dojo handbook
Mocks Fakes & stubs
technical coaching with the Samman method

Creating your Dojo
Coaching for learning
Unit testing principles

Emily invites:
Dave Farley

Some years ago I worked with a team that was doing continuous integration.

We wanted to move to continuous deployment, yet we could not convince our client to do so.
Although we could not install automatic, we did build a pipeline for our installation.

At that moment we did demos at the end of our sprints. When the demo was finished we asked the client if we could install. When the client agreed could, we launched our pipeline to do the installation.

I bought the red button you see on the left. (I bought it on DreamCheeky yet that website no longer sells it. The link on barndo.com still works, yet the item is no longer sold)
This USB button, has two events, the opening of the cover and the pressing of the button.

One of the developers look at the code that came with the button. The code is now available on github, yet then it used to be on codeplex. That developer adapted that program that the opening of the cover, would launch the webpage for the pipeline and the pressing of the button, would triggering the launching of the install.

Although it started as a gimmick, it create a real interesting dynamic.
At the end of our demo, we would slide the button to the client. If the client was impressed with the demo, the button was pressed. The client loved that control. Even though before had asked also, and we even briefly had allowed the client to press the right button on our pipeline, it felt too much an IT thingy. The button changed that dynamic. Now the client really felt in control,

The logo.

After most demos, the button was pressed; Yet I still remember that one time, the client had complained about the color of a new logo, at the start of the demo and then everything went smoothly. The team felt they nailed it again; Helas. The slight wrong color of the logo was enough to not press the button. After the initial surprise of the team,I saw in the corner of my eyes two developers making signs to each other. Later it turned out one of them she wanted the other to stall the client, she went back to her computer, implemented the requested color change, once she committed that was automatically installed on our demo site. In less then 5 minutes she came back, showing the results to the client, who asked for the button and pressed it. The combination of the feedback, the refusal, the quick fix and the button made a huge impact on both the the client and the team. Not long after that we were allowed to do an continuous delivery (The client now felt we would be able to roll back very fast if needed. )

Author: Yves Hanoulle

aye Thompson likes to optimising the results instead of the use of her time

The positive impact of mob programming from Chris Lucian & Austin Chadwick for #WhoIsagile #WIa60

Emily Bache never stopped programming, as that is the fun part… #WhoIsagile #WIa59

Empowering the client with a red button…

Interesting article? Dont hesitate to share

Interesting article? Dont hesitate to share

Interesting article? Dont hesitate to share

Interesting article? Dont hesitate to share

Stay up to date