You can try Scrumwise without any kind of signup. Just click on the green "Try now" button, and you will be in the tool, in an account created for you on the fly.
If you like what you see, you can keep your account by clicking the link at the top of the page in Scrumwise. Then enter your name, email address, and the password you would like to use. After that, you can use Scrumwise for free for 30 days, with no obligations and no credit card needed.
Yes, you can close your account at any time. You won't be billed anymore after you do that. To close your account, see here.
Go to the "Your company account" tab in the settings of Scrumwise. Then click "Change your billing info". You must be administrator in Scrumwise to do this.
Changes to your billing address will have effect starting from your next invoice. Changes to your credit card details will have effect from the next time we charge you for an invoice.
Yes, we will send you an invoice each month, by email. It's a legally valid invoice that you can use in your accounting. If you're based in the EU, the invoice uses the EU VAT handling rules and no VAT is added, except if you're based in Denmark.
By default, the invoice mails will be sent to the person that is selected as the contact person in Scrumwise. You can change this in the "Your company account" tab in the settings. The invoice mail settings are located in the invoice section of the tab.
An invoice mail contains a secure link directly to the invoice, so that the invoice can be viewed and printed directly from the mail without having to be a user in Scrumwise or having to log in.
You can also see all of your invoices in the "Your company account" tab in the settings.
Scrumwise is highly secure and ensures full privacy of your data. Scrumwise is hosted in a fully secure and firewalled production environment at Amazon AWS, and Scrumwise uses all best practices in security. For example, all communication is done via HTTPS, your password never leaves your own machine, and your data never leaves Amazon AWS in any other ways than when a user in your account logs in and accesses it in Scrumwise.
Also, at the software level, there are multiple levels of protection built into Scrumwise that prevent anybody from accessing other data than their own, including for malicious purposes. This includes complete checks of authentication, authorization, and validity of all requests made to the Scrumwise servers. And it includes low-level protection mechanisms server-side that prevent access to data in other accounts even in case of software errors at the higher levels.
No, Scrumwise takes great care to protect you against any kind of data loss. All data in Scrumwise is protected by four separate backup/durability mechanisms.
First, Scrumwise uses Amazon's RDS database service with multi-availability-zone deployment, which means that the database is synchronously replicated in two separate physical locations in Amazon AWS, so that no data will be lost if a database server is lost in one location.
Secondly, Scrumwise uses Amazon RDS's built-in backup mechanism that makes it possible to restore the database to any point in time from 35 days back and up to about 5 minutes ago, at any given time.
Thirdly, daily Amazon DB snapshots are taken of the database, and these are stored by Amazon in their S3 data storage service, which provides mission-critical data durability (with guaranteed 99.999999999% durability).
Finally, daily MySQL-level backups are taken of the database, still from inside Amazon AWS, and these are also stored in Amazon S3.
Yes, Scrumwise complies with all requirements and best practices for secure credit card processing. Scrumwise is certified PCI DSS compliant and is scanned regularly by SecurityMetrics. Your credit card information is securely stored and processed by CyberSource, the world's leading payment gateway, owned by Visa.
We typically do planned maintenance every 2-3 months. The maintenance is typically done on a Saturday, in a window from 9 am to 5 pm GMT. During this period, Scrumwise will be offline and unavailable while the maintenance is being performed.
We will announce planned maintenance on Twitter, and you can also get notified by email, if you'd like. You will also be notified some hours in advance directly in Scrumwise. Before maintenance starts, you will get a final notification in Scrumwise and all of your changes will be saved automatically, and Scrumwise will go into maintenance mode. So, you'll never lose any changes as a result of a maintenance.
You can get notified by email when there is upcoming maintenance, new features, etc. You can configure this in your personal account page in the settings in Scrumwise.
You can also get notified by following Scrumwise on Twitter.
After each release, we'll also post information about the new features on our blog.
We provide free support via email. In many cases, you'll have an answer within an hour. Just write us at firstname.lastname@example.org.
Also, we often provide live chat support, typically during business hours in the US and Europe.
Yes, you can export backlog items or tasks in two ways. You can copy backlog items or tasks from Scrumwise directly into a spreadsheet using standard copy & paste. This is useful for ad-hoc analysis and reporting. To do this, select the backlog items or tasks in Scrumwise, copy them by pressing Ctrl + C / Cmd + C or using the right-click menu, and then paste them into a spreadsheet of your choice.
You can also export backlog items or tasks to CSV files. To do this, select the backlog items or tasks, and select "Export these items" or "Export these tasks" from the right-click menu.
Yes, if you're using detailed time tracking in a project, you can export your time log to a CSV file using the "Export all" button at the bottom of the "Time" tab. If the "Time" tab is not shown, click the "More" link at the right side of the tabs, and select the "Time tracking" checkbox.
You can also copy time entries from Scrumwise directly into a spreadsheet using standard copy & paste. To do this, select the time entries in Scrumwise, copy them by pressing Ctrl + C / Cmd + C or using the right-click menu, and then paste them into a spreadsheet of your choice.
You can also export selected time entries to CSV files. To do this, select the time entries, and then select "Export these time entries" from the right-click menu.
getDatacall in the API. This will give you all projects in your account, including their ids.
You can get the data for each person by asking to get the persons and deleted persons included
Data object that is returned from
getData method. You do that by specifying the
Data.deletedPersons in the
getData, like this:
Yes, Scrumwise integrates with source control tools, like GitHub. See here for more on this.
Scrumwise also has an easy-to-use API that you can use to integrate to other tools. You can find the API documentation here.
Scrumwise does not yet have built-in integration to other tools than source control tools, but this will be added in the future.
Yes, Scrumwise can integrate to source control tools. This way, you can include information for Scrumwise in your commit messages, and Scrumwise will automatically update itself using that information, without you having to open Scrumwise at all.
For now, Scrumwise has support for integrating to GitHub, but other tools will be added later. If there is a particular tool that you would like us to integrate to, let us know at email@example.com.
To set up an integration to your source control tool, go to the "Your company account" tab in the settings of Scrumwise. You must be administrator in Scrumwise to do this. Go to the "Settings" page in the "Your company account" tab, and click on the link "Add an integration to a source control tool". Select your source control tool, and click "Add this integration".
Now, open the popup dialog for the integration you've added (for example, by clicking on the name of the source control tool). In the popup dialog, copy the webhook URL. Then go to your source control tool and configure it to use this webhook URL for commits. For GitHub, here is how to do this.
Your integration is now set up, and you can start including information for Scrumwise in your commit messages.
To include information for Scrumwise in your commit messages, first make sure that you are using the same email address in your source control tool and in Scrumwise. Otherwise, Scrumwise will not be able to determine who did the commit.
Here is an example of a commit message that references a backlog item in Scrumwise:
Added login page [Scrumwise item #342]
And here is a commit that references a task in Scrumwise:
Added help text [Scrumwise task #679]
You can find the id of a backlog item or task in the upper right corner of the popup dialog for the item or task.
When you reference a backlog item or task like this in your commit message, Scrumwise will register the commit in the backlog item or task. You can then see a list of commits in the popup dialog for the backlog item or task.
You can place the info for Scrumwise anywhere in your commit messages. Also, you can include references to multiple backlog items and tasks in the same commit, like this:
Performance optimizations [Scrumwise item #259] [Scrumwise item #476] [Scrumwise task #893]
Note that if a backlog item has tasks, you cannot reference the backlog item itself in the commits - you must reference the individual tasks instead.
You can also specify how much time you have used, like this:
Added login page [Scrumwise item #342, used: 2.5 h]
Scrumwise will then register the used time in the backlog item or task. Scrumwise will also reduce the remaining time in the backlog item or task, with the same amount of time, except if your project is configured to use a different unit for remaining time.
As unit, use "h" for hours, "d" for days, and "p" for points. Or, spell out the unit completely, for example "points". The unit must be the same as the unit used for tracking used time in the Scrumwise project. You can also leave out the unit, but including it is safer, since otherwise you might forget which unit it is.
You can also specify the new status of the backlog item or task, like this:
Added login page [Scrumwise item #342, status: Done]
You can set the status to "In progress", "To test", or "Done". The case doesn't matter, so you can use "done" instead of "Done", for example.
Here is an example that references both a backlog item and a task, and specifies the used time and new status for each of them:
Improved user experience [Scrumwise item #612, used: 2.5 h, status: To test] [Scrumwise task #938, used: 1.5 h, status: Done]
Scrumwise uses the email address to map a user. So, you should make sure that a user that you want to map from the source control tool to Scrumwise uses the same email address in the source control tool and Scrumwise.
If a user does a commit and Scrumwise cannot map the user to a Scrumwise user, Scrumwise will send an email about this to the email address that the user has in the source control tool.
Go to the "Your company account" tab in the settings and find the source control integration that you would like to remove. Open the popup dialog for the integration and click "Delete".
When you delete a source control integration, this will immediately cause all future commits that use this integration to be ignored by Scrumwise. So, this is a secure way to revoke an integration and its associated webhook URL, even if you do not remove the webhook URL from the source control tool (but it's a good idea to do that anyway, of course).
Administrators can do the following things that other people cannot: Add users, delete users, add and remove administrator rights, edit properties on other users, view and edit the company account, export all data in the account, and edit and delete comments made by other people.
Also, if access control on projects is turned on, there are some additional things that only administrators can do: Add projects, delete projects, rename projects, reorder projects, and control who can access each project. Also, administrators always have access to all projects in the account.
If you're an administrator yourself, you can add and remove administrator rights in the popup dialog of each user. Click on the user's name to open the popup dialog, and then click "Add administrator rights" in the bottom of the dialog to make him administrator. And click "Remove administrator rights" to remove the rights from somebody who is administrator.
There must always be at least one administrator, and Scrumwise will ensure that this is always the case, no matter what.
Yes. By default, everybody has access to all projects in the account. But if you turn on access control on projects, you can control who can access each project. For example, this is useful if you want to give your customers access to Scrumwise, and only want each customer to see his own projects.
You must be administrator to control the access to projects. To turn on access control on projects, go to the "Your company account" tab in the settings. In the "Settings" page of the tab, click "Turn on access control on projects". You can then control who can access each project by going to the People tab for the project. Administrators always have access to all projects.
When access control is on, only administrators can add projects, delete projects, rename projects, and reorder projects.
Note: If you give somebody access to a project while they are logged into Scrumwise, they must reload Scrumwise to see the project. Also, there are a few cases where a person will be logged out of Scrumwise automatically and will have to log in again. This happens if you remove the person's access to a project, or make the person administrator and that person didn't already have access to all projects. It also happens if you turn off access control on projects entirely, and the person didn't have access to all projects while access control was on. So, make sure you don't make these changes at a time where it will annoy the person to be logged out.
If your changes cannot be saved, Scrumwise will show a warning icon in the upper right corner of the window. After a short while, Scrumwise will also show a warning popup saying that your changes have not yet been saved. While this happens, Scrumwise will continue to attempt to save your changes, and as soon as this succeeds, it will show a small checkmark instead of the warning icon.
You can try this yourself by disconnecting your network connection after you've logged into Scrumwise. Try making changes while you are disconnected, and wait a little to see what happens. Then connect to the network again and see what happens.
Whenever somebody makes a change in Scrumwise, the change will be propagated to all other online users in typically less than a second. So, other users will see your changes in almost realtime. Also, while you are making a change, such as dragging a backlog item or editing a field, Scrumwise will indicate this to everybody else that are logged in, so that they can see what you are doing, as it happens. This way, you can easily see if somebody else is editing a field that you would like to edit as well.
You can try the realtime updating yourself by opening multiple windows with Scrumwise. The realtime updating will happen between those windows as well, even though you are the user logged into all of them.
No, not directly, you have to use a different email address in each of your Scrumwise accounts.
But, you can use the following trick to create as many email addresses as you need that all point to your real email address: Add a plus sign ("+") and any combination of words or numbers just before the '@' character in your email address. For example, if your email address is firstname.lastname@example.org, and you would like to use that email address in three different Scrumwise accounts, you could use the email addresses email@example.com, firstname.lastname@example.org, and email@example.com.
Scrumwise will remove the part after the plus sign before sending mail to you, so all mail will be sent to your real email address (for example, firstname.lastname@example.org). But when you log into Scrumwise, you can use the part after the plus sign to select which account to log into. This works regardless of whether your own mail server supports the plus notation, since Scrumwise removes the plus part before sending mails to you.
Note: If you use this trick when creating an account for somebody else, make sure to tell the person which email address you've used, since the person needs to use that email address to log into the account you create.
If you get the message "This email address is already in use in Scrumwise" when you try to add a new user to your account, this is because there is already a personal account that uses that email address. Scrumwise doesn't allow the same email address to be used in multiple accounts.
Here are some things you can do:
To delete just your own personal account, ask a person that is administrator in the company account to delete your account. If you are administrator yourself, you should still get another administrator to do it (you can't delete your own personal account). If you are the only administrator, you should first give administrator rights to another person, and then ask that person to delete your personal account.
If you want to close the entire company account that your personal account belongs to, see here.
To close your company account, go to the "Your company account" tab in the settings of Scrumwise, and click the link "Close your company account" in the bottom right corner of the "Company info" page. You must be administrator in Scrumwise to do this.
Note that this will close the entire company account and all personal accounts in it. The users in your company account will no longer be able to log into their accounts, and you will no longer be able to access the data in the company account.
The "What's happening" view shows you what other people have been doing recently that may be of interest to you, across all projects, based on your roles in each project. So, for example, if you're a team member in a project, you'll see what other people in your team have been doing, and if you're a product owner, you'll see what other people are doing to the backlog and what happens at a higher level in the project.
Note that you can also see what has happened in a specific project, sprint, team, backlog item, task, etc., by opening the popup dialog for that object and clicking "Show activities" at the bottom of the dialog. Almost all popup dialogs in Scrumwise have an activity history like this.
Yes, you can archive projects. This is useful if a project has been completed or is no longer being worked on, and you prefer to keep it around instead of deleting it. Archived projects are not shown in the Overview page and various other places, so archiving projects helps to avoid clutter. Archived projects are still available, and you can still select them and make changes to them. And you can unarchive an archived project anytime you want.
To archive a project, open its popup dialog and click "Archive" in the bottom of the dialog. You can also select one or more projects and use the right-click menu to archive them.
To see your archived projects, use the "Show" dropdown in the lower right corner of the Projects page. The dropdown is shown only if you have any archived projects.
You can select an archived project as your current project, even though it has been archived. This way, you can view the project and make changes to it, just as you can for active projects. To select an archived project as your current project, use the right-click menu.
Yes, you can move tasks between backlog items using cut & paste. To do this, open a backlog item, select the tasks, and use the right-click menu or Ctrl + X / Cmd + X to cut the tasks. Then open another backlog item and paste the tasks there. You can also copy tasks this way. And by the way, you can also use cut, copy & paste on backlog items in the Backlog page.
You can also split a partially finished backlog item into two backlog items and move the remaining tasks to the new item. To do this, select one or more partially finished backlog items, and select "Split these items" from the right-click menu.
Rough estimates are loose estimates that you can add to backlog items for use in prioritizing the backlog and for release planning. You don't have to use rough estimates if you don't need them.
Detailed estimates are the estimates used for planning sprints, and in the ongoing work during the sprint, such as in the task board and the burndown charts.
Rough estimates are completely separate from detailed estimates, and you can use different units for them, such as points for rough estimates, and days or hours for detailed estimates.
Yes, you can configure the units to use for rough estimates and detailed estimates. To change the units for an existing project, open the project dialog (in the Projects page) and click "Settings" in the upper right corner of the dialog. Then change the "Unit for rough estimates" or "Unit for detailed estimates" setting. You can use points, days, or hours. If you've already entered estimates somewhere in the project, you'll have the option of adjusting those estimates as part of changing the unit, such as multiplying by 6 or 8 to go from days to hours.
If you are using detailed time tracking, you can also change the unit used for the time tracking, in the project dialog.
If you're administrator, you can also change the default units used in new projects. This is done in the "Your company account" page in the settings. Note that this only affects new projects created after your change, it does not affect the units used in already existing projects.
Yes, you can do time tracking in two ways. You can either enable a "Used" field in the backlog items and tasks. This allows you to enter the time spent on each backlog item and task. Or, you can use detailed time tracking. This allows you to keep a detailed time log on each backlog item and task, and to view and export the time log for the project. This is useful if you want to track time for use in accounting or billing of customers.
To enable time tracking, open the project dialog, click the "Settings" button in the upper right corner, and select the type of time tracking you would like to use in the project. When using detailed time tracking, you can also select which unit to use for the time tracking, in the "Unit for time tracking" setting.
You can also set the default settings for these options in new projects, in your customer account settings, if you're an administrator. Note that this only affects new projects created after your change, it does not affect already existing projects.
When you're using detailed time tracking, you can view the tracked time in the "Time" tab. If the tab is not shown, click the "More" link at the right side of the tabs, and select the "Time tracking" checkbox
This is just the default. You can change this in the settings for a project. Open the popup dialog for the project and click "Settings" in the upper right corner of the dialog. Then uncheck the checkbox "Set remaining work to zero in status "To Test"".
You can use release planning to do longer-term planning that spans multiple sprints. A release can represent an actual release or delivery that you make to your stakeholders or customers during a project, or can be used as an internal milestone. It can also represent the entire output of a project that has a single delivery at the end of the project. For example, a release might take 3 to 6 months, and consist of 5 to 10 sprints.
You can have multiple releases in planning at the same time. So, you can plan multiple releases ahead, and adjust the contents of each release as your priorities change over time.
The contents of a release is the backlog items that you assign to it. You can assign backlog items using drag and drop, or the right-click menu.
Release planning uses the rough estimates of the assigned backlog items. For example, the rough estimates are used for predicting release dates, and for release burnup charts. This is different from sprints, where the detailed estimates are used.
The actual work on the backlog items are done using sprints, exactly like you would do if you weren't using release planning. You can assign the backlog items to any sprints you want, in any order. So, a release doesn't have a tight coupling to a specific sequence of sprints. It's up to you which sprints you use to complete the backlog items in a release.
When you are ready to start the actual work on a release, start the release by clicking "Start this release". This is typically done on the day where the first sprint in the release starts.
During the work on the release, you can keep track of the progress using the release burnup chart for the release.
When your release is done, complete the release by clicking "Complete this release". This is typically done on or after the day where you complete the last sprint in the release and there is no more work to do be done in the release (at least as far as your project in Scrumwise is concerned).
Release planning uses the rough estimates on backlog items, in the "Rough estimate" field of each backlog item. This way, you can add rough estimates on backlog items early on, during your release planning and high-level backlog management. Then, when a backlog item is ready to go into a specific sprint, you can do the detailed and more accurate estimation needed for that, and enter detailed estimates in the "Estimate" field of the backlog item or its tasks.
Rough estimates are completely separate from detailed estimates, and you can adjust the rough estimates independently of the detailed estimates.
You can assign backlog items to releases even though they don't have rough estimates. This is particularly useful when you're doing the loose planning of a release and you haven't gotten around to adding rough estimates on all backlog items.
If the release is in progress, it's a good idea to add rough estimates as soon as possible, since the release burnup chart and the release date prediction will not take backlog items without rough estimates into account, so will be less accurate if some backlog items are missing rough estimates.
In the release burnup chart, the lines for planned work and done work will be dotted if there are one or more backlog items without rough estimates on a given day, since this means that the lines are less accurate because of the missing estimates.
Yes. To do this, set the start date of the release, and enter the expected velocity per week in the release. This is done in the popup dialog for the release.
You can specify the best-case, expected, and worst-case velocity. If you only want to specify one velocity, it's most useful to specify the expected velocity, since that is used for most predictions.
The velocity should be the sum of the expected velocities of each team that works on the release. You can see the velocity of each team in the popup dialog for the team. You can also see the velocity across all teams by clicking the link "Show velocity in this project" in the popup dialog for the release. Note that these velocity charts show the velocity per sprint, not per week. You must calculate the velocity per week yourself, based on the velocities shown in the charts.
You can view release burnup charts in the "Burnup" tab. If the tab is not shown, click the "More" link at the right side of the tabs. Then select the "Release burnup" checkbox.
You can also view the release burnup chart of a release in the popup dialog for the release. And if you're a stakeholder in a project, the release burnup chart for the ongoing release will also be shown in your "Overview" tab.
The release burnup chart shows how much work is planned in the release (the dark blue line), and how much of that work is done (the green line). This way, you can see if work is added or removed in the release (scope changes), and how much work you've done so far.
The burnup chart also shows the planned release date, as a vertical light blue line.
If you have specified one or more velocities in the release, the burnup chart also shows the predicted future burnup using each of those velocities, and the predicted release dates that they result in. This is shown as a thin dotted line that is green for the best-case, gray for the expected case, and red for the worst-case.
The lines for planned work and done work will be dotted if there are backlog items without rough estimates on a given day, since this means that the lines are less accurate because they don't take those backlog items into account.
Note that the line for done work only includes backlog items that are completely done. It doesn't take into account work in progress on backlog items that are not yet done. This is different from the burndown chart for a sprint, where the work in progress of a backlog item is also included. So, a release burnup chart is a bit more conservative than a sprint burndown chart.
Yes, you can. This works best if you have specified the available time individually for each day in the sprint, since you can then change the available time for each remaining day in the sprint.
If you have specified the available time as a total for all days, and you change the total time, the ideal line (the gray dotted line) in the burndown chart will distribute that time across all days in the sprint. This is probably not what you want. In that case, you can simply switch to specifying the available time individually for each day, and then change the available time for each remaining day in the sprint. To do that, open the popup dialog for the team in the sprint, and click the link "Specify for each day instead".
Yes. By default, Scrumwise will automatically show you this in the Sprints page when it looks like it could be useful to you. You can configure when it should be shown in your personal account page in the settings in Scrumwise.
When shown, here is what you will see: If the sprint is in planning, you will see how much work is assigned to each member of a team. If the sprint is in progress, you will see how much work remains of what is assigned to the person. And if the sprint has been completed, you will see how much work was assigned to the person in the sprint.
When you unassign a backlog item, the progress of the item will be kept, and you can later on assign it to another sprint to continue work on the item.
Note that all of the work on the backlog item will be credited to the sprint where you complete the item. So, for example, the work will not be included in the velocity for the sprint that you unassign the item from. If you would like some of the work be credited to that sprint, you can split the item instead.
You can split the backlog item into two backlog items, one that stays assigned to the sprint and is completed in the sprint, and one that is unassigned from the sprint and contains the remaining work, to be assigned to a future sprint. To do this, select one or more partially complete backlog items, and select "Split these items" from the right-click menu. If a backlog item has tasks, the tasks that have not yet been started will be moved to the new backlog item, as part of the split.
Yes, you can change the dates whenever you want, such as when you are extending a sprint.
Note that if you have specified the available time for the teams as totals in the sprint, and you change the duration, the ideal line (the gray dotted line) in the burndown chart will redistribute that time across all days in the new duration of the sprint. This is probably not what you want. In that case, you can switch to specifying the available time individually for each day in the sprint. To do that, open the popup dialog for each team in the sprint, and click the link "Specify for each day instead".
This is because you've added backlog items to the sprint after you started the sprint. The starting point of the burndown chart shows how much work was in the sprint at the point in time when you started the sprint. So, if you hadn't added any backlog items, or very few, at that point, the burndown chart will start low. And if you add backlog items to the sprint after that, the burndown will go up, since the remaining amount of work increases.
So, you should normally pack the sprint first, and then start it when you are ready to start working. You can add or remove backlog items at any time, but anything you do after the sprint has started will affect the burndown chart.
Yes, there are optional link fields in backlog items, tasks, sprints, releases, and projects. You can use them to link to external information, such as a bug in a bug tracking system, or a page in a wiki.
To select which link fields to show in a project, open the project dialog (in the Projects page) and click "Settings" in the upper right corner of the dialog. Then find the link field settings and select which link fields to show.