Scaled Agile Principles and Practices

Click here to load reader

  • date post

    14-Feb-2017
  • Category

    Software

  • view

    80
  • download

    3

Embed Size (px)

Transcript of Scaled Agile Principles and Practices

Scaling Agile Practices

Scaled Agile PracticesA look at common concepts used in the 3 major Scaled Agile frameworks LeSS, Nexus, SAFe

Why Were Here?Easy to get bogged down in the details & differences of Scaled Agile frameworks

Hypothesis - its more valuable to look at the concepts all the frameworks support and work towards those as opposed to focusing on differences in the frameworks

Terminology & CommentsUnless otherwise stated, all 3 frameworks agree on concepts shown

Cross-team or Scaled-teams means the set of scaled Agile teams

Using standard Scrum terminologySAFe uses something closer to XP language (iterations, iteration planning, standups, demos)

The FrameworksLeSS, Nexus, SAFe 4.0

less.works Larman & Bodde

scrum.org Schwaber

scaledagileframework.com Leffingwell

Certifications Abound

Summary of Common PracticesCore Concepts the Frameworks Agree On

Pre-requisitesTeams all execute team-level Scrum well (i.e., not just following mechanics)Solid technical practices are required to be successful delivering (i.e., automation, high code quality)Feature teams strongly preferred

The teams all regularly plan togetherScaled teams planning session to clarify what is being built and minimize dependenciesUse of one shared Product Backlog; each team has their own Sprint Backlog

The teams coordinate throughout the Sprint to ensure delivery of an integrated done incrementFocus is on the integrated done increment ; shared Definition of DoneCoordination to monitor progress and remove obstacles

The teams have an integrated review every Sprint to demonstrate the integrated done incrementA shared review to show stakeholders progress and receive feedback to improve the Product Backlog

The teams regularly retrospect together to find ways to improveImprove the whole system at scaleUnderstand & follow these practices!

The Details

Pre-requisitesGeneral ConceptsOrganizational StructureAdoptionScaled EventsScaled ArtifactsScaled RolesTechnical Practices

Pre-requisitesGood Scrum teams doing Scrum well at the team-levelStable, cross-functional, preferably co-located teamsTeams able to deliver a potentially releasable done increment every Sprint Consistent/Predictable output

Scaling crappy code or crappy teams, results in Scaled crap

General ConceptsFirst level scaling - 3 to 12 teamsF/w diffs: LeSS 3-8, Nexus SPS 3-9, SAFe 5-12Larger than that requires more changes that the frameworks support: LeSS Huge, Nexus+, SAFe multiple Release Trains, possibly separate Value Streams

Avoid the need to Scale if possibleScaling is non-linear. Can you downsize or improve team structure in another way?

Apply Systems thinking - remove local optimizations, dont focus on utilizationF/w diffs: Nexus silent?

Prefer Product teams and Feature focusAs opposed to component-teams and project-based

13

Organizational StructureThe vast majority of Agile teams should be Feature teams

Minimize and remove inter-team dependencies as much as possible

A single PO who owns the integrated incrementF/w diffs: Nexus & LeSS only 1 PO for all 3-8/9 teamsSAFe has a RTE PO but also retains POs at team-level

Scaled Adoption ApproachEducate everyone first

Start adoption with one set of the smallest Scaled group (i.e. , 3-12 teams)

Flip-a-switch approach

Scaled ScrumEvents, Artifacts, and Roles

The SprintAll teams align on same Sprint cadence

F/w diffs: LeSS & SAFe same boundaryNexus teams must at least align for combined Sprint Review

Scaled Backlog RefinementReplaces or in addition

F/w diffs: LeSS & Nexus every Sprint with team representativesSAFe pre-PI planning weeks with Program level representatives

Scaled Sprint PlanningPurpose:All teams understand the work to be doneMinimize & remove dependenciesInput single Product BacklogOutput each team leaves with the work they plan to work on the next Sprint (and take to their team Sprint Backlog)

Framework differences:LeSS & Nexus - every Sprint, team representativesSAFe one for every Product Increment (PI = 4-6 Sprints), everyone attends

Scaled Daily MeetingsDaily coordination across the teams (in addition to team Daily Scrum)

F/w diffs:Nexus Nexus Daily Scrum, integration focusLeSS SoS, other teams join, and just talkSAFe - Scrum of Scrums, PO Sync

Scaled Sprint ReviewPurpose:Receive and incorporate product feedback from stakeholders every SprintDemonstrate an integrated Done increment each Sprint

F/w diffs: SAFe also has team level reviewsLeSS and Nexus only integrated Sprint Reviews

Scaled RetrospectivePurpose: improve the cross team work & process

F/w diffs: LeSS & Nexus held each Sprint & send team representativesSAFe - everyone attends but only held at end of each PI

Scaled ArtifactsBacklogsShared cross-team Product BacklogIndividual team Sprint Backlogs

Integrated Product IncrementIntegrated Done Increment delivered every Sprint

Shared Definition of DoneTeams can add to it

Scaled RolesScaled PO roleF/w diffs:LeSS and Nexus a single PO for the product (i.e., all scaled teams)SAFe - names this role Product Mgmt, does not require a single person, and also retains POs at team level

Scrum Master (Uber SM)F/w diffs:LeSS - does not have Uber SMNexus - NIT SM focused on integration and Nexus education/adoption; can be team SM tooSAFe RTE works as Uber SM among other things

Development teamsStable, cross functional, preferably co-locatedVast majority should be feature teams

Technical PracticesContinuous Integration

Highly automated testing

Other Extreme Programming Engineering PracticesRefactoring, Test Driven Development, etcF/w diffs:LeSS and SAFe suggest they are required to be successfulyNexus guide is silent but Nexus training is supportive

Other Practices & Non-PracticesInformation radiators

No recommendation for a Sprint Zero

Avoid hardening/stabilization Sprints

A Few Other Key DifferencesPortfolio ManagementLeSS & Nexus all work determined by single POSAFe 15+ roles to support Portfolio Management

RolesScrum Master roleSAFe changes role of SM (primary attendee at SoS, reports status to management)Integration RoleNexus has a new role focused entirely on the integrated increment

Team frameworksScrum - LeSS & NexusScrum or Kanban SAFeKanban teams deliver on 2 week cadence with PO & SM

SummaryThe Scaled Agile frameworks agree upon some common practices

Understand and follow those practices