the agile pmo (fall 2014 version)

38
Today we will cover... Who are these people? Are PMOs setup to fail? How do we get back to Agile? Our Fantastic Voyage through Process Experiments o ROIs and Roadmaps o Swagathons o The Social Experiment

Upload: gilt-tech-talks

Post on 02-Jul-2015

3.010 views

Category:

Technology


2 download

DESCRIPTION

Gilt Senior Director, Program Management Office Heather Fleming and Director of Program Management Justin Riservato discuss Agile, Gilt's PMO challenges and more in this informative presentation.

TRANSCRIPT

Page 1: The Agile PMO (fall 2014 version)

Today we will cover...

●  Who are these people?

●  Are PMOs setup to fail?

●  How do we get back to Agile?

●  Our Fantastic Voyage through Process Experiments

o  ROIs and Roadmaps

o  Swagathons

o  The Social Experiment

Page 2: The Agile PMO (fall 2014 version)

Hello!

Heather Fleming, Sr. Director, PMO ●  Started out in front-end development, management and design

in 1996 ●  PMP Certified, Myers-Briggs (MBTI®) Certified ●  Heading up PMOs since 2006 XO Group and Gilt

Justin Riservato, Director, Program Mgmt ●  Started out in Customer Service and Product Marketing,

realized that the best part of every job was the Project Management

●  Fell in love with Gilt’s PMO philosophy and never looked back!

INFJ

ESTP

Page 3: The Agile PMO (fall 2014 version)

What is Gilt?

adjective

•  covered thinly with gold leaf or gold paint

noun

•  a young pig

Page 4: The Agile PMO (fall 2014 version)

What is Gilt? •  Gilt (www.gilt.com) is an e-commerce company focused on flash

sales. We provide insider access to top designers in sales typically lasting 72 hours.

•  We’re also one of the top tech companies in NYC!

•  Check out tech.gilt.com to learn more about us!

Page 5: The Agile PMO (fall 2014 version)

Are Traditional PMOs Set up to Fail?

Responsibilities of Traditional PMOs ●  Planning & Roadmapping ●  Resource & Capacity Planning ●  Implementing PM Processes & Standards

Page 6: The Agile PMO (fall 2014 version)

What’s the problem?

The company is expecting you to plan and roadmap...

Months (sometimes years) out...

In software engineering...

Given a short description of the work...

And you will be held accountable for your predictions!

Page 7: The Agile PMO (fall 2014 version)

You can’t predict the future!

Page 8: The Agile PMO (fall 2014 version)

So what do most people do?

●  They believe “going Agile” is a silver bullet. ●  People use the word “Agile” in many ways. ●  They implement Scrum!

Page 9: The Agile PMO (fall 2014 version)

And then what happens?

●  The company still wants you to predict the future. ●  The engineers are rebelling against the Scrum process. ●  The PMO is called into question anyway

Page 10: The Agile PMO (fall 2014 version)
Page 11: The Agile PMO (fall 2014 version)

Remember the Triangle of Truth

Page 12: The Agile PMO (fall 2014 version)

Remember the Cone of Uncertainty

Image from agilenutshell.com

Page 13: The Agile PMO (fall 2014 version)

Tell the truth!

Page 14: The Agile PMO (fall 2014 version)

And Remember the Manifesto!

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

Page 15: The Agile PMO (fall 2014 version)

The PMO @ Gilt

We get things done. We tackle a lot of the operational function of running Gilt Tech. We help Gilt Tech explore and experiment with efficient processes to select and execute strategic projects. (Notice we didn’t say “standardize”...)

Page 16: The Agile PMO (fall 2014 version)

Our Fantastic Voyage

•  ROI, Roadmaps and RFW Process

•  One Pagers and Swagathon

•  The Social Experiment

Page 17: The Agile PMO (fall 2014 version)

Everybody Loves

Roadmaps

Page 18: The Agile PMO (fall 2014 version)

They’re so pretty!

Project Q1 Q2 Q3 Q4

SEO V2

CMS

Email Redesign

Site Redesign

Landing Pages

WMS Upgrade

Referrals V2

Page 19: The Agile PMO (fall 2014 version)

ROI/Roadmap Process

