One of the more advanced and abstract features of Intervals is it’s ability to group time into modules. These can be thought of as buckets, or classifications, of time. They make more sense when addressed from the perspective of a project manager, who needs to track a project in terms of phases, or break a project down into parts. But how do modules make sense to a developer?
For most of us using Intervals to track time as a developer, the modules will already be available to us; just pick one when entering your time. But developers who also manage projects, or freelancers, will need to use modules in a logical way. Some ideas on how to use them are:
- Create modules for each phase of a project — estimating, designing, copywriting — so you can see how much time you are tracking in each area across projects
- Create an ‘out of scope’ module to track time spent on feature creep.
- Create modules for geographical locations — use these modules to track time entered by outsourced developers or when working from your home office or coffee shop
- These are just a few ideas. Feel free to share how you’ve used modules…
For a more technical explanation of modules, or to understand them as a project management tool, read the forum post: Modules – how to use them?
