You can try Scrumwise without any kind of signup. Just click on the green "Take a quick look" button on the front page, 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, 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 6-8 weeks. 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. A newsletter and a blog will be coming later.

We provide free support via email. In many cases, you'll have an answer within an hour. Just write us at support@scrumwise.com.

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 context 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 context 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 page.

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 context 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 context menu.

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 support@scrumwise.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.

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 context 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 context 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 context 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 context menu.

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.

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"".

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 context 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.

You can also split backlog items manually by copying backlog items and moving tasks between them using cut, copy & paste.

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".

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, there are optional link fields in backlog items, tasks, sprints, 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.