agile at opm: the usajobs product owner perspective

24
Agile @ OPM: the USAJOBS Product Owner Perspective By Alesia Booth & Richard Cheng

Upload: excella-consulting

Post on 06-Jul-2015

140 views

Category:

Presentations & Public Speaking


3 download

DESCRIPTION

Alesia Booth and Richard Cheng's presentation from AgileDC on October 21, 2014

TRANSCRIPT

Page 1: Agile at OPM: the USAJOBS Product Owner Perspective

Agile @ OPM: the USAJOBS Product Owner Perspective

By Alesia Booth & Richard Cheng

Page 2: Agile at OPM: the USAJOBS Product Owner Perspective

http://www.flickr.com/photos/psd/2423294079/sizes/l/in/photostream/

Page 3: Agile at OPM: the USAJOBS Product Owner Perspective

Richard Cheng

Principal and Agile practice lead at Excella Consulting

CST, CSM, CSPO, CSP, PMP, PMI-ACP

Founder and executive committee member for the Agile Defense Adoption Proponents Team (ADAPT)

Performed Agile training, assessment, and coaching at USAJOBS

3

Page 4: Agile at OPM: the USAJOBS Product Owner Perspective

Alesia Booth

20+ years of Federal HR experience

10+ years of Federal hiring policy and systems experience

Certified Scrum Product Owner

Acted as Product Owner for development of USAJOBS 3.0

Continuing to work on recruitment data standards and talent management systems as the Program Manager for USA Staffing®

Page 5: Agile at OPM: the USAJOBS Product Owner Perspective

USAJOBS – stats

More than 24M visits

More than 8M logins

More than 10k average daily job postings

Nearly 95M average monthly searches

Customer Satisfaction ACSI Score of 74

5

Page 6: Agile at OPM: the USAJOBS Product Owner Perspective
Page 7: Agile at OPM: the USAJOBS Product Owner Perspective

Why Agile?

Page 8: Agile at OPM: the USAJOBS Product Owner Perspective

Agile Values

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 9: Agile at OPM: the USAJOBS Product Owner Perspective

Agile Principles

1. Satisfy the customer through early and continuous

delivery

2. Welcome changing requirements

3. Deliver frequently, preferring a shorter timescale

4. Business & technical work together daily

5. Pick the right team and trust them

6. Face-to-face Communication

7. Working software is the primary measure of progress

8. Sustainable pace

9. Technical excellence and good design enhances agility

10. Simplicity, maximizing the amount of work not done

11.Best results emerge from self-organizing teams

12.The team regularly reflects to become more effective

Page 10: Agile at OPM: the USAJOBS Product Owner Perspective

Scrum

Page 11: Agile at OPM: the USAJOBS Product Owner Perspective

Need Iterative & Incremental Approach

Page 12: Agile at OPM: the USAJOBS Product Owner Perspective

Outcome

Page 13: Agile at OPM: the USAJOBS Product Owner Perspective

Stakeholder Benefits

13

Page 14: Agile at OPM: the USAJOBS Product Owner Perspective

Obstacles & Lessons Learned

http://www.flickr.com/photos/7821771@N05/4679360979

Page 15: Agile at OPM: the USAJOBS Product Owner Perspective

Mindset

15

Page 16: Agile at OPM: the USAJOBS Product Owner Perspective

Know the Terminology

Page 17: Agile at OPM: the USAJOBS Product Owner Perspective

Requirements

17

Page 18: Agile at OPM: the USAJOBS Product Owner Perspective

Distance

18

Page 19: Agile at OPM: the USAJOBS Product Owner Perspective

Security/508 Compliance

19

Page 20: Agile at OPM: the USAJOBS Product Owner Perspective

Get Shovel Ready

20

Page 21: Agile at OPM: the USAJOBS Product Owner Perspective

Scope Creep

21

Page 22: Agile at OPM: the USAJOBS Product Owner Perspective

Train and Reinforce Agile

22

Training

CoachingMentoring

Page 23: Agile at OPM: the USAJOBS Product Owner Perspective

Good ScrumMaster

23

Page 24: Agile at OPM: the USAJOBS Product Owner Perspective

Final Words

24

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Agile Principle #12: