The article examines the hidden challenges of horizontal architecture roles, explains why their contributions are hard to measure, and proposes an organization‑level BTO value framework to help architects demonstrate impact and guide career growth.
This article dissects Huawei's Integrated Product Development (IPD) methodology, detailing its six‑stage closed‑loop workflow, cross‑functional collaboration, risk‑gate mechanisms, and a four‑step strategy for handling strong stakeholders, while illustrating the approach with a 2023 MTO case study and industry‑wide adoption reasons.
The article explores how early‑mature teams often struggle later when environments change, offering practical strategies—digital traceability, balanced task delegation, and principled reporting—to navigate cross‑department work, especially in weak‑matrix organizations.
The article reflects on the pitfalls of applying a single, static strategy to cross‑department initiatives, shares a three‑step pilot‑to‑scale model for early stages, and proposes three adaptive tactics—targeted focus, breakthrough tackling, and gap‑filling—for mature phases, emphasizing flexible, goal‑layered management.
This article outlines a practical, end‑to‑end quality assurance framework for large, cross‑department projects, detailing actionable steps and best practices for each phase—from requirement analysis and design through integration, testing, deployment, and post‑release monitoring—to help QA leads proactively identify and mitigate risks.
The article explains how feature teams—cross‑functional, long‑lived groups that own end‑to‑end customer features—can improve user experience, technical excellence, and operational efficiency, while outlining the cultural and organizational changes required for successful adoption.
Traditional enterprises face low R&D efficiency due to heavy, multi‑layered project management and over 70% cross‑project, cross‑department, and supplier involvement; this discussion identifies root causes, diagnostic methods, and practical short‑ and long‑term strategies to improve coordination, visibility, and organizational structure.
The article explains the two‑pizza team principle, arguing that keeping development teams small enough to be fed by two pizzas reduces communication overhead, encourages self‑organization and cross‑functional collaboration, and ultimately leads to more sustainable and faster project delivery than expanding large, unwieldy groups.
This article shares practical strategies and visual models to help designers improve cross‑functional communication, reduce information loss, and boost design efficiency by aligning stakeholder interests, handling disagreements, and building personal credibility within product teams.
This article outlines how QA engineers can maximize their impact throughout the pre‑testing, testing, and post‑testing phases of cross‑department projects by understanding system interactions, coordinating with stakeholders, designing comprehensive test cases, monitoring progress, and conducting thorough retrospectives to continuously improve delivery quality.
Based on the 2015 DevOps State Report, this article translates and analyzes the key qualities of high‑performing DevOps teams, highlighting metrics such as deployment frequency, speed, failure recovery, gender gaps, cross‑functional responsibilities, non‑blame culture, experimental mindset, useful metrics, and full commitment.
