0 views collected around this technical thread.
This article shares a step‑by‑step guide on planning, documenting, templating, configuring, and rule‑setting for the Cursor AI coding assistant, showing how thorough preparation transforms it from a source of buggy code into a reliable development partner.
This article explains a practical relative estimation technique for agile user stories, describing how teams can sort story cards on a wall, assign Fibonacci-like size columns, handle common pitfalls, and apply the method in real projects while emphasizing proper story granularity and team discussion.
This article examines how managerial habits such as unnecessary meetings, early‑stage over‑staffing, and fragmented work schedules waste valuable human capital, and it argues that respecting employees' time is essential for efficient project and team management.
The article outlines how ChatGPT 4.0 can significantly improve product managers' workflow across research, planning, design, project execution, and iteration by providing prompt engineering techniques, practical examples, and actionable recommendations while emphasizing security and information‑risk considerations.
This guide explains how to plan a Power Apps application by identifying the business problem (use case), understanding current processes, estimating the cost of manual work, and creating a project plan that aligns with user goals and organizational value.
This article explains why accurate software development time estimation is essential, outlines the benefits for clients and teams, describes common challenges, and provides step‑by‑step methods—including discovery, architecture, development, testing, buffer time, and techniques like planning poker—to produce reliable project timelines.
Software estimation is essential for making informed decisions on resource allocation, cost, and scheduling; this article explains why estimation matters, outlines effective estimation processes, highlights key factors such as granularity, shared assumptions, and collaboration, and provides practical questions to guide accurate and useful estimates.
The article explains how a quality management plan serves as a formal blueprint to identify user needs, define standards, assign responsibilities, select tools, and continuously control processes, ultimately ensuring customer satisfaction and business success.
The article debunks the myth that agile eliminates planning by showing that even in complex, time‑boxed Scrum projects a flexible, continuously‑refined plan covering scope, cost, schedule, and quality is essential for managing risk and delivering business value.
This article clarifies common agile planning myths, explains the two‑level project planning approach used in Huawei’s DevCloud—including roadmap and iteration planning—covers demand gathering, backlog management, sprint execution, and the importance of continuous feedback and adaptation in product management.
The article discusses the challenges of allocating delivery team resources based on project budgets, the need for a monthly stakeholder "parliament" to prioritize demands, and the difficulty of creating a manageable, value‑driven backlog that balances large projects, regulatory work, and small initiatives.
The article analyzes market data and surveys to show that developing a mobile app typically takes 3‑5 months, outlining four key development phases—research, feature definition, technical implementation, and testing—while offering practical insights for founders and developers.
The article walks through building an initial software project plan by translating effort estimates into a timeline, discussing ideal versus realistic weekly capacity, handling urgent issues, allocating testing time, identifying risks and assumptions, and adding buffer to produce a roughly nine‑week schedule.
This article explains how a team transitions from waterfall to an Agile 101 approach by introducing time‑boxed iterations, applying the INVEST principle for user‑story splitting, using a ranking method for relative estimation, and outlining a practical planning process to improve project predictability.