DO NOT MERGE Team analysis tool (govhub meeting prep) #10
Conversation
## New Features - **Team Analysis Tool**: `scripts/team-analysis.js` - Analyzes all team members' resource utilization - Categorizes Support & Maintenance vs Professional Services - SOW capacity analysis and recommendations - Monthly trending and historical analysis ## NPM Scripts Added - `npm run team-summary` - Meeting-ready summary report - `npm run team-detailed` - Detailed team breakdown - `npm run team-both` - Combined reports - `npm run team-analysis` - Base command ## Key Analysis Features - **Work Type Categorization**: Automatic classification using tags and keywords - **Capacity Analysis**: Compares actual vs SOW contracted hours (200/month) - **Team Member Breakdown**: Individual utilization patterns - **Meeting Recommendations**: Data-driven suggestions for client meetings ## SOW Integration - Configured for GovHub SOW (Chart 4: 200 hours/month, $35K budget) - Professional Services keyword detection (behat, playwright, drupal 11, ACN, etc.) - Maintenance vs initiatives categorization ## Documentation - Updated README with team analysis section - Added troubleshooting and configuration guides - Included usage examples and output samples ## Use Case Perfect for answering JE's questions about: - Current team capacity vs SOW expectations - Whether new initiatives require Client Services resources - Resource allocation between maintenance and professional services Testing shows 9.3% SOW utilization (93/1000 hours) - massive capacity available.
- Updated SOW config: 15 months, 3000 hours total - Fixed capacity analysis: 31.6% utilization (not 9.3%) - Realistic recommendations: moderate capacity, not massive under-utilization - Updated meeting summary with corrected insights - Data source: hours.csv shows 947.75h used, averaging 237h/month
- Fixed duplicate sowStart and monthlyNeeded variables - Script now works correctly with corrected SOW data - Shows accurate 31.6% utilization and approaching capacity limits
AI Interaction SummaryCompleted using: Claude Sonnet in Cursor Chronological History:
Customer: My company: The customer Product Owner, JE, is asking for decidated resources for some special projects. Please read part of the SOW, and extract important items related to dedicated resources and special client services like initiatives and special projects. The SOW is a 5 year (I think 3 year with optional 2 year extension) SOW. We are breaking it into 1 year chunks for noko (time tracking). The first year is 16? months then the other years are 12 months (aside: to get us aligned with government fiscal year). My maintenance team for this customer (we also work on 3 other customers) Client Services resources (vs maintenance department resources) have special skills and background and experience on other big platform builds our company has resently done. Client Services devs cost more than Maintenance department devs. Right now, we are trying to limit dev and qa to 10 hours a week, and pm'ing to 4 hours a week. See @hours.csv for more info and a projected hours scenario that leaves 200ish hours remaining. That 200 hours might be set aside for Client Services resources to do some deploy refactoring to make our deploy work on ACN (Acquia Cloud Next). One of the things the meeting is attempting to clarify, is where do hours for JE special initiatives come from? Should I reduce our maintenance to set aside even more hours for CS?" - establishing complete project requirements and analyzing SOW for resource allocation strategy
Key Accomplishments:
Technical Implementation:
Business Impact: |
No description provided.