DO NOT MERGE Team analysis tool (govhub meeting prep)

JE_MEETING_SUMMARY.md

@@ -0,0 +1,90 @@
+# GovHub Resource Analysis for JE Meeting
+*Data-driven insights for special initiatives discussion - CORRECTED*
+
+## 🎯 **Updated Bottom Line Answer for JE**
+
+**The team is operating at a sustainable pace with some capacity for new initiatives, but careful prioritization will be needed. The previous "massive under-utilization" was incorrect due to limited data.**
+
+## 📊 **Corrected Key Findings**
+
+### Real SOW Utilization (from hours.csv)
+- **Current Utilization**: 31.6% of total SOW (947.75 of 3000 hours)
+- **Monthly Average**: 237 hours/month (above 200/month target)
+- **Months Remaining**: 11 months  
+- **Hours Remaining**: 2,052 hours
+- **Needed Per Month**: 186 hours/month (manageable)
+
+### Team Performance Trend
+- **April**: 296.5 hours (48% over target)
+- **May**: 294.5 hours (47% over target)  
+- **June**: 222.75 hours (11% over target)
+- **July**: 134 hours (33% under target)
+
+### Professional Services Mix
+- **75%** Support & Maintenance work (from log analysis)
+- **25%** Professional Services work (initiatives, consulting)
+- Team capable of handling both work types
+
+## 🎯 **Revised Recommendations for JE Initiatives**
+
+### 1. **Moderate Additional Capacity Available**
+- Currently need 186h/month for remaining 11 months
+- SOW allows 200h/month = 14h/month buffer
+- Can accommodate **select new initiatives** within existing contract
+
+### 2. **Strategic Initiative Prioritization Needed**
+- **ACN deploy refactor**: Fits within Professional Services scope (SOW 2.b)
+- **npm package, Orchard tests**: Smaller initiatives that fit in buffer
+- **GovHub 2.0 planning**: Major initiative may need capacity trade-offs
+
+### 3. **No Emergency Resource Changes**
+- Don't need to "reduce maintenance hours" drastically
+- Don't need Client Services immediately
+- **Can optimize within current SOW framework**
+
+## 📋 **Updated Meeting Talking Points**
+
+### When JE asks: "Where do hours for special initiatives come from?"
+**Answer**: "We have about 14 hours/month buffer in our SOW (need 186, contract allows 200). For larger initiatives like GovHub 2.0, we'll need to prioritize within Professional Services scope or discuss scope adjustments."
+
+### When JE asks: "Should we reduce maintenance for Client Services?"
+**Answer**: "Not immediately. We can accommodate select initiatives within current capacity. For major scope expansion, we could consider Client Services for specialized work."
+
+### When JE asks: "Can your team handle technical initiatives?"
+**Answer**: "Yes, we're already doing professional services work and averaging above SOW targets. Need to prioritize which initiatives within available capacity."
+
+## 🔧 **SOW Contract Reality Check**
+
+### Monthly Capacity Situation:
+- **Contract**: 200 hours/month
+- **Actual average**: 237 hours/month (18% over)
+- **Remaining need**: 186 hours/month
+- **Buffer for initiatives**: ~14 hours/month
+
+### Already Covered in SOW Section 2.b Professional Services:
+- ✅ **3rd-Party Tool Integration** (ACN deploy refactor)
+- ✅ **Technical Strategy and Approach** (GovHub 2.0 planning)  
+- ✅ **Development of Storybook Components** (Orchard tests)
+- ✅ **Professional Services Consulting Leadership**
+
+## 🚀 **Recommended Action Plan**
+
+1. **Prioritize initiatives** by business value and technical scope
+2. **Start with smaller initiatives** (npm package, Orchard tests) in the ~14h/month buffer
+3. **Plan major initiatives** (GovHub 2.0, ACN refactor) with proper scope definition
+4. **Consider Client Services** for highly specialized work that exceeds team expertise
+5. **Monitor monthly utilization** to ensure SOW compliance
+
+## 📈 **Data Sources**
+
+- **Primary**: hours.csv (947.75 hours actual usage through July)
+- **Secondary**: Team analysis tool (recent activity patterns)
+- **Reference**: SOW Professional Services scope
+
+## 🔍 **Key Insight**
+
+The team is performing well and **slightly ahead of SOW pace** (237 vs 200h/month). The challenge isn't under-utilization but **smart prioritization** of new initiatives within sustainable capacity limits.
+
+---
+
+**💡 Corrected Message**: "We have moderate capacity for new initiatives (~14h/month buffer) and should prioritize based on business value and Professional Services scope. Major initiatives may need capacity trade-offs or specialized CS resources." 

README.md

@@ -10,6 +10,7 @@ Automated reporting tools for Noko time tracking with LLM-powered processing. Th
 - **🌍 Cross-Platform**: Works on macOS, Linux, and Windows
 - **📱 Smart Clipboard**: Automatic clipboard integration (configurable)
 - **🎯 Multiple Report Formats**: Daily updates and weekly summaries
