Tracking Project Slippage
Hey all! So I've seen 2 posts about tracking slippage for a project. If we had Wrike Analytics, I can def see how we could easily track how much the project slipped.
But I'm wondering if anyone has a recommendation for tracking why the project is slipping. So for example, Project A is put on hold because priorities changed and we now need to work on Project B. How are people tracking that or identifying that so we can see the impact of Project B on A, and maybe not just A, but also X, Y, Z, etc...
Hope that makes sense. Interested to see how the community is doing this!! Thanks all!
I don't think we are tracking project slippage. We have a lot of independent projects and usually the reason they get finished late is our team members have too many different projects on their plates.
Our development team utilizes Jira. There are at times when development is off track, so we leverage Wrike Integrate to bring transparency to the development teams activities and are starting to use Wrike Analyze to help us better understand activities between business champions and development. We are just starting to analyze this detail but this helps us understand a potential bottle neck in our process. More to learn.
We used a custom field with drop downs to keep the reasons specified. It's used for reporting purposes.
We don't track project slippage but do we have roadmap meeting once a week to discuss project status, critical tasks and backlogs.
Could you use custom project workflows? with statuses like "Delayed due to customer" etc?
We don't track project slippage through Wrike but my team meets every morning to discuss project status and any issues with meeting our milestone dates.
I like your idea Shelly Erickson! We don't officially track project slippage but we know it almost always falls into two categories: client responsiveness, and team capacity. However it would be useful to document this, and have awareness of other under-the-radar causes we may miss when looking back on projects.
We use a combo of what Aloi and Debbie posted. The meeting each week is with the two managers and director. We also make sure to keep the project updated with the correct workflow. It is very easy in our meetings to see where/why the project is how it is.
With small, short term projects (1-3 months) we use custom fields to specify reason for delay "Waiting on client, waiting on Department" etc. I've recently updated project workflows to do the same and its been a huge help.
We have a workflow with two possible end stati. Completed and Did not finish (beside some special like Did not work). If a planned date is missed the task is set to did not finish and a new task has to be generated. Both tasks will be linked. So we can filter for did not finish and see what tasks have been delayed.
Also we made a custom field for start and end date which is filled by a bot automatically. The end date custom field is changed every time we change the end date of the task. From custom fields you can get a history and so we can monitor when a task date has been changed.
An automatic way to monitor I can't imagine. At some point you need people to do the work I think.