We consistently hear that good UX practices and scrum don’t mix. We disagree. Over the past 5 years, we’ve evolved an agile scrum process for producing UX deliverables on time and within constraints. Our process allows us to meet project requirements and deadlines and fits in UX best practices such as: use of personas, iterative design, and user validation. The best part is… we’re going to share it with you. We will share these parts of our UX Agile mixology: Step by step detail on our scrum practices, including a process flow diagram for how we integrate with the development lifecycle Our special blend of story patterns that fit varying needs that audience members can take home and mix into to their own working environments How we structure our UX Team, including the secret ingredients in our team’s success

1. Carol Bergantino
Jennifer Bullard
UXPA Boston 2017
UX Neat, Agile Chaser
Your step-by-step guide for blending UX and
Agile in a busy development organization
© 2017 VERACODE, All Rights Reserved.

2. 2
• A newly acquired business unit of CA Technologies
• ~540-person organization, ~10 years old
• Software development organization experiencing multiple transformations
- Monolith  Microservices
- Agile  DevOps
• Cloud services that identify security vulnerabilities in the application layer
• Customers include retail, banking, software, and healthcare companies
About Veracode
© 2017 VERACODE, All Rights Reserved.

3. 3
Organizational Structure
UserExperience
The Product
• Three-Legged Stool
- User Experience
- Product Management
- Engineering
Ideal Organization
© 2017 VERACODE, All Rights Reserved.
Don Norman
The Invisible Computer
https://www.nngroup.com/articles-want-human-centered-development-reorganize/

4. 4
The Product
Organizational Structure
• Three-Legged Stool
- User Experience
- Product Management
- Engineering
Our Organization
© 2017 VERACODE, All Rights Reserved.

5. 5
• Team composition:
- 6 UX Designers (and we’re hiring!); 2 UA Writers; 1 Course Designer; 1 UX Director
• UX team is centralized and serves multiple development scrum teams
- Agile Teams
- 18 Dev scrum teams
• Maintain a separate backlog (this will be important later)
• Designer will embed in other scrum teams when relevant
Centralized UX Team
© 2017 VERACODE, All Rights Reserved.

6. 6
• Mission: Increased UX Capacity
• UX Guild members are from Development or QA that serve as a UX
resource for their team
• Each product team has a UX Guild member
• Smaller stories, such as small UI additions or text changes, can be
assigned to a UX Guild member
• We use the buddy system, pattern library, and UX reviews
UX Guild
© 2017 VERACODE, All Rights Reserved.

7. 7
Ingredients:
o Product Roadmap
o Centralized UX Team
o UX Guild
o Pattern Library
o UX Bat Signal
o Documented Process
o Story Patterns
Our Recipe
© 2017 VERACODE, All Rights Reserved.
Steps to Follow:
Step 1: High Level UX Estimates for Roadmap
Step 2: Resource Upcoming Roadmap Items
Step 3: Decompose Epics Into Stories (Grooming)
Step 4: Size and Subtask Stories (Grooming)
Step 5: Prioritization and Planning
Step 6: Design, Review, and Deliver (On-time!)

8. 8
• 12 Month forecast/roadmap from Product Management (revised quarterly)
• Product Management writes epics from roadmap
• Work is estimated (t-shirt sized) by Dev + UX in Parallel
- 2 separate estimates; 1 unified process
- T-shirt sizes: XS = 6 weeks/1 UX designer; S = 12 weeks; M = 24 weeks; etc.
• Sets expectations and delivery dates for UX work
• Ensures UX is properly staffed for the amount of Dev work on roadmap
Step 1: High Level UX Estimates for Roadmap
Key Ingredient/s: Product Roadmap
© 2017 VERACODE, All Rights Reserved.

9. 9
• Ensures UX is properly staffed for the
amount of Dev work on roadmap
Step 2: Resource upcoming Roadmap Items
Key Ingredient/s: Product Roadmap
© 2017 VERACODE, All Rights Reserved.

10. 10
• Dev clones roadmap epics and decomposes into stories
• Bat signal
- Stories requiring UX are labeled “ux_needed”
- Anyone can label a story with the bat-signal
- Stories with the label are visible on our bat-signal board
• Needs Analysis in Grooming:
- UX Guild or UX Designer?
• UX clones dev stories requiring a designer
Step 3: Decompose Epics Into Stories (Grooming)
Key Ingredient/s: Bat Signal; Documented Process
© 2017 VERACODE, All Rights Reserved.

11. 11
• Each pattern contains an established set of
sub-tasks with varying degrees of fidelity
• Patterns include:
- Discovery
- Design Thinking
- UX Wireframing
- Validation
Step 4: Size and Subtask Stories (Grooming)
Key Ingredient: Story Patterns
© 2017 VERACODE, All Rights Reserved.

12. 12
• Prioritize in UX backlog based on target release
• UX Designers can swarm
Step 5: Prioritization and Planning
Key Ingredient/s: Centralized UX Team
4th Quarter
1st Quarter
3rd Quarter
2nd Quarter
Project B
UX Project A Dev Project A
UX Project B Dev Project B
UX Project C Dev Project C
UX Project D
© 2017 VERACODE, All Rights Reserved.

13. 13
• Prioritize in UX backlog based on target release
• UX Designers can swarm
Step 5: Prioritization and Planning
Key Ingredient/s: Centralized UX Team
© 2017 VERACODE, All Rights Reserved.
Design Code Test Deploy
Design
Design DeployCode Test Code Test Code Test Code Test
Waterfall
Agile
DevOps

14. 14
• Designer drives design work
• Acceptance criteria for all designs:
- Doc Review
- Design Review
• Exceeding our goal of "90% delivered within one release of target"
Step 6: Design, Review, and Deliver (On-time!)
Key Ingredient/s: Centralized UX Team; Pattern Library
© 2017 VERACODE, All Rights Reserved.

15. 15
Documented
Process

16. 16
• What works well
- Estimating UX work for roadmap epics
- Seeing across all work/teams in UX scrum
- Scaling UX designers across multiple projects
- Scaling via the UX Guild
- UX pattern library
• What could be better
- Still need to ask to be invited to PM + Dev meetings, like PM/PO
- Educating dev teams + PMs on UX process is ongoing
- Governance of ng components that align with the UX pattern library
+/-
© 2017 VERACODE, All Rights Reserved.

17. Carol Bergantino: cbergantino@veracode.com
Jennifer Bullard: jbullard@veracode.com
Questions?
© 2017 VERACODE, All Rights Reserved.

18. THANK YOU