Client Communication | Weekly Updates Best Practices
Keep clients informed with weekly progress updates. Communicate problems early with solutions, not surprises. GitScrum's client views share progress without exposing internals.
9 min read
Good client communication builds trust and prevents surprises. GitScrum helps teams share progress, manage expectations, and involve clients appropriately.
Communication Rhythm
Regular Updates
CLIENT COMMUNICATION CADENCE:
┌─────────────────────────────────────────────────────────────┐
│ │
│ WEEKLY UPDATE (Standard): │
│ │
│ FORMAT: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ WEEKLY PROJECT UPDATE ││
│ │ Week of January 15, 2024 ││
│ │ ││
│ │ COMPLETED THIS WEEK: ││
│ │ ✅ User authentication flow ││
│ │ ✅ Dashboard layout ││
│ │ ✅ Database schema design ││
│ │ ││
│ │ IN PROGRESS: ││
│ │ 🔄 Payment integration (60% complete) ││
│ │ 🔄 Email notifications ││
│ │ ││
│ │ NEXT WEEK: ││
│ │ • Complete payment integration ││
│ │ • Begin reporting module ││
│ │ ││
│ │ BLOCKERS/RISKS: ││
│ │ ⚠️ Awaiting API credentials from payment provider ││
│ │ ││
│ │ MILESTONE STATUS: ││
│ │ MVP: On track for Feb 15 ││
│ │ ████████████░░░░░░░░ 60% ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ TIMING: │
│ • Send same day each week (e.g., Friday 3pm) │
│ • Consistent format │
│ • Brief is better (can expand if questions) │
└─────────────────────────────────────────────────────────────┘
Milestone Reviews
MILESTONE COMMUNICATION:
┌─────────────────────────────────────────────────────────────┐
│ │
│ MILESTONE REVIEW MEETING: │
│ │
│ AGENDA: │
│ 1. Demo completed features (15 min) │
│ 2. Discuss what's next (10 min) │
│ 3. Gather feedback (10 min) │
│ 4. Address questions/concerns (10 min) │
│ │
│ PREPARATION: │
│ ☐ Working demo environment │
│ ☐ List of completed features │
│ ☐ Next milestone scope │
│ ☐ Known issues/limitations │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ MILESTONE REPORT: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ MILESTONE COMPLETE: MVP Phase 1 ││
│ │ ││
│ │ DELIVERED: ││
│ │ • User registration and login ││
│ │ • Dashboard with analytics ││
│ │ • Basic reporting ││
│ │ • Mobile-responsive design ││
│ │ ││
│ │ DEFERRED TO PHASE 2: ││
│ │ • Advanced filtering (per discussion Jan 10) ││
│ │ • Export to PDF (added to backlog) ││
│ │ ││
│ │ DEMO: https://staging.example.com ││
│ │ ││
│ │ NEXT MILESTONE: Phase 2 (Feb 28) ││
│ │ Focus: Payment integration, user management ││
│ └─────────────────────────────────────────────────────────┘│
└─────────────────────────────────────────────────────────────┘
Managing Expectations
Scope Discussions
SCOPE CHANGE COMMUNICATION:
┌─────────────────────────────────────────────────────────────┐
│ │
│ WHEN CLIENT REQUESTS NEW FEATURE: │
│ │
│ DON'T: │
│ ❌ "Sure, we can add that" │
│ ❌ "That's out of scope" (dismissive) │
│ ❌ Promise without assessing impact │
│ │
│ DO: │
│ ✅ "Let me assess the impact and get back to you" │
│ ✅ Present options with trade-offs │
│ ✅ Document the decision │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ SCOPE CHANGE RESPONSE: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ RE: Adding export to Excel feature ││
│ │ ││
│ │ Thanks for the request. I've assessed the impact: ││
│ │ ││
│ │ ESTIMATE: 3-4 days development ││
│ │ ││
│ │ OPTIONS: ││
│ │ ││
│ │ Option A: Add now ││
│ │ • Delays Phase 2 by ~1 week ││
│ │ • New target: March 7 instead of Feb 28 ││
│ │ ││
│ │ Option B: Add to Phase 3 ││
│ │ • No impact to current timeline ││
│ │ • Available mid-March ││
│ │ ││
│ │ Option C: Replace lower-priority feature ││
│ │ • Remove PDF export, add Excel instead ││
│ │ • No timeline impact ││
│ │ ││
│ │ Let me know which option works best for you. ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ KEY: Present options, let client decide priority │
└─────────────────────────────────────────────────────────────┘
Communicating Delays
DELAY COMMUNICATION:
┌─────────────────────────────────────────────────────────────┐
│ │
│ WHEN DELAY IS LIKELY: │
│ │
│ TIMING: Communicate EARLY │
│ • As soon as risk is identified │
│ • Not the day before deadline │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ DELAY COMMUNICATION: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ PROJECT UPDATE: Timeline Adjustment ││
│ │ ││
│ │ I need to share an update on our Phase 2 timeline. ││
│ │ ││
│ │ SITUATION: ││
│ │ The payment provider integration is more complex than ││
│ │ initially scoped. Their API has limitations we need ││
│ │ to work around. ││
│ │ ││
│ │ IMPACT: ││
│ │ Original target: Feb 28 ││
│ │ New target: March 7 (1 week delay) ││
│ │ ││
│ │ WHAT WE'RE DOING: ││
│ │ • Working with payment provider on solutions ││
│ │ • Parallelizing other work ││
│ │ • Daily standups to minimize further delays ││
│ │ ││
│ │ WHAT WE NEED: ││
│ │ No action needed from you, just wanted to keep you ││
│ │ informed. Happy to discuss in our next call. ││
│ │ ││
│ │ I apologize for the delay and appreciate your ││
│ │ understanding. ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ STRUCTURE: │
│ 1. State the situation clearly │
│ 2. Explain impact (new dates) │
│ 3. What you're doing about it │
│ 4. What you need from them (if anything) │
└─────────────────────────────────────────────────────────────┘
Client Involvement
Appropriate Involvement
CLIENT INVOLVEMENT LEVELS:
┌─────────────────────────────────────────────────────────────┐
│ │
│ HIGH INVOLVEMENT: │
│ • Sprint reviews/demos │
│ • Requirement discussions │
│ • Priority decisions │
│ • Acceptance testing │
│ │
│ MEDIUM INVOLVEMENT: │
│ • Weekly status updates │
│ • Milestone reviews │
│ • Design reviews │
│ │
│ LOW INVOLVEMENT: │
│ • Daily standups (usually internal only) │
│ • Technical implementation details │
│ • Internal team issues │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ SPRINT REVIEW WITH CLIENT: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ SPRINT 5 REVIEW ││
│ │ ││
│ │ ATTENDEES: ││
│ │ Team: Dev lead, Designer, PM ││
│ │ Client: Product owner, Stakeholder ││
│ │ ││
│ │ AGENDA: ││
│ │ 1. Demo completed features (20 min) ││
│ │ - Show working software ││
│ │ - Gather immediate feedback ││
│ │ ││
│ │ 2. Discuss next sprint (15 min) ││
│ │ - Review proposed priorities ││
│ │ - Get client input ││
│ │ ││
│ │ 3. Open discussion (10 min) ││
│ │ - Questions, concerns ││
│ │ - Upcoming needs ││
│ │ ││
│ │ OUTPUT: ││
│ │ Agreed sprint 6 priorities ││
│ │ Action items documented ││
│ └─────────────────────────────────────────────────────────┘│
└─────────────────────────────────────────────────────────────┘
Feedback Collection
Getting Useful Feedback
FEEDBACK COLLECTION:
┌─────────────────────────────────────────────────────────────┐
│ │
│ DURING DEMOS: │
│ │
│ ASK SPECIFIC QUESTIONS: │
│ ✅ "Does this flow match how your team would use it?" │
│ ✅ "Is this information sufficient for your decision?" │
│ ✅ "What's missing from this view?" │
│ │
│ AVOID: │
│ ❌ "What do you think?" │
│ ❌ "Does this look good?" │
│ → Too vague, unhelpful responses │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ FEEDBACK TASK: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ Client Feedback: Dashboard Review ││
│ │ ││
│ │ From: Sprint 5 review (Jan 19) ││
│ │ ││
│ │ FEEDBACK RECEIVED: ││
│ │ • "Date range filter should default to last 30 days" ││
│ │ • "Need to export this data to Excel" ││
│ │ • "Chart colors hard to distinguish" ││
│ │ ││
│ │ CATEGORIZED: ││
│ │ Quick fix: Date range default ││
│ │ Backlog: Excel export (scope TBD) ││
│ │ Design: Chart colors (designer to review) ││
│ │ ││
│ │ FOLLOW-UP: ││
│ │ ☐ Add date range fix to Sprint 6 ││
│ │ ☐ Scope Excel export for prioritization ││
│ │ ☐ Schedule design review for colors ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ CLOSE THE LOOP: │
│ • Acknowledge feedback received │
│ • Communicate what you'll do with it │
│ • Update when addressed │
└─────────────────────────────────────────────────────────────┘
Documentation for Clients
Client-Facing Reports
CLIENT REPORTING:
┌─────────────────────────────────────────────────────────────┐
│ │
│ WHAT CLIENTS NEED: │
│ │
│ ✅ Progress against milestones │
│ ✅ What they can see/test │
│ ✅ What's coming next │
│ ✅ Any blockers or risks │
│ ✅ Decisions needed from them │
│ │
│ WHAT CLIENTS DON'T NEED: │
│ │
│ ❌ Internal team velocity │
│ ❌ Technical implementation details │
│ ❌ Individual developer tasks │
│ ❌ Internal process issues │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ GITSCRUM CLIENT VIEW: │
│ │
│ Use GitScrum's reporting features to share: │
│ • Milestone progress │
│ • Completed features │
│ • Upcoming work │
│ │
│ Configure visibility: │
│ • Show feature-level, not task-level │
│ • Hide internal technical work │
│ • Focus on business value delivered │
│ │
│ REGULAR REPORTS: │
│ • Weekly status (automated if possible) │
│ • Milestone summaries │
│ • Quarterly reviews │
└─────────────────────────────────────────────────────────────┘