Teams running any form of agile methodology in Wrike have probably run into the burndown chart question. Can Wrike show you a burndown? The answer is not natively, in the traditional sense.
The feature that most directly addressed the burndown request is Baselines in the Gantt Chart. A baseline lets you compare your project’s current schedule against the schedule it had on a specific date in the past. This gives you the planned versus actual comparison, but it is a schedule comparison, not a task completion count over time.
Wrike Analyze expanded significantly, and with custom widgets you can build charts that show task completion rates over time, project progress against targets, and various performance metrics. These can approximate burndown-style reporting, but they require configuration and are not the out-of-the-box burndown chart that agile teams are used to seeing. Wrike is a good collaboration tool, but it is not well-suited for managing complex projects using certain agile methodologies like Scrum. For teams where burndown charts are a main part of how they manage sprint progress, that assessment still has merit.
Teams that run agile processes in Wrike and need to track sprint progress typically take one of a few approaches. They build custom dashboards that show task completion counts, overdue work, and remaining items in the sprint folder. They use Wrike Analyze to build progress-over-time charts that approximate a burndown view. They supplement Wrike with a separate reporting tool for sprint-specific metrics and use Wrike for task management alone.
A team that needs burndown charts as a deliverable of the sprint process will find that Wrike is not the strongest fit right now. A team that needs task management, workflow tracking, and collaboration during a sprint, and is willing to build custom reporting in Analyze, will find that Wrike can support agile work effectively.