Download - Agile Is Killing Me! Product Camp Austin 2010

Agile is killing me! Managing your time when development goes Agile

Paul [email protected]

please thank our sponsors

3© 2010 Paul Brownell [email protected]

Paul Brownell

• Software Process Practice Leader• 15 years as a software executive• Agile practitioner since 2001• Specialist in Scrum and Outsourcing• Led SCRUM teams distributed across India,

Israel, China, and the US


Objective – Share Techniques

• Dealing with role conflict• Adapting to global teams• Leverage organization models• Avoid common pitfalls


ComprehensiveDocumentation

Processes and Tools

Contract Negotiation

Following a Plan

Agile Fundamentals

over

over

over

overCustomerCollaboration

Individualsand

Interaction

Respondingto Change

Working Software


Scrum Process


Scrum Roles

Product Owner• Develops backlog• Determines priorities• Serves as proxy for the user/customer• Identifies business value• Relates work units to business objectives• Defines acceptance criteria• Interacts daily with teams

Scrum Master• Facilitates development process• Coordinates with other teams• Provides status information• Removes blocks and protects from

interruption• Ensures implementation of lessons

learned

Team• Designs software• Codes Software• Tests software• Documents software


Product Manager Role


Product Manager• Develops strategy• Analyzes markets• Manages portfolio• Sets pricing• Builds business partnerships• Promotes product• Supports sales• Interacts with customers


Role Conflict


Product Manager• Develops strategy• Analyzes markets• Manages portfolio• Sets pricing• Builds business partnerships• Promotes product• Supports sales• Interacts with customers

customers team


Role ConflictTechniques

• Identify a Proxy: Business Analyst, Architect, Lead Developer or Lead QA• Involve customers/clients to provide direct

feedback and input• Provide windows of scheduled availability•Make time for: Release Planning, Sprint

Planning, Demos

© 2010 Paul Brownell [email protected]

11

Adapting to Distributed Teams

• Minimal face-to-face time• Different time zones• Language and culture

barriers• Hard to ‘sketch on a

napkin’• Discussions by email


Adapting to Distributed TeamsTechniques

• Identify a Proxy in the same time zone• Provide windows of scheduled availability in

the same time zone•Make time for: Release Planning, Sprint

Planning, Demos and daily standups


13

Organization Structures – Combined Role

• Advantages– Clear connection to

customer– Clear understanding of

release status and content

• Keys to success– Good proxies– Careful time management

customer team customer

Product Manager/Owner 1

Product Manager/Owner 2

Product A-F Product G-L

Product Line Owner


14

team

Organization Structures – Split Role (Large Company, Many Products)

• Advantages– Clear functional focus– Match skills to function– PO can co-locate

• Keys to success– PM & PO tightly

connected

customer

Product Manager

Products A-F Products A-F

Products G-LProducts G-L

Product Owner

Product Line Owner


15

team team

Organization Structures – Split Role (Small Company, Many Products)

• Advantages– Clear functional focus– Match skills to function– PO can co-locate

• Keys to success– PM & PO tightly connected– Careful PM time

management

customer

Product Owner 1

Products A-F Products G-L

Product Owner 2

Product Manager


16

Planning Continuously

• Regular re-examination of priorities• Smaller granularity deliverables• Forest is built one tree at a time• More meetings


Planning ContinuouslyTechniques

• Just-in-time deliverables• Teamwork• Use tools to stay organized: Rally,

VersionOne, JIRA + GreenHopper •Watch out for:– Getting stuck in the building– Thrashing priorities– Overcomplicating the requirements

Ask about a free consultation

[email protected]

please thank our sponsors

Download - Agile Is Killing Me! Product Camp Austin 2010

Top Related