Tiffany Jachja, an engineering manager at Autodesk, outlines a framework for developer enablement aimed at scaling software delivery through effective engagement, feedback, and community building. The document highlights the importance of continuous integration, delivery practices, and proactive developer support to improve productivity, reduce defects, and enhance time to market. It emphasizes identifying developer needs, creating supportive communities, and facilitating training to empower developers and address common challenges.

1. Scaling Software Delivery
TIFFANY JACHJA
ENGINEERING MANAGER
AT AUTODESK
A framework for developer enablement through DevRel and Outreach

2. I coach, mentor, and manage a global developer
enablement support team.
I started my career off as an engineer consulting
fortune 500 companies. Eventually, I specialized in
digital transformations, developer relations, data,
and program management. Now I use my cloud-
native development and delivery expertise to help
engineers deliver their best work.
Hi! I'm doing this work at Autodesk
Tiffany Jachja
Engineering Manager at Autodesk
Career Coach at Correlation One
@TiffanyJachja

3. Introduction
The Framework
Q&A!
SLIDE 4
SLIDE 15
SLIDE 34
Agenda

4. We know it and have known, throughout the years. 60% Reduction in production defects
2x Improvement in time to market
37% Reduction in developmenet time
Current research shows what's
possible.

5. We know it and have known, throughout the years.
• The 2020 State of DevOps Report by Puppet found that high-
performing organizations are able to deploy code 46 times more
frequently than low performers.
• Atlassian found that organizations that adopt DevOps practices
achieve 30 times more frequent deployments and 60 times
fewer failures.
60% Reduction in production defects
2x Improvement in time to market
37% Reduction in developmenet time
Current research shows what's
possible.

6. We know it and have known, throughout the years.
• The 2020 State of DevOps Report by Puppet found that high-
performing organizations are able to deploy code 46 times more
frequently than low performers.
• Atlassian found that organizations that adopt DevOps practices
achieve 30 times more frequent deployments and 60 times
fewer failures.
• Forrester Research revealed that organizations implementing
CI/CD pipelines experience a 200% improvement in time-to-
market and a 60% reduction in defects.
• Journal of Systems and Software reported that Agile
methodologies lead to a 37% reduction in development time and
a 16% increase in customer satisfaction.
60% Reduction in production defects
Improvement in time to market
37% Reduction in developmenet time
Current research shows what's
possible.
2x

7. There's a general consensus on what will get you there.
Insert words! :)

8. Insert words! :)
Continuous Integration, Continuous Delivery, Continuous Testing, Infrastructure as Code, Project
Management, Configuration Management, Observability, Automation, Continuous Improvement,
GitOps, Chaos Engineering, Feature Flags, SRE, Platform as a Service, API First, Please stop me.
There's a general consensus on what will get you there.

9. Insert words! :)
Continuous Integration, Continuous Delivery, Continuous Testing, Infrastructure as Code, Project
Management, Configuration Management, Observability, Automation, Continuous Improvement,
GitOps, Chaos Engineering, Feature Flags, SRE, Platform as a Service, API First, Please stop me.
People Process Technology
There's a general consensus on what will get you there.
In summary:

10. So how do we scale this?
Developer
Enablement!
This talk is about the how. Hopefully it'll give you some ideas on how to
enable developers to scale better software delivery!

11. Enablement
Delivery Platforms and
Services
Why DevRel and Outreach?
By building relationships, providing support, and fostering
a strong developer community, these activities contribute
to the success of both developers and the company they
represent.
Developers

12. DevRel
Delivery Platforms and
Services
Why DevRel and Outreach?
Developers
DevRel works to support developers, foster a vibrant developer
community, & drive the adoption and success of the company's
products, services, or platforms within the developer ecosystem.

13. Don’t hurt on productivity.
Here's the framework:
Drive success, maxmize impact, and minimize interruptions.
Don’t hurt on productivity.

14. Drive success, maxmize impact, and minimize interruptions.
Don’t hurt on productivity.
Target Fix Facilitate
Here's the framework:

