Welcome to the Collaborating on project support items section. Here are the core actions for collaborating on project support items that are available to your project and team to maintain the non-schedule details for the project using Project IQ:

1. Manage project issues
   
2. Manage project risks
   
3. Track project decisions
   
4. Record and manage change requests
   
5. Capture lessons learned
   
6. Manage project documents
   

None of these are mandatory and you may skip some, or even all, based on your project delivery requirements.


Download Job Aid: Collaborating on project support items

Important: If you are not familiar with Project IQ, we recommend you review the Project IQ and Work IQ Overview page. It will provide you with a working knowledge of the Project IQ area.

Once the project has moved into the Executing phase, all the actions undertaken during Planning phase are ongoing and will be completed as appropriate on each project. The focus at this stage is to help you and your team maintain any and all of the non-schedule-based support items.

Here are a few practical tips:

• Consistent with the Project Management Institute’s (PMI) definition, use Issues to track and manage all current challenges, or opportunities, that could impact the project’s successful conclusion.  You can identify, prioritize, assign, and track by due date all issues to help ensure they are resolved in a timely fashion.

• Also consistent with PMI’s definition, use Risks to track and manage all future challenges, or opportunities, that could impact the project’s successful conclusion.  Like Issues, you can identify, assign, and track by due date all risks to help ensure they are managed in a proactive manner.  Since risks have not yet occurred, you can also manage them based on likelihood, consequences, costs, and trigger dates to help prioritize which risks should be managed more closely and actively.

• Decisions can be used to identify and manage key decisions required to move the project forward, or to record decisions made that do not impact the scope, cost, or schedule (i.e. Do not require a change request). We believe that using Decisions allows the project to be more flexible while still ensuring that a record (with formal approval) exists for all important decisions. 

• Change requests on the other hand typically involve changes to the project scope, budget, and / or schedule and therefore require more detailed management.  In addition, to effort, cost, and schedule impacts from the change, you can also record impacts the change has on other areas and formally track and manage the approval (or rejection) of the change requests on your project. 

• Lessons learned allow you (and your team) to record valuable knowledge gained that may be helpful for future projects.  Commitment to capturing lessons learned during project execution helps the organization drive continuous process improvement.

• And finally, Project IQ leverages SharePoint document management to ensure that all relevant project documents, as well as formal project deliverables are available to all team members in a centralized location.
  

---

_{Disclaimer: Some images in the instructional video and text instructions contained herein may appear different from (or not available) in your organization’s Sensei IQ instance due to specific custom configurations and/or continuous solution updates. Ensure that you are already an enabled user in the Sensei.IQ for Project application and check out the What’s New page. Contact your system administrator for any assistance.}