Team Level

Flow_TeamLevelThe Team Level is composed of development teams and shared services. Each development team is composed of the developers, testers, analysts and SMEs required to produce and implement a Business value increment, for quality assurance, and continuous incremental improvement. A team’s work is composed of the stories and tasks for a specific release, enhancements, production support, and maintenance requests.

Skills needed in a team typically include analysis, design, code, build, deploy, testing, acceptance, validation, and implementation. Extended skills needed might include: Architecture and design, build and release management (environments), SEO, and subject matter/domain expertise (technical, Business, and customer).

Roles at the Team Level

Role Focus of the Role
Product Owner
  • Acceptance, validation, adoption: MBI and features
  • To the development team, the Product Owner looks like a representative of enterprise business value
  • To those who identify what value is needed, the Product Owner looks like a member of the development team: one who thoroughly understands value and their perspective
Team Agility Coach
  • Instilling and nurturing Lean-Agile practices
  • Coaching for visibility, transparency, and Lean-Agile practices
  • Continuous incremental process improvement and team efficiency
Business Subject Matter Expert
  • Acceptance criteria
  • Validation and implementation of Business value increment
  • Contributing to requirements
Business Analyst
  • Synthesizing/refining requirements
  • Business analysis
  • Acceptance tests
Technical Architect
  • System architecture and design
Technical Lead
  • Design and code quality
  • Define appropriate skills for technical development
Developer
  • Designing, writing code, unit test
  • Developing use cases as needed or appropriate
  • Incremental value delivery, quality, and continuous improvement
Tester
  • Early involvement with developers and analysts to support ATDD and TDD
  • Representing testing discipline within the team
  • Developing and execute test cases
  • Coordinating testing activity to ensure a last “safety net” prior to deployment to production
Production Support
  • Providing operational and production input
  • Preparing and execute transition to production
Database Administrator and Database Developer
  • Supporting the creation and implementation of database projects
  • Performing day-to-day administration and maintenance of database servers
  • Note: These roles are often limited; they are not expected to participate in Daily Stand-ups or retrospections unless they are a member of the core team.

Resources in this topic

Are We Using Automated Acceptance Tests? (Article)
Cross-Functional Teams: Improving Communication Between People who Work Together (Article)
Daily Stand-Ups (Article)
Dynamic Feature Teams: When Static Won't Work (Article)
Going Beyond Scrum, Part 2 (Blog Entry)
How Is Integration Across Teams Being Handled? (Article)
How Small Are Our Stories? (Article)
How Will UX Work With the Teams? (Article)
If We Do Estimate, What Estimation Method Should We Use? (Article)
Iteration 0 - Conduct (Article)
Lean-Agile Coach Library (Article)
Lean-Agile Team Checklists (Article)
Meetings for Lean-Agile (Article)
Online Learning (Article)
Overview of Roles (Article)
Should We Estimate Our Work? (Article)
Team Level (Process) Supportive Inflection Points (Article)
Team Level (Technical) Supportive Inflection Points (Article)
Technical Agility Roadmap (Article)
To What Extent Will Test-First Methods Be Used? (Article)
Types of Tests for Code (Article)
Using Visual Controls (Article)
What Design Method Will Be Used? (Article)
What Is the Ecosystem Structure at the Team Level? (Article)
What Test Harness for Acceptance Tests Will Be Used? (Article)
What is Agile at scale? The different approaches to achieve it | FLEX from Product Management to the Team (Article)
Writing Explicit Policies (Article)
Writing Tasks (Article)