Agile Walk Through - Free Beta

Tracking time and progress

Constant tracking

AWT makes it easy and natural to update state and time of tasks and bugs you're working on often enough to give your team-members good idea about current tasks' state and your current occupation, as well as to track time with reasonable precision.

Informing your team-mates about the state of your work will help to better coordinate your activities and in particular to prevent situations of starting doing the same job by different people.

Time tracking is also important for a number of reasons:

  • Whilst working on Fixed price projects it helps you to see how much of the planned time you have already consumed to be able to assess if the project is on budget.
  • On projects you run on Time and material basis it gives your the information to bill customer fairly according to real time spent, which is especially difficult if one person works on more than one project.
  • Finally, it gives you better understanding of time you spent on particular activities, which, with comparison to the initial estimates, will help you to do better forecasts in future.

Measuring in the flow

It's important to realize that the main purpose of time-tracking in AWT is not to control team-members activities, but rather to help learning how much time particular work take, that is extremely hard thing on their own because of the nature of human mind.

You have probably already heard of a concept of flow, which was popularized by Mihály Csíkszentmihályi in his book Flow: The Psychology of Optimal Experience. In this state of mind people are very focused on their activity, hours can go by like minutes, and amazing productivities can be achieved. This means that if you don't track your time, it'd be difficult for you to say how much it really took, because you'd feel that it was just a rapid thing.

AWT incorporates time-tracking into the natural sequence of work activities, where you don't see this tracking as a thing on its own.

You can start your work from to-do list where you can get the issue with the highest priority and instantly let the system know that you started working on it. If the issue is not assigned, you can simultaneously assign it to yourself and start permorming take and start action.

  • Todo-take-and-start-task-1
  • Todo-take-and-start-task-2

Once you've finished working on the bug or task, perform pause or finish action if all work has been done. You'll be able to adjust the time you've spent working on it, which by default will be difference between start and end time.

  • Todo-pause-task-1
  • Todo-pause-task-2

Closing the day

Finally you can check your work done on the particular day, pause or finish tasks if you've forgotten to do it before and correct spent time if necessary.

  • Project-daily-works

Works

In AWT vocabulary work defines the timeframe which was spent on working on particular task or bug.

Works are created every time you perform pause or complete action using item's menu, from issues page or pausing or finishing actions from Daily works page.

When works-information carefully entered it gives good outlook of team-activities which helps to do better planning and stick to defined plan.

In Mine daily works you will be able to see how much you were supposed to work and did work comparing works and reservations time (e.g. I'm already overworked 25% on project CareerIgniter).

Similarly, checking All daily works project manager can get information about people spending more than planned or less than planned, what can be the indication of some troubles on project or inaccurate time-tracking.

  • Project-works-mine
  • Project-works-mine-daily
  • Project-works-all-daily

Statistics Total by user gives an answer about how much time particular people spent on the project (and compare it to reservations) which helps to learn about necessary people engagement for similar projects, that can help do better time- and cost-forecasts for the future. Total by category gives more general breakdown - only works by category, which describe how much of the particular activities were needed for project completion.

  • Project-works-total-by-user
  • Project-works-total-by-category
Copyright 2007-2010 Agile Walkthrough