Greg Young

Agile Prague 2025

The next year of Agile Prague Conference is going to be Sep 15-16, 2025.

AgilePrague Innovate Experiment Change

Conference workshops 2024

Join the workshops organized together with Agile Prague 2024 and learn:

ICAgile Certified Professional in Agile Coaching (ICP-ACC) on Sep 18-19, 2024,
Certified Business Resilience on Sep 18-19, 2024

September is an Agile month

September is an Agile month. At least you can make it very Agile.

Join AgilePrague Sep 16-17, Women In Agile Prague Sep 18, and Regional Scrum Gathering Stockholm Sep 9-10. Three conferences, great learning. Register today to get early bird ticket.

Enjoy #AgileSeptember!

Wouldn’t it be great to go to a conference that included all of the topics that are most interesting to you? A conference that addressed your most pressing questions?
That’s what the Open Space sessions are for. It’s the part of the conference that you get to design.

Join the lunch Open Space and deepen your learning experience.

Greg Young

Greg Young is an independent consultant and entrepreneur. He is always involved with many concurrent projects, currently these include building out a distributed event store and mighty moose (a continuous test runner). For periods of years Greg has been known to stop living anywhere and just travel.

gregyoung

Blog: http://goodenoughsoftware.net

http://continuoustests.com

Developers are strange creatures

We as developers have many biases that often we need to take a step back from in order to gain perspective. This session will deliberately go after many of our sacred cows and show how they are really just us over-optimizing a belief.

Becoming Effective in the First 24 Hours of your Project

Often we get thrown into new projects either due to movements within an organization or our own choice of becoming contractors. This talk looks at strategies for getting the lay of the land and providing value with your first few days of the project. Where are areas that are worrying within the code base? What code should probably be refactored? How can we more quickly identify hot spot and gotchas inside of a project?

See the slides