Feature vs component
Upcoming SlideShare
Loading in...5
×
 

Feature vs component

on

  • 5,034 views

 

Statistics

Views

Total Views
5,034
Views on SlideShare
3,459
Embed Views
1,575

Actions

Likes
5
Downloads
104
Comments
0

6 Embeds 1,575

http://www.scaledagiledelivery.com 1552
http://www.agilelego.com 13
http://www.linkedin.com 5
url_unknown 3
http://www.slideshare.net 1
http://10.32.72.154:15871 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Feature vs component Feature vs component Presentation Transcript

  • Component vs. Feature Teams
  • Copyright © 2007-2011, Innolution, LLC. All Rights Reserved.
    Component Teams (Single Backlog)
    Product Backlog
    Component Team #1
    Component Team #2
    Component Team #3
    Component
    Area #1
    Component
    Area #2
    Component
    Area #3
  • Copyright © 2007-2011, Innolution, LLC. All Rights Reserved.
    Component Teams (Multiple Backlogs)
    Product Backlog #1
    Product Backlog #2
    FA #1 PB
    FA #3 PB
    FA #2 PB
    Component Team #1
    Component Team #2
    Component Team #3
    Component
    Area #1
    Component
    Area #2
    Component
    Area #3
  • Component Teams
    Portfolio
    ©2010 Leffingwell, LLC.
    Reproduced with permission
    Epic 1
    Investment Themes
    Portfolio Backlog
    Epic 2
    Epics
    fit in time boxes
    Epic 3
    Architecture
    evolves continuously
    Arch. Epic 4
    Product LineManagment
    Epic 5
    Program
    Features & Enable Development
    Rough Planning
    Feature
    Feature
    Feature
    Feature
    Feature
    Epic Program Backlog
    Product Manager
    Feature
    Feature
    Feature
    Features & Enablers fit in PSI’s
    Feature
    Feature
    Enabler
    Enabler
    Team Backlog
    Pods of ~3-12 Scrum Teams
    Team
    Storiesfit in sprints
    (Implemented by) Tasks
    Team Backlog
    Spikesare research, design, refactor Stories
    Team Backlog
    Sprints
    Sprints
    See www.scalingsoftwareagility.wordpress.com and Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise. Addison-Wesley. 2011
  • Copyright © 2007-2011, Innolution, LLC. All Rights Reserved.
    #1 PB
    #2 PB
    #3 PB
    Combine Component Teams members to make Feature Teams
    Product Backlog
    Feature Team #1
    Component Team #1
    Component Team #2
    Component Team #3
    Component
    Area #1
    Component
    Area #2
    Component
    Area #3
  • Multitasking Gets you There Later
    UnitaskingOrganization
    Team Organization
    Source: InfoQ - Multitasking Gets You There Later
  • Feature Teams
    Copyright © 2007-2011, Innolution, LLC. All Rights Reserved.
    Each team has all of the people to develop complete features
    Product Backlog
    Feature Team #1
    Feature Team #2
  • Multiple teams on One Epic
    8
    Epic Backlog
    Feature Team #1
    Feature Team #2
    Feature Team #3
  • Goal
    Portfolio
    ©2010 Leffingwell, LLC.
    Reproduced with permission
    Epic 1
    Investment Themes
    Portfolio Backlog
    Epic 2
    Epics
    fit in time boxes
    Epic 3
    Architecture
    evolves continuously
    Arch. Epic 4
    PLMT
    Epic 5
    Program
    Features & Enable Development
    Rough Planning
    Feature
    Feature
    Epic Program Backlog
    CustomerTeams
    Feature
    Feature
    Enabler
    Features & Enablers fit in PSI’s
    Feature
    Feature
    Feature
    Feature
    Enabler
    Team Backlog
    Pods of ~3-12 Scrum Teams
    Team
    Storiesfit in sprints
    (Implemented by) Tasks
    Team Backlog
    Spikesare research, design, refactor Stories
    Team Backlog
    Sprints
    Sprints
    See www.scalingsoftwareagility.wordpress.com and Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise. Addison-Wesley. 2011
  • Dean Leffingwell
    Kenny Rubin
  • Chad “Agile Ninja” Holdorfwww.scaledagiledelivery.com
    Hi, my name is Chad Holdorf and I call myself the Agile Ninja (formally know as the UberScrumMaster). One day I saw a job posting on Rally for an UberScrumMaster and thought that sounded like a fun job. As I read the description I thought it sounded a lot like me.
    I work for a large manufacturing Fortune 100 company in Des Moines IA as an Agile Process Pro. I’m not sure that is the right title, but my role is to roll out and support Agile to the organization.
    The challenges I blog/tweet/talk about are related to how the organization I work in is tailored around hardware and waterfall processes. This drives me bonkers!
    I’ve been applying Agile practices since Feb08. As an Agile Coach, I orchestrated the first large-scale Agile transformation within the company. This project included over 200 people and 30+ managers and was initiated, successfully, just four months prior to a critical product launch. I specializing in organizational change, optimization, efficiency and business value delivery, I make organizations better. Today 600+ people are practicing what I call “Scaled Agile Delivery Methodology” within the company I work for.