If your organization has such a requirement then a recurring task will be helpful in your resource pool utilization. Adding recurring activities for a status meeting only adds to the administrative burden and requires the project manager to track additional tasks that don’t impact the project’s critical path. I prefer to setup my project management governance routines to include a weekly status meeting using Microsoft Outlook or corporate calendar system. Depending on the complexity of the launch, you likely have status meetings every day if not multiple times during a given day. I’ve never missed a launch date or postponed a launch because I skipped a team status meeting during a project launch. The main reason is these are support tasks that don’t fall on a project’s critical path. My preference is to avoid recurring tasks for a weekly status meeting in a project schedule. The question was “What are the pros and cons of using a recurring task in Microsoft Project versus scheduling individual tasks for a weekly status meeting?” I recently received an email regarding the use of recurring tasks in Microsoft Project.
