Blog

Check if or check that? Or: Have you tried turning if off and on again?

How often do we read or write that we should check something? Example: "Check if the computer is connected to power." Clear message, no misunderstanding. But what if it says: "Check that the computer is connected to power." more ...

Ten questions for Ines Lasch, intern at parson

Ines Lasch just finished her vocational training as a technical writer and is doing an eight-week internship at parson. We asked her ten questions. more ...

Vocational Training for Technical Communicators. How Does it Work?

Anja Schiel, trainee, and Ulrike Parson, CEO of parson AG, offer their insights into the vocational training for technical communicators. more ...

Make Technical Documentation Intelligent - From Content Management to Content Delivery

In this article, Martin Kreutzer and Ulrike Parson describe how you fill content-delivery portals with intelligent information so that users quickly get the right answers to their questions. more ...

parson's mentoring program

You sent the job application and the interview went well. Now comes your first day at work. Everything is strange: colleagues whose names you immediately forget, business processes, the ERP system. Even the coffee machine doesn't work right away. And where was that meeting room again? more ...

Developing Software on a Beer Mat

I just learned that our workshop "Developing software on a Beer Mat" at the annual tekom conference in Wiesbaden is already fully booked. The tekom organizers made another time slot available, so that more people can participate. What is going on? I have had the most horrible nightmares seeing myself on a big stage watch the only three people in the audience fall asleep. Or worse: leave.

Maybe most of the people who registered just read the word “beer”?

Well, it’s not about beer. It’s about user stories. About agile software development. About Scrum. And how software developers and technical writers can benefit from it. Because Scrum does not use lengthy functional specifications anymore. In Scrum we write our requirements as short user stories that could easily fit on a beer mat. But not only are these user stories brief. They are independent and self-contained. Perfectly fitted for a user manual. Don’t believe it?  Read Developing Software on a Beer Mat. User Stories for Documentation and Development.

Add comment


  • facebook
  • linkedin
  • xing