PDN Overview
•Download as PPTX, PDF•
0 likes•1,390 views
The document discusses Pearson's Developer Network (PDN) program. It provides an overview of the PDN, including that it is made up of people, processes, and tools to support Pearson's APIs. It notes the value of the PDN is in reducing learning curves and supporting APIs independently or with API management solutions. The rest of the document details the components of the PDN program, including promotion and onboarding of developers, content and support, and addresses challenges and opportunities in cataloging, documenting, and promoting APIs across Pearson to take advantage of new technologies.
Recommended
More Related Content
Viewers also liked
Viewers also liked (18)
Similar to PDN Overview
Similar to PDN Overview (20)
PDN Overview
- 3. PDN Myth vs Reality Internal and External No difference between and Internal only program and an Internal, partner, client, and open program 1 Program and Pan Pearson PDN is a program consisting of people, processes, and tools capable of supporting all of Pearson 2 Value Add PDN increase productivity by reduce the learning curve. Result is significant cost savings) 3 Vendor Agnostic PDN is a stand alone program that can work independently of an API Management Solution or in conjunction with 4
- 4. Agenda API as a Product refers to the need of product like packaging and support API Product PDN is a program built on processes, workflows, and tools Program Value of PDN is recognized with you look at a central vs. decentralized approach. Value PDN is a solution that we can use to address several challenges and opportunities Opportunity This is all great but where are we going. Next Steps PDN is a program but team makes it successful Team
- 5. API as a Product
- 6. API as a Product obscure piece of Programming, powerful piece of Technology, powerful business Tool Marketing and Promotion People and teasm have to know the API exists before it can be used 1 Location and Information There has to be a single place to find information about and accessing the API. 2 Grouping and Versioning APIs need to be grouped like functionality in a product and versioned so the latest is obvious 3 Support Just as a product needs support in the form of a helpdesk, APIs need support in a very similar fashion 4
- 8. Currently Decentralized Geo’s Business Lines Enterprise Teams Next Gen Curren t Gen Current environment is Inefficient and Costly Teams.1000’s Capabilities1000’s For Example: PI
- 9. 60% 40% 5% 10% Decentralized – Time associated with API Support PDN – Time associated With API support Decentralized – Time associated with discovery and learning PDN – Time associated with discovery and learning Associated Effort and Value
- 10. Open Incremental Private Incremental API Majority of effort, early. Internal Incremental. Partner Build and treat as a product regardless of intended audience.Productize Early Incremental, not Either, Or
- 11. PDN Program
- 12. Is and IS NOT Fact 01 Portal. Fact 02 Governance Fact 03 Vendors Fact 01 Processes Fact 02 Standards Fact 03 Tools IS ISN’T
- 13. 10% 20% 40% 30% Promotion.1 Onboarding2 Content.3 Support.4 The PDN is a set of programs and processes that can be grouped into 4 sets of activity (or categories) Activity Breakdown What we DO
- 15. Consumer & Publisher Onboarding
- 16. Onboarding, Education, and Self Service Access Access to PDN and APIs must be automated and timely. 1 Documentation APIs must be well documented and easily understand 2 Code Samples A picture is worth a thousands words. A sample is worth a thousands tries 3 Sample Apps Demonstrate how multiple APIs interact with one another and demonstrate reuse 4 Onboarding and Education
- 17. Support for Publishers, Consumers, Partners and the Company as a whole the printing Consumers Developers, teams, and laypeople who want to understand and use the APIs 1 Publishers Teams who create APIs 2 Partners Different divisions, 3rd parties and/or clients 3 Company The combination of all 3 make the program a success. 4 Who we Support
- 18. 30%30% 20% 15% 5% Onboarding Integrations Tickets Samples Workshops Support comes in many forms. There is a natural cycle of learning about a suite of APIs, sharing this expertize, identifying areas that are difficult to understand and simplifying. Type of Support
- 20. Challenges and Opportunities We have a unique opportunity to take advantage of the PDN by cataloguing all APIs to insulate Pearson from security holes, lose of domain knowledge, and take advantage of the newly evolving next generation of technologies 0 1 0 2 0 4 0 5 0 3 APIs Everywhere Losing Knowledge Informed Next Gen is Now OnePearson APIs are all over Pearson, unknown and undocumented As we lose people, we lose their associated knowledge of technology. We are unaware as an organization of many technical capabilities Perfect opportunity to add APIs to the PDN as they are developed rather than afterwards Straightforward and simple way to achieve OnePearson
- 21. The Team
- 22. Team Members. Program Director PDN Allen Rodgers Manager Onboarding and Education Launa Stiles Manager Developer Services and Support Matt Dalzell Director PDN Europe Warwick Bailey
- 23. Team Members Manager Onboarding and Education Launa Stylese Manager Developer Services and Support Matt Dalzell Director PDN Europe Warwick Bailey
- 24. Next Steps
- 25. Next Steps Compliance Architecture Onboard Promote 01 02 03 04