000 03655nam a22003015i 4500
001 239001
003 ES-VaUE
005 20240306114251.0
007 cr nn 008mamaa
008 210915s2021 xxu| o |||| 0|eng d
020 _a9781484271643
024 7 _a10.1007/978-1-4842-7164-3
_2doi
040 _aES-VaU
_bspa
_cES-VaU
_dES-VaU
050 4 _aHF4999.2-6182
_b2021 EB
100 1 _aLewko, Caroline.
_eautor.
_4aut
_4http://id.loc.gov/vocabulary/relators/aut
245 0 0 _aDeveloper Relations :
_bHow to Build and Grow a Successful Developer Program
_cby Caroline Lewko, James Parton
250 _a1st ed. 2021.
264 1 _aBerkeley, CA
_c2021
_bSpringer International Publishing
300 _a1 recurso en línea
336 _atexto
_btxt
_2rdacontent
337 _aelectrónico
_bc
_2rdamedia
338 _arecurso electrónico
_bcr
_2rdacarrier
505 0 _aPart 1: Developing a Common Understanding -- 1. What is Developer Relations? -- 2. Where does Developer Relations Fit?- 3. The Origin of Developer Relations & The Rise of the Developer -- 4. The Value of the Developer Economy -- Part 2: The Key Differentiators of Developer Relations -- 5. The Audience: Developers -- 6. Developers as Decision Makers -- 7. Developer First & Dev Plus -- 8.Business Models -- 9. Developer Products -- Part 3: Alignment on Goals -- 10. Corporate Alignment -- 11. Program Goals -- Part 4: Go to Market/Strategy Activation -- 12. Developer Segmentation -- 13. Developer Personas -- 14. Developer Messaging -- 15. The Developer Journey -- 16. Discover -- 17. Developer Experience -- 18. Evaluate -- 19. Learn -- 20. Build -- 21. Scale -- 22. Communities.-Part 5: Measure -- 23. Metrics -- Part 6: Growing Your Program -- 24. Team -- 25. Program Maturity -- 26. What Comes Next? -- Appendix.
520 _aIncreasingly, business leaders are either looking to start a new developer program at their company or looking to increase the impact of their existing DevRel program. In this context, software developers are finally recognized as legitimate decision makers in the technology buying process, regardless of the size of their organization. New companies are appearing with the sole purpose of making tools for developers, and even companies whose primary focus was elsewhere are waking up to the developer opportunity. Even as the need and demand for DevRel has grown, there are still re-occurring challenges for DevRel leaders. It is these challenges that this book addresses, covering all aspects of a DevRel program. It is an essential reference to professionalize the practice of developer relations by providing you with strategic, repeatable, and adoptable frameworks, processes, and tools, including developer segmentation and personas, and developer experience frameworks. In Developer Relations, you'll find the answers to the following questions: How do we convince stakeholders to support a program? How do we go about creating a program? How do we make developers aware of our offer? How do we stand out from the crowd? How do we get developers to use our products? How do we ensure developers are successful using our products? How do we measure success? How do we maintain the support of our stakeholders? After reading this book you'll have a clear definition of what developer relations is, the type of companies that engage in DevRel, and the scope and business models involved. .
856 4 0 _uhttps://go.openathens.net/redirector/universidadeuropea.es?url=https://doi.org/10.1007/978-1-4842-7164-3
_zAcceso a este recurso digital (usuarios Universidad Europea de Valencia)
942 _2lcc
_cLE
988 _aSpringer_Business_2021
999 _c239001
_d239001