ognizant Communication Corporation

FAILURE & LESSONS LEARNED IN INFORMATION TECHNOLOGY MANAGEMENT

AIMS & SCOPE

Most people learn more from failures than from successes. In information technology management, many lessons have been learned over the years "the hard way" through failed implementations, poor management practices, technology limitations, and the like. Failure & Lessons Learned in Information Technology Management is devoted to addressing failures of and lessons learned from information technology projects in business, universities, government, and the military that did not succeed due to technology, management, organizational, social, cultural, and other issues. The goal is to learn from these cases and understand the basis of decisions made in order to not recreate the same mistakes or "reinvent the wheel." The organizational names in the articles can be protected by using pseudonyms.


INSTRUCTIONS TO CONTRIBUTORS

Submission of Manuscripts: The entire manuscript, including references and figure legends, should be typed double spaced on 8 1/2 X 11-inch paper with at least 1-inch margins printed on one side only. Submit three (3) complete copies (including figures and tables) to:

Dr. Jay Liebowitz
Editor-in-Chief
Robert W. Deutsch Distinguished Professor in IS
Dept. of Information Systems
University of Maryland-Baltimore County (UMBC)
1000 Hilltop Circle
Baltimore, MD 21250
Telephone: 410-455-3227
Fax: 410-455-1073
Email: liebowit@umbc.edu

Preparation of Manuscripts: Arrange the manuscript as follows: Title Page, Abstract, Text, Acknowledgements, References, Figure Legends, and Tables. Number all pages of the manuscript.

Title Page: The first page must include the article title, all author names and corresponding affiliations (complete addresses), and the designated corresponding author's complete mailing address, with telephone, fax, and E-mail address (if applicable). Include a short title (up to 40 characters) to be used as a running head. Also include any current address information on this page.

Abstract: Provide an approximately 200-word abstract. It should cover the main points of the article so the reader can quickly obtain a general overview of what the article contains. Provide 3 to 5 keywords for indexing after the abstract.

References: References should be placed at the end of the text, beginning on a separate sheet, arranged in alphabetical order and styled to follow American Psychological Association guidelines as set forth in their Publication Manual (4th edition). Cite surnames and year in parentheses in the text. Do not list personal communications in the reference list. Follow the examples below for styling references:

Journal Reference
Leibowitz, J., & Potter, W. (1995). Scheduling objectives, requirements, resources, constraints, and processes: Implications for a generic expert scheduling system architecture and toolkit. Expert Systems With Applications, 9(3), 423-432.

Book Reference
Liebowitz, J. (Ed.) (1996). Hybrid intelligent system applications. Elmsford, NY: Cognizant Communication Corporation.

Book Chapter
Michailidis, A., & Rada, R. (1996). Collaborative authoring tools. In R. Rada (Ed.), Groupware and authoring (pp. 9-44). London: Academic Press.

Figures and Tables:
Provide high-quality glossy or laser-quality black and white art work. Identify each figure with a label on the back. Avoid small lettering or symbols that would not take reduction for printing. Provide a separate sheet with legends for all figures. Place each table on a separate sheet. Avoid extremely wide tables that would not fit easily on a page.

Computer Disk:
To speed publication and ensure accuracy, authors are requested to submit a computer disk that contains the final version of the manuscript along with the paper copy to the editorial office. Please observe the following criteria:

1. Specify what software was used (e.g., WordPerfect 6.0). 2. Specify what computer was used. 3. Include both text file and ASCII (DOS) file on the disk. 4. The file should be single spaced and should use wrap around end of line feature (i.e., no return at the end of a line). All textual elements should begin flush left, no paragraph indents. Place two returns after every element such as title, heading, and paragraphs. 5. Keep a back-up disk for reference and safety.

Page Proofs/Offprints:
Page proofs will be sent to the designated corresponding author. An offprint order form for ordering reprints and full copies of the issue will accompany the page proofs and must be returned with the proof.

Copyright Agreement:
When accepted for publication, copyright of the article, including the right to reproduce the article in all forms and media, shall be assigned exclusively to Cognizant Communication Corporation. It will be necessary for all authors to sign a Transfer of Copyright Agreement upon acceptance on the manuscript.

Although every effort is made by the publishers and editorial board to see that no inaccurate or misleading data, opinion, or statement appears in this Journal, they wish to make it clear that the data and opinions appearing in the articles and advertisements herein are the sole responsibility of the contributor or advertiser concerned. Accordingly, the publisher, editor, editorial board, and their respective employees, officers, and agents accept no responsibility or liability whatsoever for the consequences of any such inaccurate or misleading data, opinions, or statement.