New to Intervals? Have questions or need help?:
Modules - how to use them?

1. •  
     CommentAuthorMichael
   • CommentTimeMay 8th 2007

    
   Modules are an advanced feature in Intervals. If you don't use them they should not get in the way, but if you do use them they help create pretty powerful reports. Here is an example of how a software developer can use Modules:
   
   Security (Module)
   - login page (.5 hrs) - (task)
   - password change page (.5 hrs)- (task)
   - user initialize - (task)
   
   Then you can run a Project Activity report on a single module if needed, or use Projects >> Time Summary >> View By Module for grand totals.
   
   If you plan to use "Security" frequently with your projects it can be added as a default Module under Site Settings. That way you can compare that particular Module across projects as well as do aggregate reports. For example, show me all hours I have spent on "Security" this year.
2. •  
     CommentAuthorMichael
   • CommentTimeJun 11th 2007

    
   ## follow up ##
   
   The above post is detailed example within a project. To take one step back and look at things from a higher view, the general idea with Modules is that they can be a phase of your project OR a detailed feature/piece of a project.
   
   For example, we do web design and web development. For a fairly straightforward job we will likely use Modules as phases of the project: Discovery, Design, Production, Development, etc. If the project is more custom nature in nature, we will use Modules in the contract we sign with the customer. Then, we track against those Modules to keep project scope under control. For example, here is an example of Modules we recently used on a contract:
   
   Module 1 - Site Strategy
   Module 2 - Visual Design
   Module 3 - HTML Production
   Module 4 - Content Management
   Module 5 - Product Management
   Module 6 - Store Management
   Module 7 - Wholesaler Application & Queue Management
   Module 8 - Site Administrator Management
   Module 9 - Custom Metrics / Reporting
   Module 10 - Simple Site Search
   Module 11 - Email Marketing & List Management
   Module 12 - Training and Support
   Module 13 - Hosting Analysis, Recommendation, FTP Server
   Module 14 - Deployment, Launch and Debugging
   
   Each module above has an allotment of hours from the standard work types.
3. • CommentAuthorbee
   • CommentTimeFeb 3rd 2008

    
   This is a fairly general question, to be sure. I've heard the term Discovery kicked around and want to clearly define it in my process, before adding/keeping it as a default module. I do the sales and meeting with clients. In most cases, this involves "discovery", meaning that I spend an hour or two determining what the client wants and exploring, really, how much they know about web development. . . usually included is how they intend to use their site. (There are usually several functions they haven't yet "discovered".) Is this the Discovery module as you're using it?
   Or, does Discovery take place after the initial meeting, when I "discover" that their site was built by their neighbor's cousin's boyfriend (who disappeared) and try to find the most efficient way to wrest control of the files and/or retrieve their domain name from the abyss :) in order to create a site that works.
   Or, is Discovery defined as just meeting several times during the process to "discover" whether they're pleased/displeased with our progress. Or, perhaps it's research; for example, which keywords are most popular for their industry.
   Thanks. I really like what I see so far in Intervals.
4. •  
     CommentAuthorjreeve
   • CommentTimeFeb 4th 2008

    
   In our experience, Discovery is time we spend defining a project, before we start working on it. Many times, a client will come to us with just an idea, with no expectations of how to implement the idea online. We use Discovery to encompass the amount of time spent on defining a clients needs, which in turn, enables us to more accurately estimate how much time it will take to complete the project. This Discovery phase can be a few hours, or it can take several days. When this phase consumes more than a few hours of our time, we will charge the client for our time. Why? Because we are lending our expertise to the client, helping them refine their needs into a workable proposal; something they could not achieve without our web development insight. Hope this helps!
5. • CommentAuthorbee
   • CommentTimeFeb 4th 2008

    
   Yep! It helps. That's what I thought. And, you're right. Most clients wouldn't have the tools at hand to pull together their site's scope. I once clocked 17 hours of meetings for a small, static 7-page "business card" site!! Delightful people. . . They invited me to tea for two or three hours every few days, until their Discovery invoice became quite hefty. I kind of miss those leisurely Discovery tea parties.... :)
   Thanks!