1 views collected around this technical thread.
This article outlines a three‑step framework—building consensus, setting shared goals, and establishing a clear communication channel—to close the collaboration gap between product‑development and business teams in a SaaS company, backed by real‑world results and practical PMO tactics.
The article examines why many agile transformations fall short due to non‑agile business practices, explains the overlapping responsibilities of PO and BA, highlights two common pitfalls for new product owners, and outlines a comprehensive, market‑driven approach to product planning and lifecycle management.
The article examines the challenges of moving large, multi‑team software organizations from waterfall to lean‑agile practices, offering concrete tactics for product planning, cross‑team coordination, integration, testing, and release, and concludes with a note on an upcoming DevOps hackathon.
This article explains the concept of an impact map—covering the four key questions why, who, how, and what—to bridge the gap between business goals and development implementation, using examples from agile practice and historical industry failures, and highlights its strategic planning benefits while noting promotional details for related training.
Through agile coaching, this case study details how the demand analysis workflow for Youku’s mobile app was redesigned, standardized in Alibaba’s RDC platform, and evaluated, resulting in clearer product planning, decentralized reviews, data‑driven management, and measurable improvements in efficiency, quality, and cross‑team collaboration.
This article introduces Impact Mapping as a powerful visual technique for turning abstract business goals into concrete software features, illustrates its use with a detailed analysis of the movie "The Secret Life of Walter Mitty," and explains how the method integrates with user‑story mapping in product development.
This article explains how to use user stories as a collaborative tool for agile product planning, detailing the key challenges, the roles involved, the three-step storytelling process (finding clues, drawing the main line, and specification), and how to run effective requirement workshops.
This article explains how to organize a user story map in eight practical steps, detailing the benefits of visualizing the backlog, prioritizing features, fostering collaborative brainstorming, and planning incremental releases to ensure early validation of architecture and scope.