User Timesheets etc.

Overview of simple features a User might use

 

eTrack is designed to sit open on everyone's desk (like email) and be used by all staff.    Five key ways in which staff might use eTrack, as shown in the following screen shots, are:

  • Complete Timesheets and estimated hours to complete;
  • View assigned work;
  • View personal schedule;
  • Write up correspondence, view procedures and link to documents;
  • Complete compliance, checklists or approvals.

Depending on your industry, other uses may include:

  • Look up or update a client, supplier or manager's details;
  • Raise issues, variances, support queries, help desk queries;
  • Record expenses, disbursements or materials used;
  • Add to a knowledge base of information;
  • Receive alerts as to when something needs doing;
  • Track Sales and correspondance;
  • Track requirements, test cases and defects.

Complete Timesheets

 

Customers use Timesheets more than any other feature.   eTrack makes it very simple for every staff member to complete their own timesheet.   This helps ensure all work is tracked (including goodwill) and accurately.

Do you find staff switch around between projects?  

A powerful feature of the eTrack timesheet is that you can have the precision of creating plans using Roles with separate rates but not have to have the administrative overhead of assigning people to work that can change.   Each User has a default Role but (if security allows) can select to book time to a different role assigned to the work (ie at a different rate).    

 

Users can...

Book actual time and

Estimate Time to Complete (ETC).

Optionally, automatically decrement the ETC when hours are added. 

Charge order of entries and carry forward to next week for even easier entry.

Add comments.

Record time against multiple Activities on one day.

Print one or bi-weekly Timesheets.

 

View Work Allocations

 

However extensive the main tree becomes, a users view can be as simple as you wish.   The profile of each user can be separately set up to restrict what they "can access".   Additional security controls what each person can do to each item.

 

Users can....

View their 'Intray'.

View a pre-defined report of any fields.

Sort, filter, drill down to details and back.

Export to many formats or print.

 

With one click, the user can view their own personal schedule (might be read only) that has all project and non project work on it.

 

 

Case Notes

 

Case Notes can be applied to any item such as work, people, companies, releases, assets etc.

The use of Case Notes is unlimited.  Some common uses are:

 

  • Phone call summary
  • Letters
  • Faxes
  • Emails
  • Notifications
  • Drawings
  • Procedures
  • Hints and Tips
  • Knowledge base
  • Links to document templates
  • Links to project documentation
  • Telemarketing
  • Requirements
  • Test Cases
  • Issues
  • Risks
  • Compliance documents


Users can...

Link to a document.

Edit using Microsoft Word.

Edit in place with Rich Text (numbers, colours etc)

Notify someone when to do something like return a call on a date.

View all your Notifications.

Sort, Filter, Print.

 

QA Tasks and Compliance Checklists

 

As a user completes their timesheet, the checklists are one click away.   A common use is to populate templates so that when a work item is created the relevant checklist is also created. Editing can be protected by security.  Common uses include...

  • Compliance tasks
  • QA Tasks
  • Security items
  • To Do Lists
  • Approvals
  • Estimating work by going to a lower level of detail than the main tree.
  • Auditing


Users can...

Use to estimate a work phase.

Tick off, automatically recording who and when.

Add notes.

 

Requirements Tracking


eTrack supports Requirement Tracking.


a) Use case scenarios can be written into the Notes tab of eTrack and related to each other with many to many relationships.


b) ‘Non Functional’ requirements can be defined in templates so a complete checklist of all things to consider can be created for each project.

c) Your process and methodology guidelines and templates can be made visible at a users finger tips or a direct link made to an Intranet methodology. This can be continually improved by encouraging users to raise suggestions in eTrack that flow through approval steps using the workflow capabilities.

d) Change Requests can be raised using eTrack’s Issue Tracking and Help Desk capabilities that can be related to the requirements or use cases.

e) Test Cases can be created that relate to the requirements or refer to use cases as the test procedures. Different groups of Test Cases can be combined to form Test Runs, say for regression testing at various stages of the release cycle (eg: full, 3 days before release, 2 hours before release). Instances of the Test Runs can be created with assigned people and results recorded.

In addition the use cases and requirements can be directly assigned to people, budgeted and scheduled. There is no need to create separate tasks and link the use cases to the tasks for scheduling since the requirements are just another type of work item with their own views (sub tabs)! 

This is a very brief overview of Requirements Tracking.  Please contact eTrack for more information and a demonstration.

Top | Home | About Us | Demos | Why eTrack? | Testimonials | Contact Us | © 2005 eTrack Products Pty Ltd :: Designed by machineThinking