Project Management Journal Guidelines for Case Submissions

Project Management Journal® publishes cases relevant to instructors, reflective practitioners, and organizations from the project, program, and portfolio management fields. Project Management Journal® seeks cases that are of interest to a broad audience.

Due to the integrative and interdisciplinary nature of these fields, Project Management Journal® publishes the best cases from a number of other disciplines, including, but not limited to, organizational behavior and theory, strategic management, marketing, accounting, finance, operations research, technology and innovation management, entrepreneurship, economics, political science, history, sociology, psychology, information science, decision science, systems theory, and communication theory.

Project Management Journal® neither approves nor disapproves, nor does it guarantee the validity or accuracy of any data, claim, opinion, or conclusion presented in either editorial content, articles, From the Editor, or advertisements.

Project Management Journal® is a journal to disseminate and discuss project management research and teaching. It is not a platform to discuss the content or quality of PMI standards, credentials or certifications, and those of other standard-setting organizations.

Authors' Guidelines

Cases published in Project Management Journal® must be research-based (whether field- or secondary-research) and opportunities for students to learn about application of project management theory and/or project management practices. Authors are expected to describe in the instructor’s manual the knowledge and foundations underlying their research approach, and theoretical concepts that give meaning to data or to proposed decision support methods, and to demonstrate how they are relevant to organizations in the realm of project management.

Authors should define any specialized terms and analytic techniques used. Cases should be factual and well written, avoiding jargon at all times. No fictional cases or cases containing composite characters will be considered for publication; however, companies and individuals may be disguised for privacy. Project Management Journal® does not prefer subjects of study, as long as they are in the project, program, or portfolio management field, or in the field of the project-oriented organization or project network, nor do we attach a greater significance to one methodological style than another does.

Avoid Use of Commercialism

Cases should be accurate and objectively written in narrative format in the past tense and be accompanied by a comprehensive instructor’s manual that provides a clear teaching plan. Instructor’s manuals will be made available only to instructors and will not be published within the journal itself. Cases that are commercial in nature (e.g., those that endorse or disparage specific products) will not be published.

Editing Your Case and Instructor’s Manual

Write in clear and concise English, at the level of the potential audience for the case, using active rather than passive voice. Cases should not exceed 7,500 words, exclusive of figures, tables, and references. Instructor’s Manuals do not have a length limitation.

Manuscript Format/Style

All manuscripts submitted for consideration should meet the following guidelines:

  • All papers must be written in the English language (American spelling).
  • Title page of the manuscript should only include the title of the paper.
  • To permit objective double blind reviews by two referees, the abstract, first page and text must not reveal the author(s) and/or affiliation(s). When authors cite their own work, they should refer to themselves in the third person. Any papers not adhering to this will be returned.

Formatting the Paper

Papers must be formatted in an electronic format using a current version Microsoft Word. For Mac users, convert the file to a Windows format. If the conversion does not work, Mac users should save files as Word (.doc) files.

Fonts

Use a 12-point Times or Times New Roman font for the text. You may use bold and italics in the text, but do not underline. Use 10-point Helvetica or Arial font for text within tables and graphics.

Margins

Papers should be double-spaced and in a single-column format. All margins should be 1 inch.

Headings

Use 1st, 2nd, and 3rd-level headings only. Do not number headings.

References, Footnotes, Tables, Figures and Appendices

Always acknowledge the work of others used to advance a point in your instructor’s manual. Avoid referencing theory within the case itself. For questions regarding reference format, refer to the current edition of Publication Manual of the American Psychological Association. Identify text citations with the author name and publication date in parentheses, (e.g., Cleland & King, 1983), and listed in alphabetical order as references at the end of the manuscript. Include page numbers for all quotations (page numbers should be separated by an en dash, not a hyphen).

Follow the formats in the examples shown below:

Baker, B. (1993). The project manager and the media: Some lessons from the stealth bomber program. Project Management Journal, 24(3), 11–14.

Cleland, D. I., & King, W. R. (1983). Systems analysis and project management. New York, NY: McGraw-Hill.

Hartley, J. R. (1992). Concurrent engineering. Cambridge, MA: Productivity Press.

It is the author´s responsibility to obtain permission to include (or quote) copyrighted material, unless the author owns the copyright. Use the permission form, which is available at the Manuscript Central site.

Graphics and Illustrations

Be sure to number tables and figures with Arabic numerals, include titles for each, and insert them in their preferred location within the body of the text. In addition, provide artwork in 300-dpi jpg, tiff, or PowerPoint formats.

Tips for creating graphics:

  • Provide only the essential details (too much information can be difficult to display).
  • Color graphics are acceptable for submission, although Project Management Journal® is published in grayscale.
  • Helvetica or Arial font should be used for text within the graphics and tables.
  • Figure numbers and titles are centered and appear in boldface type below the figure.
  • Table numbers and titles are centered and appear in boldface type above the table.
  • Figures and tables should be cited and numbered consecutively in the order in which they appear in the text.
  • Tables with lines separating columns and rows are acceptable.

Use an appendix to provide more detailed information, when necessary.

Submission Policy

Submit manuscripts electronically using Project Management Journal®’s Manuscript Central site.

