All posts by Paul Herwarth von Bittenfeld

Tools4AgileTeams Conference 2017: First-Bird Tickets Are Now Available

Tools4AgileTeams

The 6th instalment of our Tools4AgileTeams conference in Wiesbaden is on 30 November ad 1 December. The organizational and content preparation has begun, and the ticket sales for the T4AT 2017 are now open! The first-bird rate is currently available for early registrations and you can now secure your participation in the conference at an attractive price.

Tools4AgileTeams 2017 Conference: Call for Sessions – Submit Yours Now!

Tools4AgileTeams 2016 Keynote

The 6th instalment of our Tools4AgileTeams conference is already looming on the horizon. It is on 30 November and 1 December, and as usual, in Wiesbaden. We return to the rooms of the IHK Wiesbaden, after having a good experience with them last year.

We’ve also decided on the overarching theme for this year’s conference: Agile Goliath – is this possible?

Three Pillars of Successful Product Innovation

At //SEIBERT/MEDIA, we’ve been developing and creating software for years. During this time, we’ve discovered some basic elements that are vital to building products that gain wider marketplace acceptance and are, ideally, exciting.

When I hear about dissatisfied customers or projects that failed, it’s usually because we’ve neglected to consider at least one of the following “three pillars of successful product innovation.” I now regard them as essential to our success as a product provider.

RheinMainJS Meetup on 26 January 2017 at //SEIBERT/MEDIA in Wiesbaden

RheinMainJS

The JavaScript User Group Wiesbaden und Mainz (in German) has their twelfth meeting on the 26 January 2017, and we are hosting them at //SEIBERT/MEDIA. RheinMainJS is a user group focusing on JavaScript and related areas such as mobile development. It is open to everyone who is interested in technology and you are invited to attend the bi-monthly meetings free of charge.

Hackathon at //SEIBERT/MEDIA – Field report on developing the EasyEvents plugin for Confluence

The goal of a hackathon is to buckle down and create a product and/or complete a small project under time pressure (at //SEIBERT/MEDIA within 24 hours). The hackathon team alone plans and decides what kind of product or project to work on. We explained the reasons for regularly conducting hackathons in our agile organization in more detailed articles. On the one hand, we strive to create concrete and truly innovative solutions. On the other hand, we try to attain “soft” effects, such as promoting training, teamwork and personal responsibility and motivating our employees. Our latest hackathon took place in early July 2013. In the following chronological field report, we offer insight into the work of the team that designed and developed the EasyEvents Confluence plugin.

Why we transfer requirements lists into a backlog with user stories

We are often contacted by customers with very rough, technical requirements lists for software projects. In cases like this, the first project step for //SEIBERT/MEDIA is to turn the customer’s requirements list into a product backlog that highlights how the customer benefits from the requirements. This is not a trivial task and requires time and resources. But why should the customer pay for this preparation work that has nothing to do with actually completing the project?