Product and project managers DevOps journey to Continuous Delivery What do product and project managers do when waterfall goes away? How did our customers/users react to this transition? What changes did we bring about? and How long did it take us to get here? This talks presents our journey with our customers/users in Red Hat Developers Group. Our approach to bridge the gap between Dev & Ops was to give the teams not only the ability to build, deploy the code to production but also manage the service delivery aspects. We even managed to incorporate end-user feedback into our continuous delivery model. This talk will review how we crossed the following hurdles. - ‘Culture follows structure’ hence org change from two different Dev & Ops departments to just one - Transition from just building products to running and managing services in production. - Release schedules didn’t disappear, they simply served as a marker on our continuous delivery path. - Continue to focus on reducing dependency on Service Delivery teams - balancing access & security. - Invested in building toolchains that minimized and automated efforts to build, deploy & maintain code. - Continuous feedback channels such as user behaviour via telemetry, stability via monitoring tools etc. - Redefined business value by focusing on flexible architecture that allows for easy extensibility via plugins. - Engagement with community & customers via several touch points and direct access to developers.

1. Product & Project Manager’s
DevOps Journey to
Continuous Delivery
Ranjith Varakantam
Principal Agile Coach

2. developers.redhat.com

3. Ranjith Reddy V.
Principal
Agile Coach
Developer Tools:
Globally distributed
teams spread over 16
countries, across 6
time zones and
working on half a
dozen projects.

4. Red Hat CodeReady
Workspaces
che.openshift.io

5. Novelty to Curiosity, Resistance to Change &
Finally to Experimentation & Adoption

6. Ideas, Experiments & Investments that
helped our DevOps culture to evolve

7. Imagine two people directing this team!

8. Security
PII Data
Storage
Dev Vs SRE

9. From just building products to running
and managing services

10. Release schedules, patches, forks &
versioning simply served as a markers
on our continuous delivery path

11. Toolchains & Responsive
Infrastructure

12. Containers allow for dynamic env.
creation

13. Complete Transparency
Visibility into Services
End-to-End Coverage
Monitoring & Alerts
Ability to toggle features on/off

14. On the Product
Management Side

15. Connecting with
Community

16. Conferences - Open Calls -
Meet ups - Open Repositories

17. Conversations & Feedback Loops

18. Telemetry - A window to
Patterns & Behaviours

19. Observing, Reflecting & Responding

20. Redefined architecture to allowed
for extensibility

21. VS Code
java
YAML
support
Stack
Insights
OpenShift
Connect

22. Start out an issue reported on Github
Discussions & Brainstorming
Progress to a Pull Request
Follow ups via chat/emails

23. Our journey
continues….