Manuscript Central is a web-based peer review system (a product of ScholarOne). Authors will be asked to create an account (unless one already exists) prior to submitting a paper. Step-by-step instructions are provided online. The progress of the review process can be obtained via Manuscript Central. Other questions regarding publication may be sent to kim.shinners@pmi.org.

Manuscripts should include the following in the order listed:

  • Title page. Include only the title of the manuscript (do not include authors’ names).
  • Abstract. Outline the purpose, scope, and conclusions of the manuscript in 100 words or less. * Keywords. Select 4 to 8 keywords. Do not include the abstract at the beginning of the case.  This should appear in the Instructor’s Manual.
  • Headings. Use 1st, 2nd, and 3rd-level, unnumbered headings.
  • Text. To permit objective reviews by two referees, the abstract, first page and the rest of the text should not reveal the authors and/or affiliations.
  • References. Use author-date format.
  • Illustrations and tables. These should be titled, numbered (in Arabic numerals), and placed on a separate sheet, with the preferred location indicated within the body of the text.
  • Biographical details for each author. Upon manuscript acceptance, authors must also provide a signed copyright agreement.

By submitting a manuscript, the author certifies that it is not under consideration by any other publication; that neither the manuscript nor any portion of it is copyrighted; and that it has not been published elsewhere. Exceptions must be noted at the time of submission.

Authors using their own previously published or submitted material as the basis for a new submission are required to cite the previous work and explain how the new submission differs from the previously published work. Any potential data overlap with previous studies should be noted and described in the letter to the Editor. The editorial team makes software-supported checks for identifying plagiarism and self-plagiarism.

Accepted manuscripts become the property of PMI, which holds the copyright for materials that it publishes. Material published in Project Management Journal® may not be reprinted or published elsewhere, in whole or part, without the written permission of PMI.

Accepted manuscripts may be subject to editorial changes made by the Editor. The author is solely responsible for all statements made in his or her work, including changes made by the editor. Submitted manuscripts are not returned to the author; however, reviewer comments will be furnished.

Upload Manuscript

Review Process

The reputation of Project Management Journal® and contribution to the field depend upon our attracting and publishing the best research and case materials. Project Management Journal® competes for the best available manuscripts by having the largest and widest readership among all project management journals. Equally important, we also compete by offering high-quality feedback. The timeliness and quality of our review process reflect well upon all who participate in it.

Developmental Reviews

It is important that authors learn from the reviews and feel that they have benefited from the Project Management Journal® review process. Therefore, reviewers will strive to:

  • Be Specific. Reviewers point out the positives about the case and instructor’s manual, possible problems, and how any problems can be addressed. Specific comments, reactions, and suggestions are required.
  • Be Constructive. In the event that problems cannot be fixed in the current submission, suggestions are made to authors on how to improve the case on their next attempt. Reviewers document as to whether the issue is with the underlying research, the case, the instructor’s manual, or the way the information is being communicated in the submission.
  • Identify Strengths. One of the most important tasks for a reviewer is to identify the portions of the paper that can be improved in a revision. Reviewers strive to help an author shape a mediocre manuscript into an insightful contribution.
  • Consider the Contribution of the Manuscript. Technical correctness and theoretical coherence are obvious issues for a review, but the overall contribution that the paper offers is also considered. Cases will not be accepted if the contribution it offers is not meaningful or interesting. Reviewers will address uncertainties in the paper by checking facts; therefore, review comments will be as accurate as possible.
  • Consider Submissions from Authors Whose Native Language Is Not English. Reviewers will distinguish between the quality of the writing, which may be fixable, and the quality of the ideas that the writing conveys.

Respectful Reviews

PMI recognizes that authors have spent a great deal of time and effort on every submission. Reviewers will always treat an author’s work with respect, even when the reviewer disagrees or finds fault with what has been written.

Double-Blind Reviews

Submissions are subjected to a double-blind review, whereby the identity of the reviewer and the author are not disclosed. In the event that a reviewer is unable to be objective about a specific paper, another reviewer will be selected for that paper. Reviewers will not discuss any manuscript with anyone (other than the Project Management Journal® Editor) at any time.

Pointers on the Substance of the Review for Cases

  • Does the case have a well-articulated purpose or learning goal that provides challenges and potential for learning?
  • Does the case inform or improve our understanding of application of theory?
  • Are the concepts clearly defined in the instructor’s manual?
  • Does the instructor’s manual cite appropriate literature and provide proper credit to existing work on the topic? Has the author offered critical and current references? Does the manuscript contain an appropriate number of references?
  • Has the author given proper citation to the original source of all information given in the work or in others’ work that was cited?
  • Is the case written in the past tense at a level appropriate for its target audience?
  • Does the case have clear characters, a coherent narrative, and a logical decision point or ending? Is it interesting?
  • Does the case have a distinct hook that foreshadows the case challenge?
  • Does the instructor’s manual contain all required elements (abstract, knowledge module, target audience and usage, research method, discussion questions and their full answers, theoretical foundations and analysis, a teaching plan, and an epilogue)?

Adherence to the Spirit of the Guidelines

Cases that severely violate the spirit of the guidelines (e.g., papers that are single-spaced, papers that use footnotes rather than conventional referencing formats, papers that greatly exceed page limitations), or which do not clearly fit the mission of the Journal will be returned to authors without being reviewed.