{"id":184,"date":"2016-10-03T10:45:46","date_gmt":"2016-10-03T10:45:46","guid":{"rendered":"https:\/\/www.michaelagreiler.com\/blog\/?p=184"},"modified":"2019-02-17T19:09:17","modified_gmt":"2019-02-17T18:09:17","slug":"checklist-tasks-program-chair","status":"publish","type":"post","link":"https:\/\/www.michaelagreiler.com\/checklist-tasks-program-chair\/","title":{"rendered":"Checklist: What you need to do as a Program Chair?"},"content":{"rendered":"\n

If you have been asked to be a program chair for the first time, or whether you already served as one, this checklist helps you to never forget what you need to do as a program chair.<\/p>\n\n\n\n

Beginning 2015, I was asked to serve as a program chair for the first time for the IEEE International Working Conference on Source Code Analysis and Manipulation<\/a> (SCAM) 2016. As I haven’t done this before, I only had a vague idea which tasks and responsibilities a program chair has. So I started to ask experienced colleagues as well as the program chair of the previous year. Many thanks to Margaret-Anne Storey, David Lo, Chris Bird and my program co-chair Gabriele Bavota!<\/p>\n\n\n\n

\"a
Checklist of a program chair. Keep track of all tasks and responsibilities.<\/figcaption><\/figure>\n\n\n\n

Over the period of serving as a program chair, I wrote down every task I had to perform, and now want to share this list to ease the way for other new program chair, or even as a checklist\/ reminder for experienced program chair. I am also currently preparing examples for the emails and other documents that have been created and will upload and link them over the course of the next weeks. Click here to download the checklist as PDF<\/a> that shows what a program chair does!<\/p>\n\n\n\n

  1. \n

    Select qualified PC members to invite<\/h3>\nFor your selection you can use the PC members of the previous years as a basis, but you should add a high enough number of new PC member with the right expertise. Aim at a balanced PC in respect of gender, location (Us, Asia, Africa, Europe..), junior and senior people etc.<\/li>
  2. \n

    Send PC for approval<\/h3>\nSend this list to the general chairs for approval followed by sending it to the steering committee for approval. Make modifications if needed.<\/li>
  3. \n

    Schedule all major deadlines.<\/h3>\n
      \n
    1. Deadline for submission (abstract and paper)<\/li>\n
    2. Deadline for review and discussion phase
      Remember that some reviewers may be late. So plan a little bit of buffer time.<\/li>\n
    3. Deadline for camera-ready version<\/li>\n
    4. Deadline (internal) for sending to publisher<\/li>\n<\/ol>\n<\/li>
    5. Send invitation to PC<\/h3>Search for email addresses of PC members and invite them to the PC. Mention already in the email the workload to expect as well as the deadlines.<\/li>
    6. Send PC invitation reminder<\/h3>After a while send a reminder to invited PC members who have not responded, and extend the invitation to further PC candidates if not enough accept.<\/li>
    7. Find keynote speaker<\/h3>This might be optional, but if asked brainstorm about fitting keynote speakers, make a list and discuss the keynote speakers with general chair et al.<\/li>
    8. Select and invite keynote speaker<\/h3>Have a backup speaker in case the invited cannot attend.<\/li>
    9. Prepare a Call for Paper (CFP)<\/h3>The one of the previous years can serve as a draft. Here is the SCAM 2016 CFP<\/a> for example<\/li>
    10. Announce conference<\/h3>Work with publicity chair to make conference public. You might want to send an email to SEWORLD and also advertise the conference on other conferences. Use personal network. Twitter and\/or blog about it.<\/li>
    11. Prepare\/configure submission system<\/h3>Configure for example EasyChair in the desired way.<\/li>
    12. Watch submissions coming in<\/h3>Are people in need for a deadline extension? Do you want to grant this? If so, communicate this on website and to authors that have already submitted.<\/li>
    13. Close submission website<\/h3>\n<\/li>
    14. Send bidding email<\/h3>Send an email to the PC that explains them how to bid on papers. Don\u2019t forget to include\/calculate a minimum number of papers that the PC member should bid on.<\/li>
    15. Perform desk rejections<\/h3>This might apply to too long submissions, or if only an abstract has been submitted. Also, some papers might not fit the topic or are sheer unreadable\/of too low quality.<\/li>
    16. Assign papers<\/h3>Assign papers to the PC members, while being aware of conflicts of interest. EasyChair can help with a first draft assignment which then can be reworked.<\/li>
    17. Send assignment email<\/h3>Send email with the list of assigned papers to each PC member.<\/li>
    18. Split papers, in case of two PC chairs<\/h3>This is optional. First understand the conflict of interests, and then you might split the papers among the PC chairs. For example, odd versus even numbers, except for conflicts. Then, each PC chair leads the discussion for the papers assigned. Obviously, PC chairs can discuss papers with each other, but this will help to give some accountability.<\/li>
    19. Send review reminder<\/h3>Send a reminder to the PC members about their missing reviews. Close to the deadline you might want to send a second one \u2013 only to those that still have missing reviews (EasyChair can help with this).<\/li>
    20. Email discussion start<\/h3>Let PC know that discussion phase has begun.<\/li>
    21. Moderate the discussion phase<\/h3>During the discussion phase the PC chairs act as moderators. You will have to trigger discussions, and guide the reviewers to hopefully come to an agreement on the decision of the paper. A good way to start the discussion is to look at the positive elements of a work.<\/li>
    22. Make decisions<\/h3>First tentative, ask for feedback, then final.<\/li>
    23. Handle disagreement<\/h3>For a few papers, the reviewers might not come to an agreement, or you also might disagree with the reviewers\u2019 assessment. Such cases are a bit tricky, because you must decide whether this paper will be accepted or rejected. In such situations, when I felt torn apart, an advice I got from a mentor of mine helped me. He said: \u201cRemember that the community trusted in your abilities to make the right decision. That\u2019s why they asked you to serve as program chair. So, take the feedback of the reviewers seriously, but also do not forget that the final decision is the decision of the program chair(s).\u201d<\/li>
    24. Send thank you email<\/h3>Send the PC a thank you email to appreciate their hard work.<\/li>
    25. Send email decision<\/h3>Send an email to authors informing them about the decision. In case of an acceptance, inform them about the next steps needed for the camera-ready version.<\/li>
    26. Letter of PC Chair(s)<\/h3>Write a letter for the front of the proceedings.<\/li>
    27. Create program<\/h3>Decide on presentation format (e.g., 20 min presentation, 10 min discussion, 3 presentation per session) and group papers with similar topics together. Incorporate needs of steering committee for meetings and time slots.<\/li>
    28. Accepted papers to proceedings<\/h3>Send list of accepted papers and the letter of the PC chairs for proceeding creation.<\/li>
    29. Select the Best Paper<\/h3>Ask PC for feedback and incorporate this into the decision.<\/li>
    30. Select Best Reviewer<\/h3>Optional: To show gratitude for the work PC member do, it is nice to also select a few PC members that did outstanding work.<\/li>
    31. Select and invite session chairs<\/h3>Keep the needed expertise of the session chairs in mind, and make sure they will attend the conference<\/li>
    32. Create and print the awards<\/h3><\/li>
    33. Opening slides<\/h3>Prepare the slides that are used during the opening session. These might contain some information on number of submissions, acceptance rate.<\/li>
    34. Select papers for journal extension<\/h3><\/li>
    35. Invite authors to journal extension<\/h3><\/li>
    36. Find reviewers for invited papers<\/h3>Think about the reviewers’ expertise. An option is to add a reviewer who already reviewed the paper before.<\/li><\/ol>\n\n\n\n

      Obviously, a few extra tasks are missing. Reminder emails, 1-1 conversations with PC, authors, steering committee, web or publicity chairs which you will have to handle on demand.<\/p>\n\n\n\n

      Something general missing? Leave a comment. Also, leave a comment if you have some good strategies or tips for some of the tasks. I’ll update the list accordingly.<\/p>\n\n\n\n

      Happy reusing!<\/p>\n

      Updated on February 17th, 2019 <\/p>","protected":false},"excerpt":{"rendered":"

      If you have been asked to be a program chair for the first time, or whether you already served as<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"spay_email":"","jetpack_publicize_message":""},"categories":[38],"tags":[],"jetpack_featured_media_url":"","jetpack_publicize_connections":[],"jetpack_shortlink":"https:\/\/wp.me\/paHqvV-2Y","jetpack-related-posts":[{"id":161,"url":"https:\/\/www.michaelagreiler.com\/time-is-ticking-deadline-for-scam-2016-approaching\/","url_meta":{"origin":184,"position":0},"title":"Source code analysis and manipulation \u2013 Conference Deadline","date":"May 18, 2016","format":false,"excerpt":"With only one month to go, time is ticking to submit to SCAM 2016 the\u00a0International Conference on Source Code Analysis and Manipulation. The conference is suited for researchers and practitioners that are interested or work on\u00a0theories, techniques, and\/or applications that concern analysis and\/or manipulation of the source code of software\u2026","rel":"nofollow","context":"In \"Research\"","img":{"src":"","width":0,"height":0},"classes":[]},{"id":5371,"url":"https:\/\/www.michaelagreiler.com\/security-code-review-checklist\/","url_meta":{"origin":184,"position":1},"title":"Security Code Review Checklist to find Security Vulnerabilities","date":"February 9, 2021","format":false,"excerpt":"Security code review checklists can help developers focus on security vulnerability and privacy issues. A security-focused mindset is important, as we can see a shift left in the security field. This means that developers nowadays have to know more about security than ever. But, do you know the OWASP Top\u2026","rel":"nofollow","context":"In \"Code reviews\"","img":{"src":"https:\/\/i2.wp.com\/www.michaelagreiler.com\/wp-content\/uploads\/2021\/02\/image.png?fit=989%2C849&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":3151,"url":"https:\/\/www.michaelagreiler.com\/code-review-checklist-2\/","url_meta":{"origin":184,"position":2},"title":"A Code Review Checklist - Focus on these 10 Important Topics","date":"August 13, 2019","format":false,"excerpt":"A code review checklist, as well as clear rules and guidelines around code reviews, can make your code review practice so much more beneficial to your team and significantly speed-up code review times. So make sure you focus on the essentials with this code review checklist!","rel":"nofollow","context":"In \"Code reviews\"","img":{"src":"https:\/\/i2.wp.com\/www.michaelagreiler.com\/wp-content\/uploads\/2019\/08\/Code-Review-Checklist_twitter.jpg?fit=814%2C512&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.michaelagreiler.com\/wp-json\/wp\/v2\/posts\/184"}],"collection":[{"href":"https:\/\/www.michaelagreiler.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.michaelagreiler.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.michaelagreiler.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.michaelagreiler.com\/wp-json\/wp\/v2\/comments?post=184"}],"version-history":[{"count":1,"href":"https:\/\/www.michaelagreiler.com\/wp-json\/wp\/v2\/posts\/184\/revisions"}],"predecessor-version":[{"id":813,"href":"https:\/\/www.michaelagreiler.com\/wp-json\/wp\/v2\/posts\/184\/revisions\/813"}],"wp:attachment":[{"href":"https:\/\/www.michaelagreiler.com\/wp-json\/wp\/v2\/media?parent=184"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.michaelagreiler.com\/wp-json\/wp\/v2\/categories?post=184"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.michaelagreiler.com\/wp-json\/wp\/v2\/tags?post=184"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}