Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Developers Delivery Team members are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.

The specific skills needed by the Developers Delivery Team are often broad and will vary with the domain of work. However, the Developers Delivery Team are always accountable for:

  • Creating a plan for the Sprint, the Sprint Backlog;

  • Instilling quality by adhering to a Definition of Done;

  • Adapting their plan each day toward the Sprint Goal; and,

  • Holding each other accountable as professionals.

Delivery Team Size

Optimal Development Delivery Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three Development Team members decrease interaction and results in smaller productivity gains. Smaller Development Delivery Teams may encounter skill constraints during the Sprint, causing the Development Delivery Team to be unable to deliver a potentially releasable Increment. Having more than nine members requires too much coordination. Large Development Delivery Teams generate too much complexity for an empirical process to be useful. The Product Owner and Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog.

Resources

Books

         

Scrum Pocket GuideAgile Software Development with ScrumScrum Guide

Scrum Theory and Principles

        

The-Pragmatic-Programmer-From-Journeyman-to-MasterThe-Art-of-AgileDevelopmentAgile Project Management with Scrum

Cross-functional, Self-organizing

        

Peopleware-Productive-Projects-and-Teams-(Second-Edition)Practices-of-an-AgileDeveloperScrum-and-XP-from-the-trenches

Development

        

specification-by-exampleAgile-Estimating-And-PlanningUser Stories Applied

Analysis

        

Growing-Object-Oriented-Software,-Guided-by-TestsBeyond-Software-ArchitectureDesign-Patterns

Emergent Architecture

        

refactoring-improving-the-design-of-existing-codeAgile Software Development Principles Patterns and PracticesThe-Clean-Coder-A-Code-ofConduct-for-Professional-Programmers

Programming

     

The Art of TestingTest-Driven-Development-By-Example

Test First Development

        

Clean-Code---A-Handbook-of-Agile-Software-Craftsmanshipimplementation-patternspatterns-of-enterprise-application-architecture

Standards

        

Working-Effectively-with-Legacy-Code-by-Michael-FeatherContinuous-Integration-Improving-Software-Quality-and-Reducing-RiskAgileTesting

Testing

        

Continuous-Delivery-Reliable-Software-Releases-through-Build,-Test,-and-Deployment-AutomationVisual-Studio-Team-Foundation-Server-2012-Adopting-Agile-Software-Practices-From-Backlog-to-Continuous-Feedback-3rd-Edition-Microsoft-Windows-Development-SeriesProfessional-ScrumDevelopment-with-Microsoft-Visual-Studio-2012

Application Lifecycle Management