How Wiley Streamlines Developer Collaboration with Copado
by the Numbers
10,000+
Research Institutions
16 Million+
Research Audience
12 Million+
Professionals
1000
Corporate Partners
About the company
John Wiley has been helping people and organizations develop the skills and knowledge they need to succeed for over 200 years. John Wiley develops digital education, learning, assessment, and certification solutions to help universities, businesses, and individuals move between education and employment and achieve their ambitions. By partnering with learned societies, they support researchers to communicate discoveries that make a difference.
Table of contents
Share
John Wiley started using Salesforce in 2009 and saw vast improvements in their business after the implementation. This morphed into lines of business creating their own instances, which quickly became difficult to manage. They decided on the need to consolidate the six instances back into one single instance. John Wiley felt that they were still very much on a journey to be able to truly maximize and capitalize on their Salesforce investment.
The initial developer team at John Wiley was a small team of 5 members, making it relatively easy to stay aligned and collaborate together. But as the organization grew and started scaling to over 50+ employees, this initial ease of teamwork seemed to vanish as more and more hires were brought on and teams began splitting to support different lines of business. This was amplified by the fact that their release process was entirely dependent on changesets, which required lots of manual intervention and effort.
Finding a Way to Avoid Development Delays and Scale Releases
Changesets meant that conflicts were often missed, and with no central source of truth or version control, teammates found themselves negatively impacting each other. They had to stop everything that was in development and manually intervene and rebuild. As the complexity in innovation grew, the conflicts rising along with it became worse.
Each conflict caused a delay in deployments and a decrease in release velocity and an increase in frustration across the teams. The team knew this could not go on and that something needed to change in order to be able to scale efficiently.
Key Challenges
The Solution
John Wiley started seeing results with Copado as soon as they implemented the tool. Copado’s automation functionality lets them push innovation through with utmost ease. When conflicts arise, they immediately become visible through the monitoring features.
Conflicts now get immediately reviewed, tested and signed off within hours. Having complete visibility of the entire pipeline lets them scale effectively without the fear of impacting one another. This has led to a better and more consistent experience for their users and improved customer satisfaction.
The Future
With Copado, John Wiley is able to push changes from their sandboxes and training environments through to production with the confidence that all the code is safe and secure. Copado provides the team with the visibility and automation to guarantee a successful deployment on a weekly basis.
Through its flexibility, the team is now able to work in a collaborative and streamlined manner. “No more components are missed when deployments happen, which increases our user satisfaction,” reports Lyons.
.svg){kind=small}
.avif)
.svg)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.svg)
.svg)
.svg)