The content catalog for JavaOne is available. The abstract for my presentation, From the Spring Framework to Java EE 7 (CON3598) can be found there together with more than 500 other sessions. Still haven’t registered?
Conferences
JavaOne 2013
Having missed out on the last couple of JavaOne conferences, I am extremely happy that I will be attending this year. And not only as an attendant, but as a speaker.
More details on my talk will follow. For now, make sure you register for the conference.
A Pragmatic Approach to Continuous Delivery Slides
The slides from my presentation at jDays 2012 are now available here:
jDays 2012
I am at the final stage preparing my presentation on A Pragmatic Approach to Continuous Delivery for jDays next week. Hope to see you there!
I will make the slides from the presentation available here shortly after the presentation.
A Pragmatic Approach to Continuous Delivery
Summer time means less people at work and more time to think ahead what to do the remaining part of the year. In my case it means that I have signed up for a talk called A Pragmatic Approach to Continuous Delivery at jDays, a Swedish Java Developer Conference located in Gothenburg. Read the abstract here, and vote for it here if you think it sounds interesting.
While I was at it, I also proposed a lightening talk on the same subject to Smidig 2012, a Norwegian Agile Developer Conference in Oslo.
Agila Sverige 2012 Wrap-Up
Agila Sverige is a wrap. It has been two exiting days with a lot of great presentations and interesting topics discussed at the Open X sessions.The slides from my presentation can be found here: Arkitektrollen – Agila Sverige 2012 (text is in Swedish).
If you want more information about The Agile Architect Pattern, see my previous post about it here at this site.
Agile Architect Pattern
Intent
Guide the team to reduce technical debt before it becomes a problem.
Motivation
The nature of agile development is to deliver working software continuously. This means that the focus for all actors (Product Owner, Scrum Master and Team) is on the functionality delivered in each iteration. As a consequence, technical debt is considered okay and is likely to increase for each iteration completed. Often, this is allowed to go on until the debt has reached a level where the velocity of the team is starting to decline. After a while something has to be done, and the term Refactoring Sprint is introduced. A refactoring sprint is in this context an iteration totally devoted to paying off technical debt, thus no functionality is delivered for an entire iteration.
How it works
The Agile Architect Pattern prevents the scenario from the motivating example from happening by introducing an Agile Architect role. The Agile Architect can be seen both as a member of the team and as well as a stakeholder. This makes him/her able to both work with the team members, guiding them while trying to identify architectural issues as well as discussing requirements for future iterations with the technical resources from the client. While the team has a iteration-by-iteration time frame, the agile architect can see a few iterations ahead making sure the architectures evolves in a way that (hopefully) will not cause major problems ahead.
When to use it
The Agile Architect Pattern should be used in any project spanning over enough iterations likely to cause the technical debt large enough to slow the team down. It is important that the Agile Architect is comfortable both in the code domain acting as a guide for the team as well as on a higher level of abstraction to be able to interact with the client technical resources.
Upcoming Talk at Agila Sverige
I will be giving a lightning talk on the subject “The Architect role is needed, even in agile projects!” at the Agila Sverige conference which is arranged in Stockholm the 23rd and 24th of April this year. I will not reveal too much of the content here, but as the title implies, I will be promoting the need of an Agile Architect in every project. Agile or not…
Øredev 2010 – final thoughts
Having attended all previous Øredev conferences I think I am pretty qualified when I say that this year’s conference was by far the best. Great topics, excellent speakers and flawless organization. Even the closing panel debate, which usually is just something you have to suffer through to be able to win prices in the raffle at the end, was interesting this year.
Since it is such a diverse conference, it is difficult to point out a single item that was the main trend at the conference. But if I should pick one thing, I guess it would be that most of the talks I attended more or less circled around the Get Real! theme of the conference. Hopefully this means that the industry is getting more mature. Don’t want to be a self-fulfilling pessimist, so it is just to be optimistic 🙂
See you there next year!
A Special Year
The first time I attended JavaOne was 1999 and I have only missed it once since then. Sadly, this year will be the second time I am not present there. I have become kind of used to the week in San Francisco every year. It is the perfect way to start the summer with a visit to that beautiful city. Since it is in September this year, it would probably been the perfect way to end the summer (…we have short summers here in Scandinavia…).
I will for sure miss the massive input and inspiration this conference gives me and enables me to keep up-to-date on everything that is happening in the Java Community. This year’s conference is also special since it is the first time Oracle is hosting the show. It feels like a good idea to co-host it with Oracle Develop and I hope it will be a success to be continued. Next year, I will definitely be attending, one way or the other…!