+- **👥 Team Analysis**: Comprehensive team resource utilization analysis for SOW planning
 - **⚙️ Flexible Configuration**: Environment-based setup for any team
 
 ## 🚀 Quick Start
@@ -71,6 +72,9 @@ npm run llm-geekbot
 
 # Test weekly reports  
 npm run llm-weekly
+
+# Test team analysis
+npm run team-summary
 ```
 
 ## 📋 Usage
@@ -110,6 +114,41 @@ npm run llm-weekly
 - Detailed weekly project summaries
 - Accomplishments and next steps
 
+### Team Analysis & SOW Planning
+
+Analyze team-wide resource utilization for SOW planning and client meetings:
+
+```bash
+# Summary report (perfect for meetings)
+npm run team-summary
+
+# Detailed breakdown report
+npm run team-detailed
+
+# Both summary and detailed reports
+npm run team-both
+```
+
+**Team Analysis Features:**
+- Team member resource utilization breakdown
+- Support & Maintenance vs Professional Services categorization
+- SOW capacity analysis and recommendations
+- Monthly trending and historical analysis
+- Identifies under/over-utilization patterns
+
+**Example Output:**
+```
+## 📊 Key Metrics
+- Total Hours Used: 93.0 hours
+- SOW Utilization: 9.3% of contracted capacity
+- Remaining Capacity: 907.0 hours
+
+## 🎯 Recommendations for Client Meetings
+1. Scale Current Team: Under-utilizing SOW capacity
+2. Accommodate Initiatives: Room for new initiatives within existing contract
+3. No Additional CS Resources Needed: Current team can handle expanded scope
+```
+
 ### Manual Data Operations
 
 ```bash
@@ -122,6 +161,10 @@ npm run fetch-daily
 # Generate raw data for custom processing
 node scripts/generate-reports.js raw-weekly
 node scripts/generate-reports.js clean-geekbot
+
+# Custom team analysis date ranges
+node scripts/team-analysis.js summary 2025-04-01 2025-07-31
+node scripts/team-analysis.js detailed 2025-06-01
 ```
 
 ## ⚙️ Configuration
@@ -215,6 +258,20 @@ Add context files to `data/ProjectName/memory-bank/`:
 - `progress.md` - Status and next steps
 - `productContext.md` - Project background
 
+### Team Analysis Configuration
+
+The team analysis tool automatically categorizes work as:
+
+**Support & Maintenance:**
+- `#maintenance` tagged entries
+- Core/module updates, security patches
+- Bug fixes and routine maintenance
+
+**Professional Services:**
+- `#professional` tagged entries
+- Initiative keywords: behat, playwright, migration, upgrade, drupal 11, govhub 2.0, acn, cloud next, storybook, orchard, auth0, siteimprove, figma
+- Strategic consulting and feature development
+
 ### LSM Activity Classification
 
 **LSM** = **Lullabot Support and Maintenance Department**
@@ -240,6 +297,7 @@ lsm-noko-reporting-automation/
 │   ├── generate-reports.js # Report data processing
 │   ├── llm-geekbot.sh     # Daily update automation
 │   ├── llm-weekly.sh      # Weekly report automation
+│   ├── team-analysis.js   # Team resource analysis
 │   └── setup-env.sh       # Interactive setup
 ├── package.json           # NPM scripts and metadata
 ├── .env.example          # Configuration template
@@ -254,6 +312,11 @@ npm run llm-geekbot    # Generate daily reports
 npm run llm-weekly     # Generate weekly reports  
 npm run fetch          # Fetch 7 days of data
 npm run fetch-daily    # Fetch 1 day of data
+
+# Team Analysis
+npm run team-summary   # Summary report for meetings
+npm run team-detailed  # Detailed team breakdown
+npm run team-both      # Both summary and detailed reports
 ```
 
 ### Script API
@@ -263,6 +326,11 @@ npm run fetch-daily    # Fetch 1 day of data
 ./scripts/fetch-noko.sh ProjectName 7 json
 node scripts/generate-reports.js raw-weekly
 ./scripts/llm-geekbot.sh
+
+# Team analysis with custom date ranges
+node scripts/team-analysis.js summary 2025-04-01
+node scripts/team-analysis.js detailed 2025-06-01 2025-07-31
+node scripts/team-analysis.js json  # Raw JSON output
 ```
 
 ## 🚨 Troubleshooting
@@ -295,6 +363,11 @@ node scripts/generate-reports.js raw-weekly
 - Install clipboard utility for your platform
 - Or set `CLIPBOARD_ENABLED=false`
 
+**Team analysis shows low utilization**
+- Fetch more historical data: `npm run fetch`
+- Check if all team members are logging to correct project
+- Verify project ID configuration
+
 ### Dependency Issues
 
 **Missing `jq`:**
