ScrumWorks has three components: the ScrumWorks Server, the ScrumWorks Desktop Client, and the ScrumWorks Web Client. Thanks to the magic of Java, all three components work can be installed and/or run on Windows XP, Windows Vista, Windows Server 2003, Mac OS X 10.4.2+, and Linux. The ScrumWorks Desktop Client requires Java 1.5 installed on each client computer. To run ScrumWorks Server on Mac OS X and Linux, The Java Development Kit (JDK) 1.5 must first be installed.
Start with our self-support resources, then search our forum. Please understand that technical support is not included with the free ScrumWorks product. However, we try to help users posting in our forums when we can (especially when your problems are caused by flaws in our product or documentation). Posting in the forum helps others get solutions to frequently-encountered problems. As a result, we typically do not reply to email or telephone requests for assistance.
The port on which the ScrumWorks application is accessible is actually set in a user-editable configuration file.
1. Shut down the ScrumWorks server;
2. If you're using ScrumWorks 1.3.*, edit the file: SCRUMWORKS_DIR/server/scrumworks/deploy/ jbossweb-tomcat41.sar/META-INF/jboss-service.xml
3. OR if you're using ScrumWorks 1.4+, edit the file: SCRUMWORKS_DIR/server/scrumworks/deploy/ jbossweb-tomcat55.sar/server.xml
4. Change the "8080" to whatever port you desire (port 80 is the standard HTTP port)
5. Save and close the file
6. Start up the ScrumWorks server, it will be running on that new port.
7. Note, subsequent upgrades will reset the port to 8080.
Attention 1.8.0 and 1.8.1 users: There is a bug with the ScrumWorks Server system tray monitor when changing ports as described above. The ScrumWorks server monitor stops working when the port is set to anything other than 8080. Please note that although the monitor reports ScrumWorks is not running, ScrumWorks does in fact start and works on the new port. We hope to fix this problem shortly.
ScrumWorks 1.2.0 introduced the "Is Done" attribute to product backlog items.
1. Invoke the ScrumWorksDesktopClient.
2. Doubleclick a backlog item which has been completed.
3. Check the "Is Done?" checkbox.
4. Click "OK"
5. Observe that a green checkmark appears to the left of the completed backlog item, and it is grayed out.
6. Repeat until you've marked all your completed backlog items.
7. Generate a new product burndown chart, and your data points will be visible.
The product burndown sprint bars are calculated using the effort values for that backlog item as they existed on the start date of the current sprint being plotted. By default, ScrumWorks considers a Product Backlog Item to have started life the day you entered it into ScrumWorks. You can change this by clicking the "History" button in the Product Backlog Item editor. In this expanded mode, you can add, delete, or edit backdated effort estimates for the Product Backlog Item so earlier bars in the Product Burndown Chart will reflect the work as having been identified on previous dates.
First, you can only move data files between the same version of ScrumWorks. We strongly recommend upgrading to the latest edition of ScrumWorks before moving your data. Once both servers have the same version of ScrumWorks installed, use the backup procedure to obtain your data from the first server and then restore your backup to the second server.
Now that the ScrumWorks server is installed and running, each user must use their web browser to launch the client. See the Client Installation Guide in the Documentation.
No. You can do Scrum successfully with 3x5 cards, Excel spreadsheets, an abacus, or a variety of software products that weren't originally designed for Scrum. ScrumWorks just adds convenience and visibility so people can focus on their work instead of doing (or neglecting to do) a bunch of stuff manually.