├── .github └── media │ ├── click-edit-pencil-icon.png │ ├── click-readme.md.png │ └── propose-changes.png ├── LICENSE ├── README.md ├── code-of-conduct.md └── contributing.md /.github/media/click-edit-pencil-icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/aleixmorgadas/awesome-engineering-strategy/080ce22aae0ad3e0d10c6d1c0c31030e43885c83/.github/media/click-edit-pencil-icon.png -------------------------------------------------------------------------------- /.github/media/click-readme.md.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/aleixmorgadas/awesome-engineering-strategy/080ce22aae0ad3e0d10c6d1c0c31030e43885c83/.github/media/click-readme.md.png -------------------------------------------------------------------------------- /.github/media/propose-changes.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/aleixmorgadas/awesome-engineering-strategy/080ce22aae0ad3e0d10c6d1c0c31030e43885c83/.github/media/propose-changes.png -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Creative Commons Legal Code 2 | 3 | CC0 1.0 Universal 4 | 5 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE 6 | LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN 7 | ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS 8 | INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES 9 | REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS 10 | PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM 11 | THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED 12 | HEREUNDER. 13 | 14 | Statement of Purpose 15 | 16 | The laws of most jurisdictions throughout the world automatically confer 17 | exclusive Copyright and Related Rights (defined below) upon the creator 18 | and subsequent owner(s) (each and all, an "owner") of an original work of 19 | authorship and/or a database (each, a "Work"). 20 | 21 | Certain owners wish to permanently relinquish those rights to a Work for 22 | the purpose of contributing to a commons of creative, cultural and 23 | scientific works ("Commons") that the public can reliably and without fear 24 | of later claims of infringement build upon, modify, incorporate in other 25 | works, reuse and redistribute as freely as possible in any form whatsoever 26 | and for any purposes, including without limitation commercial purposes. 27 | These owners may contribute to the Commons to promote the ideal of a free 28 | culture and the further production of creative, cultural and scientific 29 | works, or to gain reputation or greater distribution for their Work in 30 | part through the use and efforts of others. 31 | 32 | For these and/or other purposes and motivations, and without any 33 | expectation of additional consideration or compensation, the person 34 | associating CC0 with a Work (the "Affirmer"), to the extent that he or she 35 | is an owner of Copyright and Related Rights in the Work, voluntarily 36 | elects to apply CC0 to the Work and publicly distribute the Work under its 37 | terms, with knowledge of his or her Copyright and Related Rights in the 38 | Work and the meaning and intended legal effect of CC0 on those rights. 39 | 40 | 1. Copyright and Related Rights. A Work made available under CC0 may be 41 | protected by copyright and related or neighboring rights ("Copyright and 42 | Related Rights"). Copyright and Related Rights include, but are not 43 | limited to, the following: 44 | 45 | i. the right to reproduce, adapt, distribute, perform, display, 46 | communicate, and translate a Work; 47 | ii. moral rights retained by the original author(s) and/or performer(s); 48 | iii. publicity and privacy rights pertaining to a person's image or 49 | likeness depicted in a Work; 50 | iv. rights protecting against unfair competition in regards to a Work, 51 | subject to the limitations in paragraph 4(a), below; 52 | v. rights protecting the extraction, dissemination, use and reuse of data 53 | in a Work; 54 | vi. database rights (such as those arising under Directive 96/9/EC of the 55 | European Parliament and of the Council of 11 March 1996 on the legal 56 | protection of databases, and under any national implementation 57 | thereof, including any amended or successor version of such 58 | directive); and 59 | vii. other similar, equivalent or corresponding rights throughout the 60 | world based on applicable law or treaty, and any national 61 | implementations thereof. 62 | 63 | 2. Waiver. To the greatest extent permitted by, but not in contravention 64 | of, applicable law, Affirmer hereby overtly, fully, permanently, 65 | irrevocably and unconditionally waives, abandons, and surrenders all of 66 | Affirmer's Copyright and Related Rights and associated claims and causes 67 | of action, whether now known or unknown (including existing as well as 68 | future claims and causes of action), in the Work (i) in all territories 69 | worldwide, (ii) for the maximum duration provided by applicable law or 70 | treaty (including future time extensions), (iii) in any current or future 71 | medium and for any number of copies, and (iv) for any purpose whatsoever, 72 | including without limitation commercial, advertising or promotional 73 | purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each 74 | member of the public at large and to the detriment of Affirmer's heirs and 75 | successors, fully intending that such Waiver shall not be subject to 76 | revocation, rescission, cancellation, termination, or any other legal or 77 | equitable action to disrupt the quiet enjoyment of the Work by the public 78 | as contemplated by Affirmer's express Statement of Purpose. 79 | 80 | 3. Public License Fallback. Should any part of the Waiver for any reason 81 | be judged legally invalid or ineffective under applicable law, then the 82 | Waiver shall be preserved to the maximum extent permitted taking into 83 | account Affirmer's express Statement of Purpose. In addition, to the 84 | extent the Waiver is so judged Affirmer hereby grants to each affected 85 | person a royalty-free, non transferable, non sublicensable, non exclusive, 86 | irrevocable and unconditional license to exercise Affirmer's Copyright and 87 | Related Rights in the Work (i) in all territories worldwide, (ii) for the 88 | maximum duration provided by applicable law or treaty (including future 89 | time extensions), (iii) in any current or future medium and for any number 90 | of copies, and (iv) for any purpose whatsoever, including without 91 | limitation commercial, advertising or promotional purposes (the 92 | "License"). The License shall be deemed effective as of the date CC0 was 93 | applied by Affirmer to the Work. Should any part of the License for any 94 | reason be judged legally invalid or ineffective under applicable law, such 95 | partial invalidity or ineffectiveness shall not invalidate the remainder 96 | of the License, and in such case Affirmer hereby affirms that he or she 97 | will not (i) exercise any of his or her remaining Copyright and Related 98 | Rights in the Work or (ii) assert any associated claims and causes of 99 | action with respect to the Work, in either case contrary to Affirmer's 100 | express Statement of Purpose. 101 | 102 | 4. Limitations and Disclaimers. 103 | 104 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 105 | surrendered, licensed or otherwise affected by this document. 106 | b. Affirmer offers the Work as-is and makes no representations or 107 | warranties of any kind concerning the Work, express, implied, 108 | statutory or otherwise, including without limitation warranties of 109 | title, merchantability, fitness for a particular purpose, non 110 | infringement, or the absence of latent or other defects, accuracy, or 111 | the present or absence of errors, whether or not discoverable, all to 112 | the greatest extent permissible under applicable law. 113 | c. Affirmer disclaims responsibility for clearing rights of other persons 114 | that may apply to the Work or any use thereof, including without 115 | limitation any person's Copyright and Related Rights in the Work. 116 | Further, Affirmer disclaims responsibility for obtaining any necessary 117 | consents, permissions or other rights required for any use of the 118 | Work. 119 | d. Affirmer understands and acknowledges that Creative Commons is not a 120 | party to this document and has no duty or obligation with respect to 121 | this CC0 or use of the Work. -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Awesome Engineering Strategy [![Awesome](https://awesome.re/badge.svg)](https://awesome.re) 2 | 3 | > 🎉 How to design and execute engineering strategies for tech leadership. 4 | 5 | Engineering Strategy is a composition of resources such books, posts, templates, learning materials, and open engineering strategies made by the community and companies. 6 | 7 | Contributions are welcome! Check out the contribution guidelines for adding items to the list. 8 | 9 | ## Contents 10 | 11 | - [Books](#books) 12 | - [Posts](#posts) 13 | - [Videos](#videos) 14 | - [Methods](#methods) 15 | - [Courses and Workshops](#courses-and-workshops) 16 | - [Templates](#templates) 17 | - [Supporting Material](#supporting-material) 18 | - [Open Engineering Strategies](#open-engineering-strategies) 19 | - [Communities](#communities) 20 | - [Podcasts](#podcasts) 21 | 22 | ## Books 23 | 24 | - [Strategic Monoliths and Microservices: Driving Innovation Using Purposeful Architecture](https://www.goodreads.com/book/show/55782292-strategic-monoliths-and-microservices) - A set of strategic patterns on addressing business capabilities with a monolith and microservices approach. 25 | - [Technology Strategy Patterns: Architecture as Strategy](https://www.goodreads.com/book/show/42414767-technology-strategy-patterns) - A set of business tools and patterns from an engineering point of view. 26 | - [Staff Engineer: Leadership Beyond the Management Track](https://www.goodreads.com/book/show/56481725-staff-engineer) - How is the role of the staff engineer and how this role addresses the engineering strategy. 27 | - [Reaching Cloud Velocity: A Leader's Guide to Success in the AWS Cloud](https://www.goodreads.com/book/show/53503300-reaching-cloud-velocity) - A high-level book on business strategy, people, culture, data and architecture and how this drives cloud velocity. 28 | - [UN Global Platform Handbook on Information Technology Strategy](https://www.goodreads.com/book/show/55047345-un-global-platform-handbook-on-information-technology-strategy) - A set of wardley maps on IT. Bringing situational awareness to different contexts. 29 | - [Good Strategy Bad Strategy: The Difference and Why It Matters](https://www.goodreads.com/en/book/show/11721966) - Understand the core components of a strategy. 30 | - [The Value Flywheel Effect: Power the Future and Accelerate Your Organization to the Modern Cloud](https://www.goodreads.com/book/show/61167316-the-value-flywheel-effect?ac=1&from_search=true&qid=donxleC2tR&rank=1) - Using Wardley Mapping and other sensemaking approaches to help organizations anticipate market changes and user needs. 31 | - [Team Topologies: Organizing Business and Technology Teams for Fast Flow](https://www.goodreads.com/book/show/44135420-team-topologies) - Team Topologies is a practical, step-by-step, adaptive model for organizational design and team interaction based on four fundamental team types and three team interaction patterns. 32 | - [Thinking in Systems](https://www.goodreads.com/book/show/3828902-thinkingow-in-systems) - An essential introduction into system thinking. It helps the reader to understand the fundamentals and introduces several system traps and how to overcome them. 33 | - [Domain-Driven Design: Tackling Complexity in the Heart of Software](https://www.goodreads.com/book/show/179133.Domain_Driven_Design) - Strategic patterns to understand complex domains and how to model them based on the impact on the business competitive advantage. 34 | - [Implementing Domain-Driven Design](https://www.goodreads.com/book/show/15756865-implementing-domain-driven-design) - An implementation approach to DDD from strategic patterns to tactical patterns with code examples. 35 | - [Domain-Driven Design Distilled](https://www.goodreads.com/book/show/28602719-domain-driven-design-distilled) - An accessible book to learn the main concepts of Domain-Driven Design. 36 | - [Wardley Maps](https://medium.com/wardleymaps/on-being-lost-2ef5f05eb1ec) - A deep explanation of the origin of Wardley Maps up to the full understanding of how to do strategy which it is adaptive to the environment. 37 | - [Architecture Modernization. Socio-technical alignment of software, strategy, and structure](https://www.manning.com/books/architecture-modernization) - Concrete tools, techniques, and processes to align software architecture with your business domains, organizational design, team topologies, and corporate strategy. 38 | 39 | ## Posts 40 | 41 | - [Designing an Engineering Strategy Post Series](https://learnings.aleixmorgadas.dev/p/designing-an-engineering-strategy) - How to build an engineering strategy from 0. 42 | - [Engineering strategy](https://lethain.com/engineering-strategy/) - What's an engineering strategy. 43 | - [Defining a Tech Strategy](https://sarahtaraporewalla.com/agile/design/architecture/Defining-a-Tech-Strategy) - A high-level guideline on defining a tech strategy. 44 | - [Tech Strategy: You Need it, But What is it?](https://medium.com/nick-tune-tech-strategy-blog/tech-strategy-you-need-it-but-what-is-it-af292421e422) - In-depth reflection of what is a tech strategy. 45 | - [🗺🧭 Using Wardley Mapping to understand why Google made G. Appointments to compete in the Calendly market](https://learnings.aleixmorgadas.dev/p/-using-wardley-mapping-to-understand) - Using wardley mapping to understand google appointments. 46 | - [What is a Strategy? Why do you need one in Tech?](https://www.linkedin.com/pulse/what-strategy-why-do-you-need-one-tech-rui-felgueiras) - Introduction to what is a strategy for tech. 47 | - [Delivering on an Architecture Strategy](https://blog.thepete.net/blog/2019/12/09/delivering-on-an-architecture-strategy/) - Describes strategic architectural initiatives, a framework which allowing product peeps and techies to make progress on big technical improvements via aligned autonomy. 48 | - [ADR: Deep Dive into Architecture Decision Records](https://okorkmaz.medium.com/adr-deep-dive-into-architecture-decision-records-8c110ce7d74e) - Introduces what an architecture decision record is, describes the terminology, how to document the finalized architecture, and focuses on the best practices by presenting real scenerio. 49 | - [Strategy glossary](https://alexewerlof.substack.com/p/strategy-glossary) - Building a common language for vision, mission, goals, objectives, roadmap, plans, milestones, policies. 50 | - [Strategy basics](https://alexewerlof.substack.com/p/strategy-basics) - First in a series of posts about strategy why, how and what. 51 | - [Writing an engineering strategy](https://lethain.com/eng-strategies/) - A guide on how to write and document an engineering strategy. 52 | - [Architecture Modernization Enabling Teams (AMET)](https://esilva.net/articles/architecture-modernization-enabling-team) - Explains how AMET coordinates and upskills all teams and stakeholders in the modernization initiative. 53 | - [When and when *not* to do an engineering strategy](https://learnings.aleixmorgadas.dev/p/when-and-when-not-to-do-an-engineering) - Using Cynefin Framework, it shares in which domains designing an engineering strategy makes more sense compared to just execute. 54 | - [Emergent Platform and Evolution in Sociotechnical Systems](https://esilva.net/articles/emergent-platforms) - How platforms emerge from business challenges and the different types of teams like enabling and platform teams collaborate with stream-aligned teams to create the space and opportunities for platforms to evolve. 55 | - [Interim Platform Teams](https://learnings.aleixmorgadas.dev/p/interim-platform-team) - When a stream-aligned team starts supporting internal customers and acting as an interim platform team. How to deliver a great internal experience while delivering features for external clients. 56 | - [Creating an integrated business and technology strategy](https://martinfowler.com/articles/creating-integrated-tech-strategy.html) - Eleven prevalent strategic directions that organisations traverse with examples. 57 | - [Solving the Engineering Strategy crisis](https://lethain.com/solving-the-engineering-strategy-crisis/) - A unified theory of Engineering strategy, with a particular emphasis on how you can drive strategy. 58 | - [Engineering Strategy is a Fractal](https://learnings.aleixmorgadas.dev/p/engineering-strategy-is-a-fractal) - How to apply organization engineering strategy to the local context while keeping aligned with organization goals. 59 | - [Engineering strategy notes](https://lethain.com/strategy-notes/) - A collection of links on the topic gathered. 60 | - [Engineering strategy is more similar to poker than to chess](https://learnings.aleixmorgadas.dev/p/engineering-strategy-is-more-similar) - A comparison of chess and poker games and how they relate to engineering strategy. 61 | - [The outcome of the strategy becomes culture](https://learnings.aleixmorgadas.dev/p/the-outcome-of-the-strategy-becomes) - Culture guides and constrains your strategy. Using strategy to influence your culture. 62 | - [What's your engineering strategy?](https://www.linkedin.com/pulse/whats-your-engineering-strategy-pt-1-pat-cullen-cwjqe/) - Multi-part strategy guide with specific templates you can deploy rapidly in your organization. 63 | - [Combining Engineering Strategy with the North Star Framework ⭐](https://learnings.aleixmorgadas.dev/p/combining-engineering-strategy-with) - How to combine an engineering strategy with the north star framework to be guided by actionable metrics. 64 | - [Engineering strategy beyond good and best practices](https://learnings.aleixmorgadas.dev/p/engineering-strategy-beyond-good) - How only investing on good and best engineering practices won't position your company ahead of the competition that makes context specific decisions. 65 | - [You need to understand the business to design a good engineering strategy](https://learnings.aleixmorgadas.dev/p/you-need-to-understand-the-business) - A set of relevant aspects of the business that help people to have a broader understanding to improve their engineering strategy with a set of questions to ask to the domain experts. 66 | - [Basal Cost of software](https://www.eferro.net/2021/02/basal-cost-of-software.html) - How the basal cost, composed of direct impact on team capacity of the added complexity and the cost of the development or evolution of other features, affects the existing systems and teams to deliver value. 67 | - [Dealing with teams with competing priorities and needs](https://learnings.aleixmorgadas.dev/p/dealing-with-teams-with-competing) - An engineering strategy example of how to deal with teams with competing priorities. 68 | 69 | ## Videos 70 | 71 | - [Experimentation and Evolution with Wardley Maps](https://www.youtube.com/watch?v=gAh7rK2F9pk) - How Cat has used Wardley Maps to inform her always evolving strategy for the modernization of Ticketmaster’s core ticketing platform not only in terms of technical capabilities and architecture but also process maturity, organizational design, and more. 72 | - [Crossing the River by Feeling the Stones](https://www.youtube.com/watch?v=oZZKjxeg5W0) - Simon Wardley examines the issue of situational awareness and explains how it applies to technology. 73 | - [Complex Adaptive Systems](https://www.youtube.com/watch?v=l4-vpegxYPg) - How to understand and categorize domains into ordered, complicated, complex, and chaotic, and how to navigate them. 74 | - [Systems are communication structures](https://www.youtube.com/watch?v=U_0B-aY_L0c) - Understand how communication within an organization creates patterns that repeat themselves and scale up to the organization. 75 | - [Whole Work: Sociotechnicity & DevOps](https://www.youtube.com/watch?v=WtfncGAeXWU) - How to understand the present to design a better present that will create better futures from a system thinking perspective. 76 | 77 | ## Methods 78 | 79 | - [User Needs Mapping](https://userneedsmapping.com/) - An approach combining the essentials of Wardley Mapping with Team Topologies with a strong focus on user needs. 80 | 81 | ## Courses and Workshops 82 | 83 | - [Pragmatic Wardley Mapping](https://learn.hiredthought.com/p/wardley-mapping) - An online course to introduce people into Wardley Mapping. 84 | - [Implementing Domain-Driven Design](https://kalele.io/training/iddd/) - Hands-on exercises show you how to use DDD strategic and tactical design in your implementations. 85 | - [Fast Flow of Change](https://kalele.io/fast-flow-of-change/) - Combining Wardley Mapping, DDD & Team Topologies, this workshop will help you to design for adaptability. 86 | - [Engineering Strategy Workshop](https://aleixmorgadas.dev/workshops/engineering-strategy) - Introduction to engineering strategy theory and components. 87 | - [Strategy for Technical Leaders Masterclass](https://ruthmalan.com/Bredemeyer/Strategy_Masterclass_Overview.htm) - This masterclass builds on our work with software, system and enterprise architects and product, program and executive managers including CTOs and CIOs. 88 | 89 | ## Templates 90 | 91 | - [Engineering Strategy Notion Template](https://aleixmorgadas.notion.site/Engineering-Strategy-Template-910ad428d3d14c5a9aef4a4c32c4a8ba) - A template with the core elements of an engineering strategy, the high-stake problem, the understanding phase, the direction, and coherent actions. 92 | 93 | ## Supporting material 94 | 95 | - [Context mapping](https://github.com/ddd-crew/context-mapping) - Visualize the contract between bounded contexts and teams with a collection of patterns. 96 | - [Core domain charts](https://github.com/ddd-crew/core-domain-charts) - Help you to visualise the strategic importance of each (sub)domain or business capability in your architecture allowing you to make business model-aligned architectural decisions. 97 | 98 | ## Open Engineering Strategies 99 | 100 | > Open Engineering Strategies section aims to provide a relevant set of public available Engineering Strategies so we can learn from each other. 101 | 102 | - [Community Startup](https://learnings.aleixmorgadas.dev/p/community-startup-engineering-strategy?s=w) - Prove product market fit with an MVP. 103 | - [GitLab Strategy](https://about.gitlab.com/company/strategy/) - Complete GitLab three-year strategy. Containing direction, customer focus, and team dynamics. 104 | - [Flutter in 2022 Strategy](https://flutter.dev/go/strategy-2022) - Flutter annual strategy document for 2022. 105 | - [Gitpod Strategy](https://gitpod.notion.site/Gitpod-s-Direction-be35d064c0704fbda61c542b84e07ef6) - Gitpod purpose, vision, and strategy. 106 | - [Qatium Product Market Fit](https://learnings.aleixmorgadas.dev/p/post-product-market-fit-open-engineering) - An engineering strategy when the product verifies product market fit and the engineering isn't evolving the practices to match the new product needs. 107 | 108 | ## Communities 109 | 110 | - [Engineering Strategy on Discord](https://discord.gg/mebRYrNamF) - Discord community focused on Engineering Strategy. 111 | 112 | ## Podcasts 113 | 114 | - [Engineering Strategy Podcast](https://open.spotify.com/show/2o8lWLvV9O0P2Gf9J6xzLo?si=049c9a2c90924aa7) - Engineering strategy interviews to tech leaders in English and Spanish by Aleix Morgadas. 115 | - [Tech Lead Journal](https://techleadjournal.dev/) - A podcast by Henry Suryawirawan where experienced technical leaders share the often undefined, beyond-the-code skills that shaped their journeys. 116 | -------------------------------------------------------------------------------- /code-of-conduct.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to making participation in our project and 7 | our community a harassment-free experience for everyone, regardless of age, body 8 | size, disability, ethnicity, gender identity and expression, level of experience, 9 | nationality, personal appearance, race, religion, or sexual identity and 10 | orientation. 11 | 12 | ## Our Standards 13 | 14 | Examples of behavior that contributes to creating a positive environment 15 | include: 16 | 17 | * Using welcoming and inclusive language 18 | * Being respectful of differing viewpoints and experiences 19 | * Gracefully accepting constructive criticism 20 | * Focusing on what is best for the community 21 | * Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | * The use of sexualized language or imagery and unwelcome sexual attention or 26 | advances 27 | * Trolling, insulting/derogatory comments, and personal or political attacks 28 | * Public or private harassment 29 | * Publishing others' private information, such as a physical or electronic 30 | address, without explicit permission 31 | * Other conduct which could reasonably be considered inappropriate in a 32 | professional setting 33 | 34 | ## Our Responsibilities 35 | 36 | Project maintainers are responsible for clarifying the standards of acceptable 37 | behavior and are expected to take appropriate and fair corrective action in 38 | response to any instances of unacceptable behavior. 39 | 40 | Project maintainers have the right and responsibility to remove, edit, or 41 | reject comments, commits, code, wiki edits, issues, and other contributions 42 | that are not aligned to this Code of Conduct, or to ban temporarily or 43 | permanently any contributor for other behaviors that they deem inappropriate, 44 | threatening, offensive, or harmful. 45 | 46 | ## Scope 47 | 48 | This Code of Conduct applies both within project spaces and in public spaces 49 | when an individual is representing the project or its community. Examples of 50 | representing a project or community include using an official project e-mail 51 | address, posting via an official social media account, or acting as an appointed 52 | representative at an online or offline event. Representation of a project may be 53 | further defined and clarified by project maintainers. 54 | 55 | ## Enforcement 56 | 57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 58 | reported by contacting the project team at hello@aleixmorgadas.dev. All 59 | complaints will be reviewed and investigated and will result in a response that 60 | is deemed necessary and appropriate to the circumstances. The project team is 61 | obligated to maintain confidentiality with regard to the reporter of an incident. 62 | Further details of specific enforcement policies may be posted separately. 63 | 64 | Project maintainers who do not follow or enforce the Code of Conduct in good 65 | faith may face temporary or permanent repercussions as determined by other 66 | members of the project's leadership. 67 | 68 | ## Attribution 69 | 70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, 71 | available at [https://contributor-covenant.org/version/1/4][version] 72 | 73 | [homepage]: https://contributor-covenant.org 74 | [version]: https://contributor-covenant.org/version/1/4/ 75 | -------------------------------------------------------------------------------- /contributing.md: -------------------------------------------------------------------------------- 1 | # Contribution Guidelines 2 | 3 | Please note that this project is released with a [Contributor Code of Conduct](code-of-conduct.md). By participating in this project you agree to abide by its terms. 4 | 5 | ## Adding something to an awesome list 6 | 7 | If you have something awesome to contribute to an awesome list, this is how you do it. 8 | 9 | 1. Go to the [awesome-engineering-strategy's GitHub page](https://github.com/aleixmorgadas/awesome-engineering-strategy). 10 | 2. Click on the `readme.md` file: ![Step 2 Click on Readme.md](./.github/media/click-readme.md.png) 11 | 3. Now click on the edit icon. ![Step 3 - Click on Edit](./.github/media/click-edit-pencil-icon.png) 12 | 4. You can start editing the text of the file in the in-browser editor. Make sure you follow guidelines above. You can use [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/). 13 | 5. Say why you're proposing the changes, and then click on "Propose file change". ![Step 5 - Propose Changes](./.github/media/propose-changes.png) 14 | 6. Submit the [pull request](https://help.github.com/articles/using-pull-requests/)! 15 | 16 | ## Updating your Pull Request 17 | 18 | Sometimes, a maintainer of an awesome list will ask you to edit your Pull Request before it is included. This is normally due to spelling errors or because your PR didn't match the awesome-* list guidelines. 19 | 20 | [Here](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) is a write up on how to change a Pull Request, and the different ways you can do that. 21 | --------------------------------------------------------------------------------