Agile Work in Modern Work Environments

Best practices for agencies, service providers, product companies and project teams

Agile in Different Company Types

🎨 Agencies & Service Providers

Specifics

  • • Multiple client projects in parallel
  • • Changing requirements from clients
  • • Fixed-price vs. time & material
  • • Team members work on multiple projects
✅ What Works
  • Kanban instead of Scrum (more flexible for ad-hoc requests)
  • Weekly client demos instead of sprint reviews
  • T-shirt sizing for quick estimates
  • Dedicated teams per client (when possible)
❌ Challenges
  • • Clients as "Product Owner" (often unclear)
  • • Context switching between projects
  • • Estimation with unclear specs
  • • "Client is always right" vs. agile principles

💡 Tip: Use Scrum Poker for transparent estimates with clients. Show uncertainty through "?" cards.

🚀 Product Companies & Startups

Specifics

  • • One product, long-term vision
  • • Fast iteration & MVP development
  • • Data-driven decisions
  • • Feature flags & continuous deployment
✅ What Works
  • Scrum with 2-week sprints
  • OKRs for quarterly goals
  • Continuous delivery instead of sprint releases
  • A/B testing for feature validation
⚠️ Attention
  • • Not too many experiments in parallel
  • • Manage technical debt
  • • Balance: features vs. stability
  • • Product Owner must be available

🏢 Large Companies & Enterprise

Specifics

  • • Many teams, dependencies
  • • Legacy systems & compliance
  • • Hierarchical structures
  • • Long release cycles
Scaling Frameworks

SAFe

Structured, top-down, good for regulated industries

LeSS

Lightweight, bottom-up, multiple teams, one Product Owner

Scrum@Scale

Scales Scrum principles to meta level

💡 Tip: Start with 1-2 pilot teams, show successes, then scale. Big bang transformations usually fail.

📊 Project-Based Teams

Specifics

  • • Fixed end date
  • • Often external stakeholders
  • • Budget constraints
  • • Team dissolved after project
Hybrid Approach: Agile + Traditional PM
  • Agile for development: Sprints, standups, retrospectives
  • Traditional for contract: Milestones, Gantt charts for stakeholders
  • Rolling wave planning: Detailed for next 2-3 sprints, rough for rest

Remote & Hybrid: Agile in Distributed Teams

Since COVID-19, remote agile is the new standard. The challenge: Scrum was designed for co-located teams.

Solution: Digital tools + adapted practices.

🛠️ Essential Remote Tools

Video: Zoom, Google Meet

For dailys, plannings, retros

Board: Jira, Linear, Trello

Digital Kanban/Scrum boards

Estimation: Scrum Poker Online 🃏

For remote Scrum Poker

Retro: Miro, Mural, FunRetro

Digital whiteboards

✅ Best Practices

📹 Cameras On

Especially in dailys & retros – fosters connection

⏰ Fixed Times

Daily always 9:00, Planning every 2nd Monday → Routine

📝 Over-Communication

What is "quickly discussed" in the office must be proactively communicated remotely

🤝 Virtual Coffee

15min informal meeting per week for team bonding

Agile Transformation: Step by Step

1

Select pilot team

Motivated team, complex product, supportive manager. Not too critical (low risk).

2

Training & coaching

2-day Scrum workshop, then external agile coach for 3-6 months.

3

3 sprints = inspect & adapt

After 3 sprints review: What works? What doesn't? Adjust process.

4

Communicate successes

Show metrics: time-to-market, bug rate, team satisfaction. Share learnings internally.

5

Scale

Second team, third team... but NOT big bang. Organic growth.

Metrics for Agile Teams

Metric What does it measure? Goal
Velocity Story points / sprint Stable over time
Sprint Commitment % of planned stories completed > 85%
Cycle Time Days from start to done ↓ Reduce
Escaped Bugs Bugs in production ↓ Minimal
Team Happiness Team satisfaction (1-5) > 4.0

Start Your Agile Journey!

Begin with Scrum Poker for better sprint planning.

Create Free Room

Scrum in Teams →

Roles, Ceremonies & Best Practices

What is Scrum Poker? →

History & Methodology

Successful Estimation →

Story Point Best Practices