Agile Prague 2014 Notes

Table of Contents

It’s been almost a week since Agile Prague finished. It was a great time of interesting discussions and meetings. I had the privilege to talk with Linda Rising about patterns, their history, and current state (still under development). She also gave wonderful talks about the Agile mindset and trust.

It was also a pleasure to discuss with Paul Klipp and take part in his talk about communication—a subject I am always interested in.

Another two interesting subjects I listened to were:

  • Vasco Duarte’s talk on the NoEstimates approach, which, in my opinion, is not exactly about not doing estimation, but extremely simplifying the way you do it. In short: estimate an item with 1 point. If it is too big (should be more than 1), split it.
  • Louis Goncalves’s talk about getting rid of performance appraisals.

I also had the privilege to give my talk about the Natural Course of Refactoring. You can find slides here.

I received very nice and positive feedback.

See you soon at Warsjawa.

(Text translated and moved from original old blog automatically by AI. May contain inaccuracies.)

Tags

Related Posts

A Manifesto Against Developers

A Manifesto Against Developers

I hate you because:

  • You focus on the features of your IDE instead of the features your client/user needs.
  • You consider typing at the keyboard as thinking.
  • You waste countless hours manually testing your code.
  • You spend more time struggling with frameworks than delivering value to end users.
  • You code for hours without asking yourself, “What am I really doing?”
  • You naively believe that technologies and tools will solve your problems.
  • You naively believe that a good algorithm is more important than a good understanding of requirements.
  • You naively believe that your intuition is enough for writing good code.
  • You naively believe that you can manage the complexity of the system piece you’re working on.
  • You agree to unrealistic deadlines.
  • You write poor code and rationalize it with various excuses (because there is no time).
  • In your head, you create code snippets without really knowing what needs to be done.
  • You guess what needs to be done rather than clarifying.
  • You mindlessly follow the technology you use.
  • You don’t understand the tools and technologies you use.
  • You isolate yourself in your piece of code, breaking contact with the world.
  • You think it’s all the fault of managers or clients and believe you can’t do anything about it.

… even though I love you because I am a programmer myself.

Read More

Two Structuring Meetings Patterns

As I describe in my book, it is beneficial to structure meetings (or parts of meetings) to make them more effective. Here are two examples useful for planning meetings, applicable in Scrum and adaptable to other contexts.

Read More

The Charisma of a Leader

The Essence of the Charismatic Leader

Recently, I’ve been working more with leaders of development teams, and I’ve become quite intrigued by the topic of dynamism and the charisma that often accompanies it.

Read More