Jennifer Beecher's talk on dealing with change at Product Tank Berlin on Continuous Discovery.

1. REMEMBERING THE
AGILE IN AGILE
Jennifer Beecher

2. MY BACKGROUND
Product Management
Engineering
Coaching
Training

3. dealing with change
potential for conflict
new requirements late in the game

4. “Welcome changing requirements,
even late in development.
-Agile Manifesto

5. CHANGE?!?

6.
Jennifer’s
6 CS OF CHANGE

7. #1 CONTEXT

8. Shared Strategy
Process
Change Briefing
Share the process and the conversations
Change is a conscious decision that doesn’t
just happen when people aren’t looking

9. #2 CONVERSATION

10. Discovery
is
information
Roundtables
Valuable information is hard to resist, unlike
decisions imposed on you
Before, during, after:
address concerns early, gather valuable input

11. #3 CROSS-POLLINATE

12. Consulting Rotation
Story Grooming
Always someone from the “other” team
included to inform, represent, contribute, share
Groom stories together so they become
everyone’s thing

13. #4 CONSIDER

14. Impact Assessment
Improvement
Opportunities
Understand tech debt, dependency changes,
opportunity cost - “Embrace the Suck”
Can you improve to avoid/predict/prepare
changes of this category in the future?

15. #5 CONFIRM

16. Publish all your
findings
Document and call out
validation
Don’t just focus on what you learned that
changes everything
Learning what’s good as is is valuable -
shout it from the roof tops

17. #6 CELEBRATE

18. Silly celebration
traditions
Change is knowledge
gained
Buzzers, confetti, ice cream, stuffed animals -
anything goes.
Reframe how you communicate change and
embrace that you gained knowledge

19. #1 CONTEXT
#2 CONVERSATION
#3 CROSS-POLLINATE
#4 CONSIDER
#5 CONFIRM
#6 CELEBRATE
Thank you!
Questions?
jen@fyulwood.com