Workfront for Large Projects
March 03, 2017
Workfront for Large Projects
Score 5 out of 10
Vetted Review
Verified User
Overall Satisfaction with Workfront
We are using Workfront to manage our state-specific timelines for a company-wide IT integration project. This is being used specifically for our department, as we are the team managing the state-by-state roll-out of the new products tied to integration. Workfront is being used to help us track our tasks, set-up dependencies, and for being able to report on the progress of a given state at any time.
- Centralize projects in one solution
Pros
- It's easy to copy over a project template to apply to our mutli-state structure.
- Making updates to tasks is easy and intuitive.
- Workfront makes it easy to visually see project status.
Cons
- It needs to be more robust. It's nice that we can set planned and actual dates, but the way Workfront operates with dependencies has caused problems with our use of these fields.
- A drag-and-drop function would be nice when there's a need to re-organize timelines.
- It's kind of frustrating that to update a date for a task with dependencies, you need to go into the actual task to edit instead of being able to click into the dates on the main view and edit. You can change the dates from the main view, but it changes how other dates are calculated.
- Since Workfront hasn't really met our needs, our management team is considering discontinuing our contract. We have not seen the results we expected, and we have had better success reverting back to using a simpler tool. If this happens we have had zero ROI.
- We had to manage two tools since Workfront wasn't meeting our needs, so this impacted efficiency and job satisfaction.
- If Workfront had the functionality we needed, I could see it improving collaboration and capacity.
I haven't been involved in the process to evaluate JIRA, but a demo looked promising.
Comments
Please log in to join the conversation