Page 20: The Agile PMO (fall 2014 version)

Change Happens.

Page 21: The Agile PMO (fall 2014 version)

ROI/Roadmaps Retrospective

What works well with this model? What doesn’t work well?

Page 22: The Agile PMO (fall 2014 version)

ROI/Roadmaps Retrospective

What we learned... ●  We were on the “less valued” side of the Manifesto

o  We were spending more time planning than doing o  ...and more time on documentation o  ...and more time on processes and tools

●  We change a lot!

●  We want transparency and a say in the order of work

Page 23: The Agile PMO (fall 2014 version)

Swagathon

Page 24: The Agile PMO (fall 2014 version)

Scientific Wild A$$ Guess…-athon

Page 25: The Agile PMO (fall 2014 version)

The Spirit...

Page 26: The Agile PMO (fall 2014 version)

The Process…

Page 27: The Agile PMO (fall 2014 version)

The era of false hope.

Page 28: The Agile PMO (fall 2014 version)

Swagathon Retrospective

What works well with this model? What doesn’t work well?

Page 29: The Agile PMO (fall 2014 version)

Swagathon Retrospective

What we learned... ●  We were still on the “less valued” side of the Manifesto

o  ...we were following a plan instead of developing working software

o  ...we spent too much time on processes and tools

●  Creating “on the fly” teams was challenging

●  We were giving people false hope with our backlog

●  We could respond to change easier, but we were still missing a bigger story...

Page 30: The Agile PMO (fall 2014 version)

The Social Experiment

Page 31: The Agile PMO (fall 2014 version)

The Social Experiment

Page 32: The Agile PMO (fall 2014 version)

Product Visionary Driving product vision and strategic innovation. Strong point of view. PR and Relationship Manager Managing the external view of the team. Communicates well both verbally and via email. Knows how to deliver an excellent presentation. Product Ideator Thinking creatively and driving tactical innovation. Being the voice of the customer. Visual Designer Creates on-brand visual designs. UX Build wireframes, runs usability tests, designs user interactions. Coder Writes feature and test code. Create queries and reports. Product Marketer Analyzes the market and competitive landscape, determines product/feature positioning so the customer clearly understands the benefit, figures out ways to drive traffic to the product or feature. Business thinker Driving KPI thinking. Understanding business mechanics. Sizing opportunities.

Organizer Driving planning of work, running productive meetings, keeping the team focused on execution. Engineering Architect High level system design. Managing technical debt. Building for the right amount of performance and scale. Providing technical leadership and mentorship. Quality Manager Ensuring the quality of releases. Making sure that the right amount of automation is built (unit tests). Motivator Creating a sense of urgency while ensuring a sustainable pace for the team. Cruise Director Making things fun. Creating a sense of team spirit. Analyst Drives product instrumentation. Proposes tests (e.g. a/b tests). Analyzes data. Creates and tests hypotheses and uses these to influence product direction. Can clearly communicate what data means. Technical Operator Drives product instrumentation. Pays attention to production operational parameters (alerts, tuning, etc).

You are more than your job title!

Page 33: The Agile PMO (fall 2014 version)

Coder Write features and test code. Create queries and reports

Page 34: The Agile PMO (fall 2014 version)

Cruise Director Making things fun. Creating a sense of team spirit.

Page 35: The Agile PMO (fall 2014 version)

Motivator Creating a sense of urgency while ensuring a sustainable pace for the team.

Page 36: The Agile PMO (fall 2014 version)

The Social Experiment Retrospective

What works well with this model? What doesn’t work well?

Page 37: The Agile PMO (fall 2014 version)

The Social Experiment Retrospective

What we learned... ●  We know how our work ties into a bigger story

●  We know we are working on the things that matter the most

●  We want to continue to get better at Collaboration

●  Valuing Individuals and Interactions is key

●  Responding to Change will always be challenging

Page 38: The Agile PMO (fall 2014 version)

H E A T H E R F L E M I N G • S E N I O R D I R E C T O R , P M O • G I L T • @ H F L E M I N G J U S T I N R I S E R V A T O • D I R E C T O R , P R O G R A M M G M T • G I L T • @ S H A R K S N M E R M A I D S

Thank You!