We are looking for authors for the Agile Journal. Here is the 2012 editorial calendar as a guideline for you:
January: Requirements; Agile Game Development
February: Low Tech Test Tools
March: Mobile, Redefining Quality
April: Acceptance Test Driven Development
May: What is Quality?
June: Agile Management
July: Cloud Development
August: Business Value
September: Agile Testing
November: Salary Survey; Embedded Systems
When I say editorial calendar as a guideline, I mean just that. If you have an article that is jumping out of you, and it doesn’t fit the guideline for a given month, please send the article to me. Do not worry!
Here’s how I work with authors: I read your article. I try not to make any copyedits. I do make some edits if I think they affect your meaning. I ask you questions in comments to make sure I understand your meaning. My job is to make sure you make sense and that you look smart and consistent to your readers. I want everyone to think, “Wow, this author has something really interesting to say.”
Sometimes, authors have peanut butter thinking. That is, they get their thoughts all stuck together. (I do this, which is why I recognize it.) I can help you unstick your thoughts. Sometimes, authors have their best sentence at the end. (I do this.) I can suggest it go at the beginning. Sometimes, authors need an example. (I do this.) I suggest you need an example. You don’t have to take my suggestions. I try to have a light touch.
My goal, which I think is your goal, is to help you get published.
PR people: Once you send in the article, your work is done. I work with the author, not with you. And no, I don’t talk with you on the phone. I edit, which is writing, not talking. I know, that’s so different from what you do. Thank you for understanding.
So, what do you say? Want to write an article for the Agile Journal? I’ll get some of my previous authors to say how nice it was working with me, even when I pushed them hard to make their articles different from what they originally thought. The results were great.Tags: Agile Journal