Recent activity
Subscribe to this feed
Victor Szalvay replied on December 11, 2009 01:45 to the idea "Publish Release Plan" in Danube:
Perhaps you all could help me focus this a bit more.
The original poster talks about "roadmaps" in the sense of PBIs in Sprints. Isn't something like that available today with the PBI module in web reports? I'm not following what's missing from that report that would justify building a new report.
I do understand the follow-on requests focusing around the Epic (Product and Program) level.
Would this essentially be a listing of Epics associated to releases? Would you want to see PBIs in this report as well?
Could someone provide some more detail/focus to help me understand the essence of this request?
Thanks!
Victor Szalvay
ScrumWorks Pro Product Owner
A comment on the idea "Integration - Mecury Quality Center - Defect Tracker" in Danube:
Hi, great question. This item has recently received a lot of votes and so it's moved up the list very recently. The ideas are under consideration are the items we're currently working on or in our roadmap for the current release cycle.
We'll consider this feature for our next release cycle when that time comes. Thanks for your input. – Victor Szalvay, on December 11, 2009 01:28
A comment on the question "Alternative date formats" in Danube:
More specifically, this is related to the server platform's localization profile. If you set the server's location to France, for instance, it will use date formats that are customary there. – Victor Szalvay, on December 11, 2009 01:25
A comment on the idea "Track Task Time spent vs time planned (estimated vs. actual)" in Danube:
Right now we're planning on releasing it as part of 4.3, probably late-January time frame. – Victor Szalvay, on November 30, 2009 17:06
Victor Szalvay posted an update in Danube on November 23, 2009 16:44:
ScrumWorks Pro 4.2 Change LogWe're excited to announce the release of ScrumWorks Pro 4.2. This post supplements the release notes by providing a detailed list of changes.
4.2 Change Log
- Team member allocation report: New task level reporting gives a tabular list of all users in the system and task allocations during a date range. Designed for managers staffing projects/sprints based on available resources. See Topic
- Team member allocation report: Export report to Excel® format with references and formulas to enable sorting and filtering.
- Print-to-Cards: Titles will not truncate. Font sizes dynamically adjust to ensure title fully displays. See Topic
- Print-to-Cards: Description maximized by dynamically adjusting font sizes and dropping other fields in preference of the description. See Topic
- Print-to-Cards: on most platforms the generated PDF will open automatically after being created.
- Web Reports: re-design of the Product Backlog Item module and new filtering based on "status".
- Themes: new filters allow for either additive filtering (PBIs have "all" themes) or "any" of the selected themes. New filters are available in the Product Backlog and Theme-filtered reports. See Topic
- LDAP/Active Directory: configurable sync intervals and better error handling.See Topic
- Fixed display issue on Sprint Detail view where dates would not update when toggling Sprints in the drop-down menu.
- Added team name to web client Sprint drop-down menu.
- Sprint drop-down menu features newest sprints on top.
- Fixed issue affecting attachments in 4.1. See Topic
- Fixed date issue affecting sprint burndown chart. See Topic
- Fixed issue in Web Reports where certain specially formatted characters would be replaced with "?" characters. See Topic
- Fixed Epic description size issue in new MySQL installations. See Topic
- API: there were no API changes this release.
As always, we're looking for your feedback. We encourage you to leave your comments here or post new topics with ideas or issues.
Happy Scrumming :)
The ScrumWorks Team- Team member allocation report: New task level reporting gives a tabular list of all users in the system and task allocations during a date range. Designed for managers staffing projects/sprints based on available resources. See Topic
Victor Szalvay replied on November 21, 2009 00:04 to the problem "SWPro 4.1 - Incorrect Dates on Sprint Burndown" in Danube:
Victor Szalvay replied on November 20, 2009 23:49 to the question "Extended characters mangled in Web Reports" in Danube:
A comment on the idea "Track Task Time spent vs time planned (estimated vs. actual)" in Danube:
Derrek - yes, my bad, I forgot to add that we'd change the editors in the task and web clients to reflect the new "original estimate" field. In essence this is a "report" though. Thoughts?
Using the historical estimation permission makes sense. Thanks! – Victor Szalvay, on November 20, 2009 20:09
Victor Szalvay replied on November 20, 2009 19:28 to the idea "Track Task Time spent vs time planned (estimated vs. actual)" in Danube:
Take people's feedback into consideration, I came up with a quick excel mockup (screenshot attached) for purposes of discussion.
We'd add a new column to the sprint detail area "original estimate", since this is needed now. Notice in the mockup how we deal with multiple users contributing to a single task. We would not have separate "estimates" for each user working on a task since there is only a single task estimate.
Another question:
- We are thinking of using the "original estimate" to mean the first estimate given (we would make task estimates no longer "required).
- Should users be able to modify the original estimate number after the fact? My feeling is no, but I was curious what types of constraints you all would prefer.
Thanks!
A comment on the idea "Track Task Time spent vs time planned (estimated vs. actual)" in Danube:
Derrek, yes this feature would be disabled if timesheets are "off". Thanks for clarifying that. – Victor Szalvay, on November 19, 2009 19:03
Victor Szalvay replied on November 18, 2009 17:54 to the idea "Track Task Time spent vs time planned (estimated vs. actual)" in Danube:
Clarifying question to all you:
What would be the scope of this report? That is, how would you want to limit the data displayed? Obviously there needs to be a limit in terms of time; you don't want to have to wade through historical data each time you view the report, but how else would you want to serve up this data?
Some possibilities:
1. - Filter by team (shows all tasks across all products)?
2. - Filter by product (includes all teams for the product)?
3. - Filter by product and team (includes a single team on a single product)?
4. - For all users (no filter)?
My guess is that you'd want to run this on a single team for a single product (option 3).
Please let me know so we build it right.
Victor Szalvay replied on November 13, 2009 22:58 to the idea "Theme "AND" filter option - including web reports" in Danube:
Victor Szalvay replied on November 13, 2009 22:56 to the idea "Track Task Time spent vs time planned (estimated vs. actual)" in Danube:
Victor Szalvay shared an idea in Danube on November 06, 2009 22:53:
Comment discussions for PBIs and TasksSuggested to me by a partner (Tasktop):
As a ScrumWorks Pro user, I want to add comments to PBIs and Tasks so that my colleagues and I can discuss issues, log questions and answers, and then review them at a later time.
Victor Szalvay replied on October 28, 2009 22:25 to the question "Why did the Earned Value Chart get obsoleted?" in Danube:
Everyone, I should have chimed in earlier on this point.
Here's the deal - when we retired the old Groups model, the report as it was didn't make sense any more (since it was based on the value of the groups).
We intend to bring it back, if there's demand for it. If/When it does come back it will be based on the business value of product backlog items and be limited to a particular release.
Victor Szalvay replied on October 14, 2009 17:38 to the idea "Is it possible to create a backlog item with email?" in Danube:
kbrannen,
While the email-to-pbi feature is definitely cool, it sounds like in your case you are looking for any automated way to create backlog items.
You can do so using the SOAP web services API, which basically uses XML.
Every ScrumWorks Pro server has a SOAP API. You can read more about it right here:
http://danube.com/docs/scrumworks/pro...
You'll need a programmer that knows SOAP, but many organizations leverage this API to build integrations, or simple submission tools like you're envisioning.
Victor Szalvay set one of Caleb Brown's replies as an official response to "MySQL-transfer.exe says Scrumworks server is not stopped" in Danube
Victor Szalvay marked one of Caleb Brown's replies in Danube as useful. Caleb Brown replied to the problem "MySQL-transfer.exe says Scrumworks server is not stopped".
Victor Szalvay posted an update in Danube on October 05, 2009 15:57:
ScrumWorks Pro 4.1 Change LogWe're excited to announce the release of ScrumWorks Pro 4.1. This post supplements the release notes by providing a detailed list of changes.
4.1 Change log
- Prioritize Epics: indicate the priority of Epics using drag-and-drop within the context of a release.
- Epic Budgets: set a soft limit on the amount of work "budgeted" toward an Epic for purposes of a particular milestone.
- API enhancements: full support for epics, programs, and other user requested enhancements. See the API change log for a complete list.
- Support for JIRA 4.0 (BETA)
- Support for Bugzilla 3.4.2.
- Added team name to web client Sprint drop-down menu
- Sprint drop-down menu features newest sprints on top
- Fixed bug showing deleted Sprints in web reports
- Fixed issue where Themes would not refresh to reflect API modification
- Fixed bug where deleted items show up in Product after theme modifications
- Various improvements to upgrade and installation
As always, we're looking for your feedback. We encourage you to leave your comments here or post new topics with ideas or issues.
Happy Scrumming :)
The ScrumWorks Team
Victor Szalvay marked one of Caleb Brown's replies in Danube as useful. Caleb Brown replied to the question "Is it possible to update the JBoss version embedded within a ScrumWorks Basic install?".
| next » « previous |
Loading Profile...
