How to Use Wrike

Wrike is a recommended project management tool in our PMO. We standardized the process as follows: 

Before writing a Project Plan, please following the described steps 

• Create a project folder in Quip using the Small template. 
• Create the project summary page by collecting the following information
• Gather requirements from stakeholders
• Define Scope of the Project
• Define Success
• Create the Project On-boarding document and review with PMO Leard to confirm the project execution plan. 

Create the project plan in Wrike

• Create a new workspace and a new project 
• Add the Work Breakdown Structure
• Define Project Activities - What are the activities that must be performed to create the deliverables of the project
• Estimate the timelines or plan backwards to deliver at a given timeline
• Assign resources to the Project activities 

Adding Tasks

• Per project standardization, we should have the placeholders for all the major tasks in D2P process (refer to D2P blueprint ) . Only for risks or special occasion, we don’t add new task because we are using task turndown rate to tracking the project delivery progress.
• Please review your plan before publishing and consult major changes in your plan with @Jinyu Wang for review. 
• If you plan to run project in Agile (You can refer to Agile blue print) , please
• create Sprint folder with Active, Completed and Backlog folders 
• Split tasks into logical and doable Sprints 

Task Update

• Before closing each task (marking it as completed), please add the project details and attached the related documents. 
• For meetings, please refer to where to find the meeting minute/recordings and presentation. 
• For document creation, please add the links to the documents. 
• For communication with decisions, please record done the email record. 
• For dev issues, please add radar ticket and necessary tech information. 
• Please follow-up with all overdue task in your daily standup meeting and clean up weekly to make sure there is no overdue pass the week.
• Please create a report listing overdue of your projects. 
• If the task change impacts project or sprint plan, seek feedback form PMO Leader before closure of tasks sprint and if needed make changes to the subsequent Sprint and tasks to include changes required if any. Goal should be to deliver success defined and agreed with the stakeholders.

Status Meeting During the status meeting, avoid directly jump into each task and request for status updates. Instead,

• Show the project plan first so the team know where they are from overall project plan perspective and emphasis the project objectives/goals. 
• Review what has been done and what is coming soon (all tasks to be started and due in next week) 
• Please keep annotate the task as you get updates to tracking the conversation. 
• Update the task status as soon as the team get started 
• Void changing due date to shirt the project schedule. Instead, add notes to the project to show delay. If there is a date change, add notes to explain the reason for future reference 
• Copy the meeting minute email to the status meeting task before closing. ​