15. Target Fix Facilitate
developer activities that will sustain
software delivery.
incidents on the spot to empower
developers.
platform trainings & services to stop
developers from introducing vulnerabilities.
The Framework.

16. This is how to do it.
1. Identify What is the problem and
what is the feedback from
developers?
2. Activiate
Engage with the ecosystem,
its stakeholders and
developers.
3. Action Close the feedback loop.

17. Target
developer activities that will sustain
software delivery.

18. Identitfy.
Getting the most of this process.
Look at the entire SDLC and look to different demographics of
developers. Feedback includes bug reports, survey results,
feature requests, and suggestions for improvement.
Theses insights and needs will be a conduit for developing and
enhancing delivery services and systems.
This is different from DORA metrics.
This is NOT a measure of productivity.
Target

19. Identitfy.
Getting the most of this process.
I repeat. This is different from DORA metrics.
Here is an example of a productivity dashboard.
If you have a productivity dashboard, consider solutions where
DORA metrics can be easily obtained from your CI/CD solution.
We're not measuring productivity to target DevRel activities.

20. Activate.
Getting the most of this process.
By organizing events, meetups, conferences, and online
forums, we can create spaces where developers can connect,
share knowledge, and collaborate.
These communities provide opportunities for developers to
learn from each other, seek help, and find solutions to
common challenges.
It's important to create an forums or spaces that don't already
exist but will be needed to sustain the team.

21. Activate.
Getting the most of this process.
By organizing events, meetups, conferences, and online
forums, we can create spaces where developers can connect,
share knowledge, and collaborate.
These communities provide opportunities for developers to
learn from each other, seek help, and find solutions to
common challenges.
It's important to create an forums or spaces that don't already
exist but will be needed to sustain the team.
When we talk about performance consider:
1. the business,
2. the team,
3. and the technical impact.

22. Action.
Getting the most of this process.
Push vs Pull model for developer activities.
Close the loop!
We created a site for stakeholders to quickly access
events, resources, and other enablement activities.
The site spotlights our solutions, partners,
customers, and team.

23. Fix
incidents on the spot to empower
developers.

24. Getting the most of this process.
Improve productivity and lower idle costs.
We made the process open by creating a space where
developers can report and issue their incidents.

25. Getting the most of this process.
Improve productivity and lower idle costs.
We made the process open by creating a space where
developers can report and issue their incidents.
We understood the issues and resolved them.
Followed up with the internal product/platform teams
to enhance developer experience.

26. Fix
Know who and what you
need early on.
Getting the most of this process.

27. Facilitate
platform trainings & services to stop
developers from introducing vulnerabilities.

28. Learning takes places in real time and in practical settings.
Repeated exposure to processes stops developers from
committing the errors that create vulnerabilities or failures.
Name the divide. What are you able to facilitate?
Will you be improving the developer experience and
addressing any issues or gaps in the product offerings?
Will you provide educational resources, tutorials, documentation,
and other materials that help developers understand and effectively
use the company's products or services?
Facilitate
Identitfy.
Getting the most of this process.

29. Educational resources, tutorials, documentation, and other
materials that help developers understand and effectively use
the company's products or services.
Here are some tips.
• Train SMEs to be able to train SMEs.
• Keep initatives and responsbilies tied to a career ladder.
• Ensure staff members understand the nuances in becoming
a developer enablement engineer.
• Ensure leadership is aligned and invested.
Activate.
Getting the most of this process.

30. Activate.
Getting the most of this process.
Sample career ladder.

31. Activate.
Getting the most of this process.
There are differences between developer enablement and developer development.

32. Facilitate
Action.
Getting the most of this process.
We created a knowledge portal.
These should consist of the following:
• Troubleshoot guides
• Quick starts
• Best practices & Training Material

33. In Summary
1. Identify What is the problem and
what is the feedback from
developers?
2. Activiate
Engage with the ecosystem,
its stakeholders and
developers.
3. Action Close the feedback loop.
Be seen in the community! Share, document,
experiment and encourage your developers to the
same.

34. Thank you!
Questions?
@TiffanyJachja
/
Contact:
tiffany.jachja@autodesk.com