Burndown charts & improved reporting
Its great to have the recently added Kanban "Board" view to support Agile practices, and request development of reporting features to support this such as burndown charts.
Having used Wrike for a few months now, there is much about it that I find to be really good, but the reporting is by far the weakest feature set.
Love to see that improved, and if it were better I'm sure we'd see a wider group interested to use the tool within our company that currently don't and won't for understandable reasons.
Hi Lawrence, thank you for posting your suggestions! First of all, in case you haven't had a chance to try it out yet, I wanted to mention the Analytics functionality which includes a Work Progress chart - this might include some of the functionality you're looking for. Also really interested in learning about the types of improvements you'd be interested in seeing, and what kind of functionality your team is missing at the moment.
The addition of a standard set for scrum workflows and reporting would allow greater uptake of the product.
Would love to see the ability to add story points and then see a burndown chart.
Would also love to see more features for working with scrum. Story points, burndown chart, business value, sprint and release numbers. Maybe you guys can get/copy some cool stuff from Targetprocess. They did some cool stuff in this case.
We are having a few issues here.
We are looking for Burndown charts as well, as we use scrum for our framework. Dev is complaining and asking to go back to using TFS so they can see their workload better. As of right now, I have to manually calculate our burndown for each user.
I see that we can see the "workload" in the workload view but we are limited to only seeing the users in wrike, not the collaborators which we do have outsourced developers who work with our in house team who do not need a user account. Also, the data needed to create our burndown chart doesn't show here. We are also limited in the workload view because we cant see the necessary data for our 2 week sprints. We don't use the duration field because it sets mandatory dates which we dont want unless we mark it as "backlogged" which we dont want either. If we mark the start and end time for each task for the beginning and end of each sprint, the duration changes to the 14 day period which is also inaccurate for measuring time, esp if the task only takes a few hours to complete.
A feature (if this exists somewhere please let me know!!) that allows us to view how many hours each user has accumulated from tasks within in a folder would be something that would help tremendously. It would calculate their workload with each task that gets assigned to them. Then, as they complete tasks, this number goes down. Further implementation to the feature could included information letting the user know how much time is left in the sprint compared to how much time they still have within their workload.
besides the things mentioned above - I would love to connect stories with tasks. Currently there is only subtasks related to waterfall but not scrum.
+1 on this. I'm not using story points, but I want a burndown report at the task level (assume 0 active tasks at complete, etc).
This is seriously annoying to calculate. Have to export to a spreadsheet.
Work Progress and existing reports do NOT fill this need.
+1 this would be great.
Yes on the burndown chart!
Hi @everyone, thanks for sharing your feedback 🙂 I wonder if Wrike's Timesheets can help you check on workload. They provide an overview of tasks you worked on during a given week and time you spent working on them. Please let me know if that functionality is what you are looking for.
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Hi Lisa, I was hoping for a feature that would allow a time value to be added to a task. Ex: Task A is estimated at 2 hours, Task B, 10 hours. Then a burndown chart would aggregate the time and task data vs a given period of time.
Does that make sense?
@James, thanks for providing details here, it really helps our Product team when they are reviewing this feature suggestion!
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
I just want to add our strong interest in having implemented some Agile project management tools in Wrike, like stories, burndown charts, etc...
At least, we really need to have some kind of Sprint task board, like the following picture. I think this thread has already summarised most of the missing elements to get there.
Is there any commitment from Wrike to implement an Agile methodology?
Hey @Marco, thanks a lot for your input!
I think the Board View partially does what you describe:
I'd be very interested to hear whether you're using it 🙂
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Hi Lisa,
the board view is indeed very far from the example I provided (taken from a document, not from a system, it would have been unpolite). The board view lacks story lanes, burndown chart and other details that anybody familiar with scrum knows to be essential.
You can actually find many systems implementing the scrum agile methodology. Wrike is unfortunately far from being an effective tool to implement such methodology. Reading through the Wrike portal, it's since a while users are submitting recommendations on how to improve Wrike in the PM area, especially with agile methodologies. Frankly speaking, I've seen no progress in the last year. This is forcing people like me to start looking elsewhere (or just discard Wrike in their software selection). That's a pity.
Anyway, thank you very much for your feedback ! Regards,
Marco.
Big +1 to this whole thread.
Wholeheartedly agree that Wrike is lacking in a lot of basic Agile functionality, tons of lost opportunity so far but hoping the Product Team can start to deliver some basics! I have just moved my team, mainly software developers, to Wrike from Jira. Was looking closely at the Jira/Unito integration, but a big flaw - Projects map to Projects! As I'm sure most of the participants in this thread would agree, a Jira "project" and Wrike "project" are fundamentally quite different. Epic to Project is much more logical, but at its heart a Jira Epic is nothing more than a task with subtasks, so I understand why Unito can't map in a Wrike Project to a Jira Epic in the backend/API. And that approach of Jira, to basically use a task as a way to track full projects, let me away and over to Wrike, which has a terrific approach with the ultimate flexibility and capability to nest unlimited projects and folders.
Some ideas here for the Product Team:
- If you could give us a board view that basically "flipped" the table view, which shows a full nested breakdown of tasks and folders as high as Space-level, we'd have a great User Story Map. Columns would be folders containing tasks or projects as features. This would only require the ability to configure a board to sort by folder or project, and not status, so hopefully a relatively easy implementation.
- Task linking that has been requested across the community, such as here: https://help.wrike.com/hc/en-us/community/posts/115002961109--Linking-to-projects-tasks?flash_digest=86fd716abda45db57376b83df642233dc82a51b4 Staple of Jira, GitHub, TargetProcess, etc. This would not help with Sprint Planning, but avidly used by agile teams and again, something that would appear to be easy to implement vs. full on Sprints or new task types in Wrike such as Stories.
- Native integration with Github/Gitlab/Bitbucket or others. Simple stuff like mirroring updates to statuses in the Repo tool with updates in Wrike. Or some visibility to the issue in the Repo tool within Wrike, and not just a link that Unito offers. Clickup and Hive have this and again it seems an easy addition via API integrations. Would go a long way to having dev teams buy into using Wrike as their issue trackers.
- Swimlanes in boards that could be based on folders or projects that teams would use as Sprints. This would give a great way for teams to drag tasks into requisite folders that would represent a sprint during Sprint Planning Meetings, right on a board.
- I agree that we need to see the ability to estimate a task, then have time tracked against it in a true feature, and not a workaround via Custom Fields that you guys talk about frequently, for example here: https://help.wrike.com/hc/en-us/community/posts/115000204949-Looking-for-a-way-to-estimate-time
You have a great timer already built into tasks. You should be able to have a true estimation field in the task (that's much more prevalent in the view than the custom fields, which you can't see without mousing over right now), and then when you start the timer and log time, it goes against that estimate. With this in place, Burndown and Cumulative Flow would be easy for your system to generate. Without native estimation, the time tracker is very limited.
Hope that's useful guys and counting on seeing some good Agile stuff for my team very soon!!
Agree with the above posts, especially agile progress reports. We can fit our agile process into Wrike, but we need the reporting as well that compliments the methods. With many industries moving towards the agile methodology, it would benefit Wrike to accommodate the agile reporting needs.
+1 for this thread. Wrike is really awsome but it lacks the (full) Agile way of working.
+1 for this thread from me as well. I remark the importance of having solid support for some Agile basic tools.
Hey everyone, thanks for all of your input here. It's been passed on to our Product team, as soon as I have an update for you, I'll let you know 😊
Strong +1 on this. Not having burndown charts is absolutely crazy to me. We really need this.
Thank you for this feedback Michael Harker!
impossible to work like this - moving back to Jira ?
All features you're developing are delivered through add-ons, similar to Resources: you started it as a "lab" stuff to get users' feedback for free and now you're asking for additional money to deliver the result of the experimentation. It's very disappointing.
I definitely have to look at somewhere else to find a modern project management system.
Yes I agree Marco Caciotti it is getting very pricey, and Wrike doesn't have much in the way of native integrations - Slack, and that's it. Could really use some of the stuff described in this thread.
Thanks!