mirror of
https://github.com/nubenetes/awesome-kubernetes.git
synced 2026-07-13 18:30:44 +00:00
332 lines
57 KiB
Markdown
332 lines
57 KiB
Markdown
---
|
||
description: "Curated, AI-ranked Project Management Methodology resources for the 2026 Cloud Native architect: top-tier tools, guides and references (Platform & Site Reliability)."
|
||
---
|
||
# Project Management
|
||
|
||
!!! tip "Nubenetes V2 Elite Portal"
|
||
You are browsing the AI-Curated V2 Elite Edition. Looking for the exhaustive list of references? Check out the [**V1 Historical Archive**](/v1/project-management-methodology/).
|
||
|
||
!!! info "Architectural Context"
|
||
Detailed reference for Project Management in the context of Platform & Site Reliability.
|
||
|
||
## Architectural Foundations
|
||
|
||
### Kubernetes Tools
|
||
|
||
#### General Reference
|
||
|
||
- [dzone: Project Management Methodology: A Beginner's Guide](https://dzone.com/articles/best-emerging-project-management-methodologies-in) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering dzone: Project Management Methodology: A Beginner's Guide in the Kubernetes Tools ecosystem.
|
||
- [dzone: A Complete Guide to the Project Management Lifecycle](https://dzone.com/articles/a-complete-guide-to-project-management-life-cycle) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering dzone: A Complete Guide to the Project Management Lifecycle in the Kubernetes Tools ecosystem.
|
||
- [dzone: Top 40 Project Management Terms and Concepts of 2019](https://dzone.com/articles/top-40-project-management-terms-and-concepts-of-20) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering dzone: Top 40 Project Management Terms and Concepts of 2019 in the Kubernetes Tools ecosystem.
|
||
- [dzone.com: Productivity: Noise Is the Problem 🌟🌟](https://dzone.com/articles/effectiveness-noise-is-the-problem) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering ==dzone.com: Productivity: Noise Is the Problem== 🌟🌟 in the Kubernetes Tools ecosystem.
|
||
- **(None)** [](https://elpais.com/smoda/trabajo/apariencias-venderse-trabajo.html) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering elpais.com in the Kubernetes Tools ecosystem.
|
||
- [guru99.com: Agile Vs Scrum: Know the Difference](https://www.guru99.com/agile-vs-scrum.html) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering guru99.com: Agile Vs Scrum: Know the Difference in the Kubernetes Tools ecosystem.
|
||
## Architecture
|
||
|
||
### Prototyping
|
||
|
||
#### Serverless
|
||
|
||
- **(2022)** [dev.to: Construyendo un MVP sin base de datos](https://dev.to/sergomz/construyendo-un-mvp-sin-base-de-datos-1i4k) <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Discusses practical architectural patterns to construct functional MVPs without incorporating an actual persistent database, using flat-files, local memory, or external SaaS instead. Explains how this architectural decoupling lowers initial operational complexity and lets developers focus on testing business logic.
|
||
## Business and Careers
|
||
|
||
### Management Patterns
|
||
|
||
#### Leadership
|
||
|
||
- **(2022)** [business.vogue.es: Adiós a los jefes tóxicos: este es el nuevo tipo de liderazgo gentil que triunfa](https://www.vogue.es/lideres) <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An analysis of evolving corporate management cultures and toxic workplace mitigation. Discusses the value of empathetic leadership and structured soft skills in reducing developer attrition within modern tech teams.
|
||
#### Team Performance
|
||
|
||
- **(2023)** [creately.com: A Step By Step Guide to Set KPIs for Team Members](https://creately.com/guides/how-to-set-kpis-for-team-members) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — A step-by-step guide to setting actionable KPIs for engineering teams. Explores balancing quantitative delivery metrics with qualitative team-growth targets to align development outputs with business objectives.
|
||
## Engineering Leadership
|
||
|
||
### Agile Methodologies
|
||
|
||
#### Continuous Improvement
|
||
|
||
- **(2020)** [==martinfowler.com: Retrospectives Antipatterns 🌟==](https://martinfowler.com/articles/retrospective-antipatterns.html) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — An authoritative breakdown of typical anti-patterns observed during agile retrospective sessions, such as the 'Blame Game' or 'Loudest Voice.' Explains how to reconstruct retrospectives into productive, post-mortem style continuous feedback loops that actively resolve systemic design flaws, optimize integration paths, and elevate overall team software delivery quality.
|
||
#### Scrum Framework
|
||
|
||
- **(2020)** [**scrum.org: Scrum no es una metodología, es un marco de trabajo**](https://www.scrum.org/resources/blog/scrum-no-es-una-metodologia-es-un-marco-de-trabajo) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Clarifies the fundamental nature of Scrum, arguing that it is not a rigid software development methodology but rather a lightweight empirical framework designed to manage complex product lifecycles. Discusses the core values of transparency, inspection, and adaptation to align cross-functional engineering processes and deliver software iteratively.
|
||
### Asynchronous Collaboration
|
||
|
||
#### Communication Strategy
|
||
|
||
- **(2020)** [hbr.org: What It Takes to Give a Great Presentation](https://hbr.org/2020/01/what-it-takes-to-give-a-great-presentation) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explains communication structures for presenting complex ideas to diverse stakeholders. Analyzes how technical architects can translate highly advanced system engineering concepts, deployment topologies, and microservice architectures into clear, business-driven narratives that secure stakeholder alignment and funding.
|
||
#### Team Dynamics
|
||
|
||
- **(2019)** [hbr.org: How to Debate Ideas Productively at Work](https://hbr.org/2019/01/how-to-debate-ideas-productively-at-work) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Offers a structural methodology for conducting objective, high-stakes intellectual debates within technical environments. Focuses on separating personal identity from architectural assertions, grounding discussions in objective system data, and using RFC-style collaborative documents to establish healthy constructive criticism mechanisms in highly technical teams.
|
||
### Career Development
|
||
|
||
#### Developer Productivity
|
||
|
||
- **(2023)** [==mariocortes.net: La crisis de seniority==](https://www.mariocortes.net/la-crisis-de-seniority) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — An analytical essay investigating the modern 'seniority crisis' within software engineering, characterized by developers securing Senior titles prematurely during hyper-growth hiring cycles. Outlines the technical, architectural, and systemic gaps that result when teams lack developers with deep lifecycle experience, proposing structured engineering mentoring and rigorous promotion criteria.
|
||
#### Management Transition
|
||
|
||
- **(2021)** [**devops.com: How Good Developers Become Good Engineering Managers**](https://devops.com/how-good-developers-become-good-engineering-managers) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Explores the complex transition from individual software contributor to engineering manager. Outlines how to pivot from tactical coding efforts to strategic engineering leadership, detailing how to manage high-level software system design, support team career growth, and avoid micro-management traps that block development productivity.
|
||
#### Organizational Scaling
|
||
|
||
- **(2022)** [==newsletter.pragmaticengineer.com: Engineering Leadership Skill Set Overlaps==](https://newsletter.pragmaticengineer.com/p/engineering-leadership-skillset-overlaps) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — Synthesizes the overlapping skill sets required among senior technical roles, such as Engineering Managers, Tech Leads, and Product Managers. Clearly demarcates boundaries of accountability regarding system execution, architecture, and strategy, offering a model to coordinate these highly interdependent engineering pillars.
|
||
#### Team Dynamics (1)
|
||
|
||
- **(2015)** [hbr.org: How to Give Tough Feedback That Helps People Grow](https://hbr.org/2015/08/how-to-give-tough-feedback-that-helps-people-grow) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Synthesizes core management communication techniques to deliver critical feedback that encourages technical growth and continuous improvement. Focuses on actionable, objective examples rather than subjective assessments, helping technical leads build a resilient, high-feedback engineering culture.
|
||
#### Technical Mentorship
|
||
|
||
- **(2019)** [==noidea.dog/glue: Being Glue==](https://www.noidea.dog/glue) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — An industry-standard analysis of 'glue work'—the essential non-coding technical tasks like mentoring, architecture alignment, communication, and process optimization that hold engineering teams together. Examines the systemic risks where technical contributors perform high-impact glue activities at the expense of their promotion metrics, calling for formal valuation of organizational architecture and technical leadership roles.
|
||
### Consulting and Advisory
|
||
|
||
#### Enterprise Strategy
|
||
|
||
- **(2022)** [rockcontent.com: Conoce los principales tipos de consultoría en las que tu negocio puede invertir para explotar su potencial](https://analoghq.ai/blog/es/tipos-de-consultoria) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — Details the landscape of professional advisory services, classifying key consulting types like strategic, digital transformation, and technical systems consulting. Outlines how enterprise architectures can leverage external expertise to fast-track digital adoption, modern cloud-native architectures, and software organizational structural alignment.
|
||
### Crisis Management
|
||
|
||
#### Psychological Safety
|
||
|
||
- **(2022)** [hbr.org: How to Deal with High Pressure Situations at Work](https://hbr.org/2022/05/how-to-deal-with-high-pressure-situations-at-work) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Outlines psychological and operational strategies for managing high-stress scenarios, such as production outages, critical system failures, or tight product delivery deadlines. Emphasizes maintaining situational awareness, structuring emergency response communication (like Incident Commander roles), and preventing cognitive overload to facilitate rational, data-driven system remediation.
|
||
### Cultural Leadership Models
|
||
|
||
#### Team Dynamics (2)
|
||
|
||
- **(2016)** [bbc.com: Por qué en Japón los jefes NO felicitan a sus empleados cuando hacen bien su trabajo](https://www.bbc.com/mundo/vert-cap-37270163) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Analyzes the unique cultural management dynamics in Japanese corporate environments, focusing on why overt recognition of individual effort is structurally avoided in favor of collective team success and continuous organic improvement (Kaizen). Offers contrasting insights for globalized, distributed engineering teams with diverse cultural backgrounds.
|
||
### Developer Productivity (1)
|
||
|
||
#### Asynchronous Collaboration (1)
|
||
|
||
- **(2022)** [**magnet.xataka.com: Esclavos de la improductividad: el 70% de las reuniones impiden que los empleados hagan su trabajo**](https://www.xataka.com/magnet/esclavos-improductividad-70-reuniones-impiden-que-empleados-hagan-su-trabajo) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Explores empirical research showing that 70% of workplace meetings actively prevent employees from completing their actual tasks. Advocates for 'No Meeting Days' and asynchronous communication strategies to enable high-focus developer work, reduce cognitive load, and boost execution speed in modern cloud-native software development pipelines.
|
||
- **(2022)** [**genbeta.com: Las reuniones laborales por videollamada nos agotan: esto es lo que pasa si se eliminan y cambian por chats**](https://www.genbeta.com/actualidad/reuniones-trabajo-nos-agotan-videollamada-se-sabe-que-pasa-se-eliminan-usamos-chats) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Analyzes the psychological and operational impact of video-conferencing fatigue in software engineering teams. Documents the benefits of replacing real-time sync calls with asynchronous chat platforms, collaborative document pipelines, and clear ticket comments, highlighting the improvement in deep focus and deployment rates.
|
||
### Metrics and Analytics
|
||
|
||
#### Brooks Law Application
|
||
|
||
- **(2021)** [**cloudbees.com: More Isn’t Always Better: Using Predictive Analytics to Show Adding More People Doesn’t Always Help**](https://www.cloudbees.com/blog/using-predictive-analytics-to-show-adding-more-people) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Details the utilization of predictive analytics in software delivery management to validate Brooks' Law empirically. Explains how engineering leaders can leverage data-driven models to optimize team sizing instead of naively scaling headcounts. Analyzes productivity bottlenecks, communication overhead, and the optimal inflection point where team expansion yields diminishing returns on deployment frequency.
|
||
#### DORA Metrics
|
||
|
||
- **(2020)** [**infoq.com: Better Metrics for Building High Performance Teams**](https://www.infoq.com/articles/better-metrics-team-performance) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Focuses on establishing effective performance indicators for software development organizations, warning against anti-patterns like counting commits or lines of code. Advocates for system-level engineering metrics, including the DORA metrics (deployment frequency, lead time for changes, MTTR, change failure rate) to cultivate continuous improvement cultures and drive systemic stability.
|
||
#### Developer Productivity (2)
|
||
|
||
- **(2022)** [**dev.to: What’s Wrong With Measuring Developer Performance (+ 10 Best Metrics)**](https://dev.to/actitime/whats-wrong-with-measuring-developer-performance-10-best-metrics-5620) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Critiques traditional individual developer performance metrics (such as lines of code, pull request count, or hours worked) as highly gamable and toxic to collaboration. Proposes ten alternative high-value holistic metrics centered on cycle times, collaboration, defect density, and deployment safety, facilitating sustainable delivery pipelines and high developer experience.
|
||
#### Organizational Scaling (1)
|
||
|
||
- **(2022)** [**blogs.elconfidencial.com: Los españoles somos más improductivos que nunca y el problema no es de los empleados**](https://www.elconfidencial.com/tecnologia/tribuna/2022-02-12/productividad-tecnologia-startups-apps_3373786) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Investigates structural productivity declines in technology and startup business environments, placing the blame not on individual developers but on chronic management flaws. Highlights issues like meeting-heavy workflows, fragmented communication platforms, technical debt, and a systemic lack of automated platform tooling that dampens developer output.
|
||
### Organizational Scaling (2)
|
||
|
||
#### Big Tech Practices
|
||
|
||
- **(2023)** [**businessinsider.com: I'm an ex-Amazon senior leader. Here's why layoffs keep happening and why ambitious managers are fueling them**](https://www.businessinsider.com/amazon-reason-for-layoffs-former-senior-tech-leader-2023-5) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — A critical insider look at how aggressive scaling incentives in hyper-growth tech companies can lead to systemic over-hiring, architectural empire-building, and subsequent massive restructuring and downsizings. Analyzes the management performance frameworks that drive these structural fluctuations, warning against localized hyper-hiring over clean organizational architecture.
|
||
- **(2023)** [**genbeta.com: Un ex-CEO, sobre el origen de tener gente que ni hace falta en las empresas: “Contratas a alguien, y lo primero que hace es contratar"**](https://www.genbeta.com/actualidad/ex-ceo-origen-tener-gente-que-hace-falta-empresas-contratas-a-alguien-primero-que-hace-contratar-1) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Investigates the organizational phenomena of manager empire-building, where expanding headcounts is falsely correlated with corporate power and strategic progress. Explains how this dynamic leads to over-engineered organizational structures and excessive communication overhead, contrasting it with lean, autonomous platform engineering practices.
|
||
#### Management Models
|
||
|
||
- **(2019)** [**hbr.org: As Your Team Gets Bigger, Your Leadership Style Has to Adapt**](https://hbr.org/2019/03/as-your-team-gets-bigger-your-leadership-style-has-to-adapt) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Analyzes the critical inflection points of organizational growth, focusing on how leadership paradigms must shift as team sizes expand. Discusses the transition from direct, tactical hands-on management to strategic, decentralized delegative leadership. Provides a conceptual blueprint for scaling engineering organizations without sacrificing operational agility or engineering cohesion.
|
||
#### Middle Management
|
||
|
||
- **(2021)** [**hbr.org: The Real Value of Middle Managers**](https://hbr.org/2021/06/the-real-value-of-middle-managers) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Defends the critical functional value of middle management in large enterprise hierarchies. Demonstrates that instead of acting as bureaucratic roadblocks, competent middle managers serve as dynamic translators between high-level executive strategy and boots-on-the-ground engineering execution, facilitating organizational alignment, psychological safety, and rapid change management.
|
||
### Product Management
|
||
|
||
#### Software Architecture Design
|
||
|
||
- **(2022)** [==estrategiadeproducto.com: La espiral de mierda==](https://www.estrategiadeproducto.com/p/evitar-caer-espiral-de-mierda) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — Synthesizes a critical systemic anti-pattern in software development where short-term delivery pressures result in technical debt compromises, creating architectural degradation and a complete collapse of engineering velocity. Highlights tactical pathways for engineering managers to defend refactoring cycles and architectural stability.
|
||
#### Team Dynamics (3)
|
||
|
||
- **(2022)** [**estrategiadeproducto.com: La segunda mayor mentira sobre Product Management**](https://www.estrategiadeproducto.com/p/segunda-mayor-mentira-product-management) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Critiques the widespread misconception of the Product Manager as the absolute 'CEO of the Product.' Explains that without direct positional authority over engineers or architects, a PM's true impact relies on data-driven influence, transparent customer insight dissemination, and cross-functional alignment.
|
||
### Project Management (1)
|
||
|
||
#### Agile Methodologies (1)
|
||
|
||
- **(2021)** [**scrum.org: Posturas del Product Owner**](https://www.scrum.org/resources/blog/posturas-del-product-owner) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Explores both constructive and destructive behaviors (or 'postures') of a Scrum Product Owner. Contrasts positive archetypes (collaborator, visionary, value maximizer) with negative ones (the scribe, the micro-manager, the bottleneck), explaining how the PO's operational style directly affects system requirements refinement and engineering team velocity.
|
||
- **(2021)** [creately.com: How to Better Manage Your Projects with Kanban Boards](https://creately.com/blog/project-management/what-is-a-kanban-board) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — Introduces visual project management methodologies using Kanban boards. Highlights essential visual metrics such as Work-in-Progress (WIP) limits, cycle times, and bottleneck identification. Explains how to map agile delivery cycles onto dynamic cards to improve flow, increase transparency, and accelerate software shipping iterations.
|
||
- **(2021)** [rebelscrum.site: Characteristics of a Great Product Owner](https://www.rebelscrum.site/post/characteristics-of-a-great-product-owner) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Examines the critical competencies required for high-performing Product Owners in modern software delivery teams. Highlights domain knowledge, structured communication, decisiveness, and the capacity to align development roadmaps with customer feedback cycles to minimize architectural rework and maximize deployment velocity.
|
||
#### Big Tech Practices (1)
|
||
|
||
- **(2021)** [==blog.pragmaticengineer.com: How Big Tech Runs Tech Projects and the Curious Absence of Scrum==](https://blog.pragmaticengineer.com/project-management-at-big-tech) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — A seminal critique of Scrum frameworks within modern hyper-scale technology companies. Contrasts classical prescriptive Scrum ceremonies with the pragmatism found in Big Tech, which prioritizes engineer-led planning, asynchronous progress tracking, and outcome-based roadmapping. Highlights how microservices-oriented teams achieve high agility through direct system ownership and continuous delivery without overhead-heavy ceremonies.
|
||
### Psychological Safety (1)
|
||
|
||
#### Communication Strategy (1)
|
||
|
||
- **(2021)** [elfinanciero.com.mx: Tu jefe no siempre tiene la razón: ¿de qué manera puedes contradecirlo?](https://www.elfinanciero.com.mx/empresas/2021/07/06/tu-jefe-no-siempre-tiene-la-razon-de-que-manera-puedes-contradecirlo) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — Discusses strategic frameworks for engineers to constructively challenge management decision-making. Emphasizes grounding alternative proposals in empirical system metrics, security considerations, or architectural risk analysis to foster bidirectional feedback and prevent high-impact development blunders.
|
||
#### Team Dynamics (4)
|
||
|
||
- **(2022)** [**elconfidencial.com: Esta psicóloga ha estudiado a los capullos de tu empresa y sabe por qué se comportan así**](https://www.elconfidencial.com/espana/2022-03-18/tessa-west-psicologa-capullos-trabajo_3392185) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Analyzes toxic behavior patterns in the workplace based on research by organizational psychologist Tessa West. Identifies archetypes like the 'kiss-up kick-downer' and 'credit stealer,' offering technical leads actionable psychological strategies to structure team communications, restrict manipulative dynamics, and protect engineering output.
|
||
- **(2022)** [elconfidencial.com: La mejor forma de decirle a tu jefe que estás hasta arriba y no puedes más con tanto trabajo](https://www.elconfidencial.com/alma-corazon-vida/2022-02-14/jefe-trabajo-empleo-quemado-no-puedes_3372444) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — Provides actionable advice on how to raise the alarm regarding work overload and impending burnout to management. Recommends presenting structured data on ongoing tasks, mapping them to clear priorities, and proposing concrete technical delegation or scope-reduction options to protect developer mental health.
|
||
- **(2019)** [hbr.org: The Surprising Power of Simply Asking Coworkers How They’re Doing](https://hbr.org/2019/02/the-surprising-power-of-simply-asking-coworkers-how-theyre-doing) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explores the foundational role of empathy and regular check-ins in fostering high-performance engineering cultures. Demonstrates how proactive personal interactions establish psychological safety, which is directly correlated with reduced system deployment risk, higher incident response efficiency, and lower developer burnout rates.
|
||
### Remote Work
|
||
|
||
#### Career Development (1)
|
||
|
||
- **(2023)** [**businessinsider.es: Avanzar en la carrera profesional y conseguir ascensos dentro de la empresa será mucho más difícil para las personas que teletrabajan, según el CEO de IBM**](https://www.businessinsider.es/desarrollo-profesional/teletrabajar-perjudica-carrera-profesional-posibles-ascensos-1240782) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Examines the controversial statements of IBM's CEO regarding remote work and career advancement. Contrasts 'proximity bias' issues within classic enterprise hierarchies against modern, asynchronous, result-oriented performance evaluation frameworks that promote talent purely based on systematic contributions.
|
||
#### Developer Productivity (3)
|
||
|
||
- **(2021)** [pymesyautonomos.com: ¿Está trabajando el empleado realmente desde su casa?](https://www.pymesyautonomos.com/management/esta-trabajando-empleado-realmente-su-casa) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — Addresses common managerial anxieties about remote work accountability. Contrasts surveillance-heavy keystroke logging techniques with output-oriented, technical project milestones (e.g., code deployment frequency, story completion rates, and system architectural goals) to sustainably measure team velocity.
|
||
### Security and Compliance
|
||
|
||
#### Corporate Governance
|
||
|
||
- **(2022)** [okdiario.com: Telefónica y Santander despiden a 467 empleados en 2021 por denuncias de compañeros](https://okdiario.com/economia/telefonica-santander-despiden-467-empleados-2021-denuncias-companeros-8655690) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Highlights corporate governance, whistleblowing protocols, and internal compliance mechanisms within large enterprises, as demonstrated by internal investigations leading to dismissals at Telefónica and Santander. Discusses the ethical standards, documentation compliance, and psychological safety guidelines required to sustain a healthy corporate and software operations environment.
|
||
### Team Dynamics (5)
|
||
|
||
#### Conflict Resolution
|
||
|
||
- **(2021)** [blog.trello.com: Consejos para manejar distintos conflictos en un equipo de trabajo](https://blog.trello.com/es/conflictos-en-el-trabajo) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — Provides an operational framework for identifying and resolving interpersonal conflicts within technical delivery teams. Highlights visual tracking systems, regular retrospectives, and structured architectural alignment reviews to defuse typical friction points, such as diverging coding standards or disputed system design decisions.
|
||
### Team Management
|
||
|
||
#### Infrastructure Operations
|
||
|
||
- **(2021)** [**redhat.com: 11 considerations for effectively managing a Linux sysadmin team 🌟**](https://www.redhat.com/en/blog/11-manager-considerations) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — A comprehensive architectural guide to managing infrastructure operations and sysadmin teams. Emphasizes modernizing Linux environments, balancing operational tasks with strategic automation, and establishing clear performance indicators. Contrasts classical hands-on sysadmin workflows with contemporary automated infrastructure-as-code paradigms to scale team efficiency.
|
||
#### Management Transition (1)
|
||
|
||
- **(2021)** [openwebinars.net: 13 Errores que cometes como Manager](https://openwebinars.net/blog/13-errores-que-cometes-como-manager) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — Outlines thirteen critical errors made by newly appointed engineering managers, such as ignoring team input, micromanaging technical solutions, and ignoring developer burnout signals. Provides tactical strategies for establishing balanced technical governance and facilitating a healthy developmental experience.
|
||
#### Team Dynamics (6)
|
||
|
||
- **(2022)** [**lavanguardia.com: La delgada línea roja del liderazgo: de la cercanía al compadreo**](https://www.lavanguardia.com/economia/20220223/8075492/liderazgo-empresa-jefes-empleados-cercania-decisiones.html) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Analyzes the boundaries of leadership behavior, illustrating the risk of transitioning from an empathetic, approachable manager to a compromised peer. Recommends strategies to balance psychological safety and team trust with professional objectivity to make fair engineering, promotional, and systemic architectural decisions.
|
||
- **(2022)** [**businessinsider.es: La brillante explicación de Steve Jobs sobre por qué los buenos empleados renuncian al trabajo**](https://www.businessinsider.es/desarrollo-profesional/explicacion-steve-jobs-buenos-empleados-renuncian-trabajo-1137601) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Explores Steve Jobs' legendary perspective on talent retention, emphasizing that high-performing engineers leave when forced to work under incompetent management or within broken architectural processes. Advocates for flat, technical-focused governance structures where system quality and customer outcomes dominate over organizational politics.
|
||
- **(2022)** [cronista.com: Cómo identificar a un mal jefe y qué errores no pueden cometer hoy los líderes](https://www.cronista.com/apertura/empresas/como-identificar-a-un-mal-jefe-y-que-errores-no-pueden-cometer-hoy-los-lideres) <span class='md-tag md-tag--warning'>[ES CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — Identifies key red flags of toxic engineering leadership, including micro-management, blame shifting, and chronic overwork structures. Outlines core modern leadership competencies like transparent team metrics, career path definition, and high psychological safety that retain top engineering talent and stabilize system operations.
|
||
## Management
|
||
|
||
### Career Development (2)
|
||
|
||
#### Professional Growth
|
||
|
||
- **(2021)** [businessinsider.es: Así es como tu educación te ha moldeado sutilmente para que nunca consigas ascender en el trabajo](https://www.businessinsider.es/desarrollo-profesional/razon-nunca-consigues-ascender-trabajo-conseguir-mejor-sueldo-970737) <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explores how traditional education systems encourage compliance over initiative, often limiting engineers from asserting their value and pursuing promotions. Discusses shifting from passive performance to proactive self-advocacy to advance technical career paths.
|
||
#### Workplace Well-being
|
||
|
||
- **(2021)** [businessinsider.es: "Estoy atrapado en unos hábitos poco saludables y me siento abrumado por todo lo que tengo que hacer, ¿cómo puedo aprender a decir no?"](https://www.businessinsider.es/desarrollo-profesional/tan-dificil-decir-no-jefe-965459) <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Spanish article offering behavioral strategies to establish professional boundaries and politely decline excessive workloads. Helps technical staff overcome burnout, prioritize core technical obligations, and build healthier relationships with management.
|
||
### Leadership (1)
|
||
|
||
#### Engineering Culture
|
||
|
||
- **(2021)** [lavanguardia.com: Los estilos de liderazgo más apreciados por los empleados](https://www.lavanguardia.com/vivo/20211113/7856878/cualidades-mas-valoran-empleados-jefe-pmv.html) <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Analyzes workplace leadership styles, mapping traits most valued by modern engineering and technical teams. Focuses on empathetic, supportive, and transformational leadership paradigms that improve retention and psychological safety in high-stress delivery environments.
|
||
#### Organizational Design
|
||
|
||
- **(2022)** [isprox.com: 16 Estilos de liderazgo: ¿cuál es más efectivo?](https://isprox.com/es/16-estilos-liderazgo-cual-es-mas-efectivo) <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Evaluates 16 distinct leadership models, contrasting authoritative and laissez-faire approaches with agile-friendly, situational, and servant leadership styles. Helps engineering directors choose a style matching their team's level of maturity.
|
||
### Workplace Culture
|
||
|
||
#### Conflict Resolution (1)
|
||
|
||
- **(2021)** [euroresidentes.com: La intimidación verbal en la empresa](https://www.euroresidentes.com/empresa/exito-empresarial/la-intimidacin-verbal-en-la-empresa) <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Tackles verbal intimidation and toxic communication habits in corporate environments. Outlines methods for building psychological safety, addressing workplace harassment, and establishing strict ethical communication rules to protect engineering talent.
|
||
## Organizational Design (1)
|
||
|
||
### Team Topologies
|
||
|
||
#### Implementation
|
||
|
||
- **(2020)** [itrevolution.com: Get Started With Team Topologies In 8 Steps](https://itrevolution.com/articles/get-started-with-team-topologies-in-8-steps) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A practical roadmap to implementing Team Topologies, focusing on identifying stream-aligned, platform, enabling, and complicated-subsystem teams. Provides concrete steps for reducing cognitive load and managing team interaction modes to improve flow and speed up product feedback loops.
|
||
#### Team Structure
|
||
|
||
- **(2020)** [itrevolution.com: The Problem With Org Charts](https://itrevolution.com/articles/the-problem-with-org-charts) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explores the friction between traditional hierarchical organizational charts and the dynamic, communication-focused patterns required for modern software delivery. Highlights how Conway's Law dictates that systems design mirrors communication structures, recommending shifting towards Team Topologies-aligned structures to streamline product delivery.
|
||
## Platform Engineering
|
||
|
||
### Innersource
|
||
|
||
#### DevOps Transition
|
||
|
||
- **(2021)** [**devops.com: Breaking Down Silos: Applying Open Source Practices in the Workplace**](https://devops.com/breaking-down-silos-applying-open-source-practices-in-the-workplace) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Explores the concepts of 'InnerSource'—using open-source development practices (like asynchronous code reviews, public pull request discussions, and clear system API documentation) inside enterprise software boundaries. Demonstrates how to break down engineering silos, improve cross-team contributions, and accelerate microservice development velocity.
|
||
### Organizational Scaling (3)
|
||
|
||
#### DevOps Transition (1)
|
||
|
||
- **(2023)** [**infoworld.com: What to do when your devops team is downsized**](https://www.infoworld.com/article/2337651/what-to-do-when-your-devops-team-is-downsized.html) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> <span class='md-tag md-tag--critical'>[LEGACY]</span> — Provides strategic architectural guidance on managing platform and DevOps infrastructure operations following organization-wide downsizings. Discusses reducing cognitive load by deprecating legacy microservices, doubling down on managed platform solutions (SaaS/IaaS), automating routine deployment pipelines, and prioritizing high-ROI continuous delivery tasks.
|
||
### Value Stream Management
|
||
|
||
#### DevOps Metrics
|
||
|
||
- **(2020)** [==infoq.com: Driving DevOps with Value Stream Management==](https://www.infoq.com/articles/DevOps-value-stream) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — A deep dive into Value Stream Management (VSM) as a framework for aligning microservice delivery pipelines with business outcomes. Details how to identify bottlenecks in the software development lifecycle (SDLC) by mapping flow metrics (lead time, cycle time, throughput). Illustrates how VSM coordinates engineering efforts to maximize systemic efficiency and avoid localized optimization traps.
|
||
## Product Management (1)
|
||
|
||
### Design Strategy
|
||
|
||
#### Micro-optimizations
|
||
|
||
- **(2021)** [joelcalifa.com: Tiny Wins](https://joelcalifa.com/blog/tiny-wins) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Details the highly effective concept of 'Tiny Wins'—prioritizing and executing small, high-impact product UX/UI micro-optimizations. Demonstrates how compound micro-improvements drastically improve overall user satisfaction and system usability with minimal architectural overhead or engineering effort.
|
||
### Methodology
|
||
|
||
#### Alternative Paradigms
|
||
|
||
- **(2021)** [blog.asmartbear.com: I hate MVPs. So do your customers. Make it SLC instead 🌟](https://blog.asmartbear.com/slc.html) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Challenges the traditional MVP (Minimum Viable Product) paradigm, advocating instead for the 'SLC' (Simple, Lovable, and Complete) framework. Argues that customers reject bare-bones MVPs, and outlines how building high-quality, fully realized smaller feature sets ensures stronger initial retention and reliable early feedback.
|
||
#### Minimum Viable Product
|
||
|
||
- **(2023)** [blog.hubspot.es: MVP: 3 pasos para desarrollar un Producto mínimo viable](https://blog.hubspot.es/sales/producto-minimo-viable) <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A 3-step Spanish guide for planning and executing an MVP. Details strategies to prioritize core features, validate assumptions through immediate customer telemetry, and iterate based on quantitative post-launch metrics.
|
||
- **(2022)** [bloo.media: Producto Mínimo Viable ¿Qué es y cómo crearlo?](https://bloo.media/blog/producto-minimo-viable-mvp) <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A technical blueprint for defining and launching an MVP, emphasizing cost-efficiency and user-centric prioritization. Outlines processes for building validation loops, avoiding scope creep, and designing feedback architectures to capture early adopter usage.
|
||
- **(2022)** [gammaux.com: Cómo definir un Minimum Viable Product (MVP)](https://www.gammaux.com/blog/como-definir-un-minimum-viable-product-mvp) <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A technical UX-oriented guide detailing how to scope and define an MVP. Illustrates methods to synthesize user research, map technical constraints to design prototypes, and ensure the initial deployment represents viable technical and user value.
|
||
- **(2020)** [gazafatonarioit.com: Entiende el MVP (Producto Mínimo Viable) y por qué prefiero Producto que se pueda probar, utilizar y adorar más temprano](https://www.gazafatonarioit.com/2020/09/entiende-el-mvp-producto-minimo-viable.html) <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explores the Minimum Viable Product (MVP) concept, advocating for a focus on early, usable, and high-quality user experiences over raw, half-finished feature sets. Proposes shifting from basic MVP models to solutions that users can test, love, and adopt early.
|
||
## Project Management (2)
|
||
|
||
### Agile Methodologies (2)
|
||
|
||
#### Agile Framework
|
||
|
||
- **(2016)** [forbes.com: Explaining Agile 🌟](https://www.forbes.com/sites/stevedenning/2016/09/08/explaining-agile) <span class='md-tag md-tag--warning'>[N/A CONTENT]</span> 🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A foundational analysis on the core principles of Agile as a paradigm of delivery. Emphasizes self-organization, customer-centric value streams, and continuous iteration as cultural priorities over rigid procedural metrics.
|
||
#### Agile Vs Waterfall
|
||
|
||
- **(2022)** [cio.com: Agile vs. waterfall: Project methodologies compared](https://www.cio.com/article/194093/agile-vs-waterfall-project-methodologies-compared.html) <span class='md-tag md-tag--warning'>[N/A CONTENT]</span> 🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An executive-level comparison between waterfall project management and iterative agile frameworks. Details the risk profiles, resource distributions, and delivery tempos associated with each model.
|
||
#### Enterprise Leadership
|
||
|
||
- **(2020)** [enterprisersproject.com: Scrum and Kanban: 3 realities CIOs should know](https://enterprisersproject.com/article/2020/10/scrum-kanban-3-realities-cios) <span class='md-tag md-tag--warning'>[N/A CONTENT]</span> 🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Strategic insights for enterprise technology leaders executing agile transitions. Examines team dynamics, organizational culture barriers, and practical hybrid methodology models within highly regulated business domains.
|
||
#### Product Management (2)
|
||
|
||
- **(2020)** [scrum.org: Make Sure You Don’t Build High Performing Teams Just to Deliver Wrong Things Faster](https://www.scrum.org/resources/blog/make-sure-you-dont-build-high-performing-teams-just-deliver-wrong-things-faster) <span class='md-tag md-tag--warning'>[N/A CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Scrum.org editorial highlighting the architectural dangers of optimizing engineering velocity without validating product value. Emphasizes establishing early customer feedback loops to prevent shipping incorrect software configurations faster.
|
||
- **(2020)** [scrum.org: Minimum Viable Product Considered Harmful 🌟](https://www.scrum.org/resources/blog/minimum-viable-product-considered-harmful) <span class='md-tag md-tag--warning'>[N/A CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A critical assessment of the traditional Minimum Viable Product (MVP) approach. Suggests that releasing poor quality MVPs can damage brand reputation, advocating instead for the delivery of highly-polished Minimum Awesome Products.
|
||
#### Scrum Framework (1)
|
||
|
||
- **(2021)** [scrum.org: What Happens To The Sprint Backlog Items That Are Not Done?](https://www.scrum.org/resources/blog/vlog-what-happens-sprint-backlog-items-are-not-done) <span class='md-tag md-tag--warning'>[N/A CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Official Scrum.org advisory detailing the correct lifecycle of uncompleted Sprint Backlog items. Establishes the architectural pattern of moving unfinished work back to the Product Backlog to preserve sprint scope integrity.
|
||
- **(2021)** [scrum.org: Scrum 2021: Getting You Started as Scrum Master or Product Owner](https://www.scrum.org/resources/blog/scrum-2021-getting-you-started-scrum-master-or-product-owner) <span class='md-tag md-tag--warning'>[N/A CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Official Scrum.org walkthrough outlining the changes and accountability updates introduced in the 2020-2021 Scrum Guide, including the addition of Product Goals and simplified commit models.
|
||
#### Scrum Vs Kanban
|
||
|
||
- **(2020)** [blog.scrumstudy.com: Scrum and Kanban, alike or different?](https://blog.scrumstudy.com/scrum-and-kanban-alike-or-different-2) <span class='md-tag md-tag--warning'>[N/A CONTENT]</span> 🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A structural analysis comparing Scrum iterations and Kanban workflows. Explores trade-offs in velocity, team responsibility, and scheduling mechanics, providing project leaders with strategic decision criteria.
|
||
#### Scrum With Kanban
|
||
|
||
- **(2021)** [**scrum.org: Kanban Guide for Scrum Teams**](https://www.scrum.org/resources/kanban-guide-scrum-teams) <span class='md-tag md-tag--warning'>[N/A CONTENT]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — The official guide detailing the integration of Kanban practices within established Scrum teams. Explains how to leverage WIP limits, cycle-time tracking, and workflow visualization to optimize team performance without sacrificing Scrum principles.
|
||
### Anti-patterns
|
||
|
||
#### Risk Mitigation
|
||
|
||
- **(2021)** [ewsolutions.com: Worst Project Management Practices](https://www.ewsolutions.com/worst-project-management-practices) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Identifies and deconstructs worst-case project management practices and structural anti-patterns in complex engineering environments. Highlights how excessive documentation, siloing, lack of transparency, and poor risk-modeling derail high-budget software and cloud projects.
|
||
### Governance
|
||
|
||
#### RACI Matrix
|
||
|
||
- **(2023)** [blog.hubspot.es: Matriz RACI: qué es y cómo utilizarla para asignar responsabilidades](https://blog.hubspot.es/marketing/matriz-raci) <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Spanish guide explaining the deployment of RACI matrices to structure large-scale digital initiatives. Demonstrates templates and practical examples to map stakeholder communication strategies, avoiding operational bottlenecking during critical release cycles.
|
||
- **(2021)** [Understanding Responsibility Assignment Matrix (RACI Matrix)](https://project-management.com/understanding-responsibility-assignment-matrix-raci-matrix) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explains the design and execution of the Responsibility Assignment Matrix (RACI), highlighting its critical role in multi-stakeholder enterprise engineering projects. Details how to clarify roles (Responsible, Accountable, Consulted, Informed) to eliminate organizational ambiguity and speed up operational decision-making.
|
||
- **(2021)** [rockcontent.com: mejor las responsabilidades con la Matriz RACI](https://analoghq.ai/blog/es/matriz-raci) <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Provides a detailed breakdown of the RACI model for assigning responsibility within multidisciplinary digital product teams. Explores how defining ownership upfront helps prevent friction during agile development iterations and release activities.
|
||
- **(2021)** [jaumepujolcapllonch.com: La matriz RACI y la asignación de responsabilidades](https://www.jaumepujolcapllonch.com/la-matriz-raci-y-la-asignacion-de-responsabilidades) <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An academic and practical analysis of responsibility delegation using the RACI framework. Discusses common implementation pitfalls, such as assigning multiple 'Accountable' parties, and how to balance ownership in complex software delivery and systems administration projects.
|
||
## Software Engineering
|
||
|
||
### Agile Methodologies (3)
|
||
|
||
#### Process Comparison
|
||
|
||
- **(2022)** [lucidchart.com: Agile vs. Waterfall vs. Kanban vs. Scrum: What’s the Difference?](https://lucid.co/blog/agile-vs-waterfall-vs-kanban-vs-scrum) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Provides a visual-oriented breakdown of classic and modern software lifecycle management frameworks. Helps technical architects align operational workflows (such as sprint planning and continuous delivery cycles) with the organizational capability and architecture style of the organization.
|
||
- **(2022)** [softwaretestinghelp.com: Kanban Vs Scrum Vs Agile: A Detailed Comparison To Find Differences](https://www.softwaretestinghelp.com/kanban-vs-scrum-vs-agile) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Provides an in-depth operational comparison of Kanban, Scrum, and the broader Agile umbrella, focusing on metrics like lead time, cycle time, and velocity. Assists teams in identifying optimal task visualization mechanics to reduce blockages and operational waste in delivery pipelines.
|
||
- **(2021)** [visual-paradigm.com: Scrum vs Waterfall vs Agile vs Lean vs Kanban](https://www.visual-paradigm.com/scrum/scrum-vs-waterfall-vs-agile-vs-lean-vs-kanban) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A comprehensive comparison of major software development paradigms, breaking down the operational mechanics of Scrum, Kanban, Waterfall, Agile, and Lean. Synthesizes when to leverage iterative sprints versus continuous flow models to maximize delivery velocity and quality.
|
||
- **(2021)** [greycampus.com: What's the Difference? Agile vs Scrum vs Waterfall vs Kanban](https://www.greycampus.com) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Analyzes project management frameworks with a focus on contrasting agile methodologies against traditional waterfall planning. Delineates how Scrum and Kanban optimize resource allocation and limit work-in-progress to handle volatile development environments.
|
||
#### Scrum And Kanban
|
||
|
||
- **(2023)** [atlassian.com: Kanban vs. Scrum](https://www.atlassian.com/agile/kanban/kanban-vs-scrum) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — The industry-standard guide dissecting the tactical differences between Kanban's continuous flow and Scrum's time-boxed sprints. Focuses on roles (Scrum Master, Product Owner) versus non-prescriptive Kanban workflows, helping engineering leads choose optimal cadences.
|
||
- **(2022)** [k21academy.com: Scrum vs Kanban](https://k21academy.com/scrum/scrum-vs-kanban) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A technical overview comparing Scrum sprints and Kanban boards, aimed at cloud engineering professionals. Emphasizes how task-level agile delivery frameworks interface with cloud DevOps pipelines to drive high-frequency infrastructure deployments.
|
||
### Anti-patterns (1)
|
||
|
||
#### Engineering Culture (1)
|
||
|
||
- **(2021)** [nichesoftware.co.nz: Promotion Driven Development (PDD) 🌟](https://www.nichesoftware.co.nz/2021/05/29/promotion-driven-development.html) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Critiques the anti-pattern of Promotion Driven Development (PDD), where engineers select unnecessary, highly complex tools and over-engineer architectures to pad resumes for promotions. Warns against the resulting complexity, technical debt, and team maintenance burdens.
|
||
### Hybrid Methodologies
|
||
|
||
#### Agile-waterfall Integration
|
||
|
||
- **(2021)** [deloitte.com: Bringing Agile benefits to a waterfall project](https://www.deloitte.com/us/en/insights/industry/government-public-sector-services.html) <span class='md-tag md-tag--critical'>[LEGACY]</span> — Addresses the hybrid integration of Agile practices within strictly regulated, legacy Waterfall enterprise environments. Details techniques for implementing iterative testing, continuous integration, and phased feedback loops to de-risk waterfall releases without violating structural compliance protocols.
|
||
### Productivity
|
||
|
||
#### Platform Engineering (1)
|
||
|
||
- **(2023)** [swarmia.com/build: Build Elements of an Effective Software Organization](https://www.swarmia.com/build) <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Provides an advanced framework for measuring and optimizing software organization effectiveness. Delves into metric patterns (such as DORA, SPACE, and developer cognitive load metrics) to scale delivery, remove operational bottlenecks, and build reliable developer platforms.
|
||
## Software Supply Chain
|
||
|
||
### Security and Compliance (1)
|
||
|
||
#### Open Source Vulnerabilities
|
||
|
||
- **(2022)** [**techcrunch.com: Protestware on the rise: Why developers are sabotaging their own code**](https://techcrunch.com/2022/07/27/protestware-code-sabotage) <span class='md-tag md-tag--warning'>[EN CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Investigates the complex security phenomenon of 'protestware,' where open-source maintainers intentionally introduce destructive changes or regional exploits into widely used packages for political or social reasons. Details the architectural impact on enterprise software supply chains and highlights the urgent necessity for robust dependency pinning, software bills of materials, and strict package mirroring.
|
||
|
||
---
|
||
💡 **Explore Related:** [DevOps](./devops.md) | [Performance Testing With Jenkins And Jmeter](./performance-testing-with-jenkins-and-jmeter.md) | [QA](./qa.md)
|
||
|
||
🔗 **See Also:** [About](./about.md) | [Postman](./postman.md)
|
||
|