Already a member?
——— OR ———
Signup
for our Free Trial!
|
|
|
|
|
|
|
XTremeTeam Sample Screen Shots |
|
|
|
|
| Overview |
|
Below are some sample screen shots of XTremeTeam.
These images are representative of the overall clean UI desing of the product.
XTremeTeam is tested against several major browsers, including Internet Explorer, Mozilla and Opera.
Any other mainstream browsers will typically work because XTremeTeam leverages a cross browser HTML rendering engine.
While looking at the images, please note the additional usability enhancements that may not be visible in a static image:
|
|
|
• |
|
Every grid has sortable columns and paged rows
|
|
• |
|
Most grids have a recycle bin feature
|
|
|
• |
|
Most grids can be free text searched
|
|
• |
|
Smart filters and complex sorting are one click away
|
|
|
• |
|
Data in grids is usually a hyperlink to pertinent details
|
|
• |
|
Starter help is available and can be individually turned off as you become a power user
|
|
|
• |
|
Commands can be issued in groups
|
|
• |
|
Dynamic Navigation Menus
|
|
|
• |
|
Context Sensitive Help on every page
|
|
• |
|
Page error, warning and confirmation boxes to guarantee you understand
|
|
|
|
| |
| Release Planning |
|
Release Planning lists all the stories that have not been completed or planned for an iteration.
This list allows you to group select stories for inclusion in the current or a future iteration.
The project status attached to the top of the list provides feedback on project velocity and the current estimate of story ideal days.
The default sort on this page is by Priority ascending, then Business Value descending, Risk ascending and Esitimate ascending.
This typically will bubble up the most important stories for planning.
|
|
|
|
|
| |
| Release Iteration Status |
|
Release Iteration lists show you the status of your selected iteration.
From here the iteration can be modified by removing a story or deferring a story to the next iteration.
Stories can be accepted from this page. Doing so will accept each acceptance test associated with the story and mark the completion date.
XTremeTeam maintains multiple estimates, the original when the story was created, an estimate during signup and another estimate when the task is started by the developer. Each estimate defaults to the previous.
|
|
|
|
|
| |
| Task Signup |
|
Signing up for tasks can be accomplished in two ways: self signup (shown here) and task assign done by a lead developer or manager.
The task is shown at the top of the page.
A brief description of your current velocity and load are displayed.
This will help you determine if you can work on this task.
Other developers who will be pairing with you are shown as well.
A complete list of your current load for that iteration are displayed at the bottom.
|
|
|
|
|
| |
| Task Start |
|
Starting a task requires setting you estimate.
This estimate is most relevant because it is made during the time you are about to do the task.
Since you may have gained better knowledge of the task or partially completed some of the work as part of another task, this estimate will most likely be the most accurate.
As with all estimates, you can provide reasoning as to why it will take the specified amount of ideal days.
The start date/time can be set because you may have started it yesterday or earlier in the morning.
|
|
|
|
|
| |
| Task Stop |
|
When you stop a task, you can set the start and stop times.
We provide this flexibility because you may have started and stopped this task prior to addressing the task in XTremeTeam.
When you set the times, XTremeTeam automatically tries to calculate the number of days used to complete the task.
This will take into consideration what time you started and stopped and weekends.
You can change this value, it is just a guess at what it would be if you worked normal hours during that time period.
You can also specify the time as a percentage of the overall time. You may have been working on two tasks 50% of the time.
In addition, you can set the overtime amount which will correct your velocity and load factor for this amount of extra effort.
|
|
|
|
|
| |
| Story Edit |
|
Story editing is straightforward. Specify an unique name and choose a subject (optional) which story is associated with.
Subjects make it easier to find associated stories and reports can be customized to subjects.
Then specify a business value and completion priority.
Enter the details of the story and an metaphor (optional) of how you see this story behaving.
Programmers will then provide feedback on the story before you typically schedule this story for an iteration.
|
|
|
|
|
| |
| Security |
|
XTremeTeam utilizes a role based security so that certain functions are streamlined and protected.
Reducing the overall features from the UI makes it easier to accomplish your task.
Protecting the feature makes the feature only available to users who should be able to perform the task.
You can see that XTremeTeam has several key roles: Customers, Programmers, Testers, Trackers, Reviewers and Coaches.
|
|
|
|
|
| |
| Context Sensitive Help |
|
Help is available from any page in XTremeTeam.
Help will be relevant to the page you are currently using.
Once help is opened, you can then navigate to any page using the index on the left.
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
;)
;)
;)
;)
;)
;)
;)
;)