@@ -325,6 +398,9 @@ curl -H "X-NokoToken: $NOKO_API_TOKEN" https://api.nokotime.com/v2/current_user
 
 # Test Claude Code CLI
 claude --version
+
+# Test team analysis
+npm run team-summary
 ```
 
 ## 📝 License

hours.csv

@@ -0,0 +1,35 @@
+   ,Total,maintenance,classy,sow 2 classy,php8,outage/deploy,professional,prof + lsm classy,professional reported,sum,difference,events,Remaining (total),Email said,Notes/average per month remaining,,,Projection,remaining (projection),average per month remaining (projection),months until sow end
+hours per month,200,,,,,,,,,,,,,,,,,,,,
+expire,"June 30, 2030",,,,,,,,,,,,,,,,,,,,
+months,63,5.25,,,,,,,,,,,,,,,,,,,
+total hours (5 years +3 months),12600,,,,,,,,,,,,,,,,,,,,
+April 2025 - June 2026,15,,,,,,,,,,,,,,,,,,,,
+Current SOW SAL-152,3000,,,,,,,,,,,,,,,,,,,,
+opportunity id,noko uid,,,,,,,,,,,,,,,,,,,,
+4404,703852,,,,,,,,,,,,,,,242,days until,,,,
+rollover,0,0,,,,,0,,,0,,,3000,,200.00,average per month over 15 months,,6/30/2026,3000,200.00,
+ Apr  ,296.5,231,,,,,65.5,,,296.5,0,,2703.5,,193.11,14.00,months until,296.5,2703.5,193.11,14
+ May  ,294.5,267.25,,,,,27.25,,,294.5,0,,2409,,185.31,13.00,,294.5,2409,185.31,13
+ Jun  ,222.75,172,,,,,50.75,,,222.75,0,,2186.25,,182.19,12.00,,222.75,2186.25,182.19,12
+ Jul  ,134,119.5,,,,,14.5,,,134,0,,2052.25,,184.45,11.13,,160,2026.25,184.20,11
+ Aug  ,,,,,,,,,,0,0,,2052.25,,184.45,11.13,,150,1876.25,187.63,10
+ Sep  ,,,,,,,,,,0,0,,2052.25,,184.45,11.13,,150,1726.25,191.81,9
+ Oct  ,,,,,,,,,,0,0,,2052.25,,184.45,11.13,,150,1576.25,197.03,8
+ Nov  ,,,,,,,,,,0,0,,2052.25,,184.45,11.13,,150,1426.25,203.75,7
+ Dec  ,,,,,,,,,,0,0,,2052.25,,184.45,11.13,,150,1276.25,212.71,6
+ Jan  ,,,,,,,,,,0,0,,2052.25,,184.45,11.13,,176,1100.25,220.05,5
+ Feb  ,,,,,,,,,,0,0,,2052.25,,184.45,11.13,,180,920.25,230.06,4
+ Mar  ,,,,,,,,,,0,0,,2052.25,,184.45,11.13,,180,740.25,246.75,3
+ Apr  ,,,,,,,,,,0,0,,2052.25,,184.45,11.13,,180,560.25,280.13,2
+ May  ,,,,,,,,,,0,0,,2052.25,,184.45,11.13,,180,380.25,380.25,1
+ Jun  ,,,,,,,,,,0,0,,2052.25,,184.45,11.13,,180,200.25,#DIV/0!,
+,,,,,,,,,,,,,,,,,,,,,
+Total,947.75,789.75,0,0,0,0,158,,,,,,,0,0.00,future,,"2,799.75",,,
+Overage,-2052.25,,,,,,,,,,,,,top up,,,,-200.25,,,
+Percent over,-68.41%,,,,,,,,,,,,,,,,,-6.68%,146.2,,
+,,,,,,,,,,,,,,,,,,,,,
+,,,,,,,,,,,,,,,,,,,,,
+,,,,,,,,,,,,,,,,,,,,,
+,,,,,,,,,,,,,,,,,,,,,
+,,,,,,,,,,,,,,,,,,,,,
+,350,,,,,,,,,,,,,,,,,,,,

package.json

@@ -8,7 +8,11 @@
     "llm-geekbot": "./scripts/llm-geekbot.sh",
     "llm-weekly": "./scripts/llm-weekly.sh",
     "fetch": "./scripts/fetch-noko.sh both 7 json",
-    "fetch-daily": "./scripts/fetch-noko.sh both 1 json"
+    "fetch-daily": "./scripts/fetch-noko.sh both 1 json",
+    "team-analysis": "node scripts/team-analysis.js",
+    "team-summary": "node scripts/team-analysis.js summary",
+    "team-detailed": "node scripts/team-analysis.js detailed",
+    "team-both": "node scripts/team-analysis.js both"
   },
   "keywords": [
     "reporting",