Video Spotlight

Banner

Agile Poll

How important are CM tools (e.g., Version Control) for Agile projects?
 

Online Users

  • R. Drew Davis
1 user(s) and 1890 guest(s) online | Show All
Home

Agile Journal Article Submission Guidelines

PDF Print E-mail

We welcome contributions to the Agile Journal. When submitting an article, please adhere to the following guidelines:

Abstracts

Abstracts are accepted at any time. The abstract must provide the key position that the article will take and points to back up the position. The abstract must also include the audience (developer, tester, manager, multiple, etc.) to whom the article is written. The editor will notify you if your abstract has been accepted, and for which upcoming issue.

 

Due Date
Articles are due on the 15th of the month prior to publication. The Agile Journal is usually published on the 2nd Wednesday of each month. See the Editorial Calendar for monthly themes at www.agilejournal.com.

Title
Try to keep the title to less than 100 characters. Anything longer than that will be truncated in the online version.

Author Bio
A short (1 paragraph) bio is required for all writers. You may include links to your company's website or links to your other published works.


Article Length
Articles should be in 1200-2000 words in length. Longer articles may be submitted but we may wish to break it into multiple pieces to run as a series.

Article Content
You may use pictures graphics or other diagrams in your article but keep in mind that graphics will be viewed online with a maximum width of 500 pixels so try to keep them relatively simple. Please submit graphics in .jpg format.

Use as little formatting in your article as possible since will all be removed prior to publication. Use of HEADING styles is not recommended and will be converted to BOLD, BOLD UNDERSCORE and BOLD ITALICS

Bulleted and numbered lists should use no more than two levels. Please avoid an over use of bulleted lists. Try to leave that for the manuals.

Submission Method
To submit your article, fill out the form below or email editor@agilejournal.com. Be sure that if you have included graphics in your article that you also email the images as separate attachments. PLEASE avoid using Word formatting other than bold, italics, underscore, and bulleted lists. We will respond to you within a few days with any questions or comments and for final editing.

 

Write For Us

First Name (*)

Please enter your First Name.
Last Name (*)

Please enter your Last Name.
E-Mail Address (*)

Please enter your E-mail Address. An E-mail will be sent to you to verify your account.
Phone Number (*)

Please enter your business phone number.



Optional Document Attachment (doc, pdf, or txt)

Unacceptable File Type. Please only upload a .DOC .PDF or a .TXT file only. If you have a different file type, contact us by E-mail, or provide a link where we can download it.
Writing Topics

Invalid Input
Authors Biography

Invalid Input
Questions and Comments

Invalid Input
Human Check
Human Check
Reload numbers
Incorrect Entry. Does not match with origonal. Please re-enter the 4 numbers above.



 

Agile Marketplace - Announcements and Special Offers

Complimentary Webinar w Forrester Analysts on Agile and Lean ALM
Complimentary webinar with Forrester Analysts Jeffrey Hammond and Dave West. Learn about Lean ALM Development, optimizing processes, cutting costs and compliance by design.
Read More


Agile CMMI – The Best of Both Worlds

Shares how a leading financial institution gains CMMI level 3 compliance and supports Agile practices.
Register for CollabNet webinar May 21


Requirements-based testing (RBT)
can help you increase efficiency, reduce project risk, and improve overall software quality. Learn how MKS Integrity for application lifecycle management enables RBT, delivering full lifecycle traceability to help ensure that project requirements have complete test planning and execution coverage. Download the Requirements-Based Testing whitepaper