# Project Management Published articles for Project Management. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Join our live webinars: Migrating from Atlassian to YouTrack DevFeed: [Join our live webinars: Migrating from Atlassian to YouTrack]() Original publisher: [Read original article]() Author: Elena Pishkova Published: 2026-09-09T12:51:07Z Content type: news Language: en Sources: [The JetBrains Blog]() Topics: [migration](), [AI Bots]() Tags: [ai-agents](), [atlassian](), [best-practices](), [data-center](), [demo](), [deployment](), [documentation](), [events](), [helpdesk](), [knowledge-base](), [livestreams](), [mcp](), [migration](), [project-management](), [tutorials](), [webinar](), [workflows](), [youtrack](), [youtrack-server]() ### AI overview JetBrains announces live webinars about migrating from Atlassian products to YouTrack. Sessions cover moving projects, users, and data from Jira, Confluence, and Jira Service Management, with migration demos, deployment and pricing information, customer stories, and regional sessions. ### Source excerpt Atlassian is discontinuing sales and support for Data Center products. If you're exploring alternatives, join us for a live session on September 30 to see how Jira-to-YouTrack migration works, including a demo and real customer stories. Register for the worldwide English-language webinar, hosted by the YouTrack team, or attend a regional session in Japanese hosted [...] ## What Is an Agile Coach? Key Responsibilities and Business Impact DevFeed: [What Is an Agile Coach? Key Responsibilities and Business Impact]() Original publisher: [Read original article]() Author: ANTONIA MCCULLOUGH, AGILE COACH @ TOPTAL Published: 2026-08-31T04:00:00Z Content type: article Language: en Sources: [Toptal Blog]() Topics: [Agile](), [Self-organizing Team](), [software-development]() Tags: [agile](), [business](), [collaboration](), [development](), [guide](), [leadership](), [management](), [project-management](), [scrum](), [software-development]() ### AI overview A guide to the Agile coach role, covering its responsibilities, organizational impact, differences from Scrum masters, consultants, and project managers, and the skills needed to support Agile practices across teams and departments. ### Source excerpt Navigate the evolving world of Agile coaching with this comprehensive guide. From responsibilities and skills to business impact, explore what the role looks like today and what it takes to succeed. ## AI Won't Replace Project Managers, But It is Reshaping How Work Gets Done DevFeed: [AI Won't Replace Project Managers, But It is Reshaping How Work Gets Done]() Original publisher: [Read original article]() Author: Emim Vigin Lumina Published: 2026-08-20T19:05:40Z Content type: article Language: en Sources: [Stack Overflow Blog]() Topics: [Artificial Intelligence](), [telemetry](), [Large Language Model](), [CI/CD](), [Machine learning]() Tags: [agentic](), [ai](), [cc-by-sa](), [ci-cd](), [contributed](), [project-management](), [telemetry]() ### AI overview AI is reshaping technical project management by automating coordination tasks and using telemetry, delivery data, and machine learning to provide predictive project insights. The article argues that project managers are shifting from administrative oversight toward strategic systems-oriented work. ### Source excerpt Founded in 2008, Stack Overflow's public platform is used by nearly everyone who codes to learn, share their knowledge, collaborate, and build their careers. ## Canon 3X: Explore/Expand/Extract DevFeed: [Canon 3X: Explore/Expand/Extract]() Original publisher: [Read original article]() Author: Kent Beck Published: 2026-07-30T13:04:07Z Content type: opinion Language: en Sources: [Software Design: Tidy First?]() Topics: [implementation](), [risk-management](), [Finance](), [Business Security]() Tags: [implementation](), [management](), [project-management](), [risk-management]() ### AI overview Kent Beck explains the 3X framework of Explore, Expand, and Extract, arguing that each phase of a product or company's growth requires different approaches to finance, teams, project management, technology, risk management, implementation, marketing, and sales. ### Source excerpt I've started a series of Canon articles where I explain my ideas as plainly & unambiguously as possible--no analogies, no persuasion, just the facts. ## Why Project Management Is a Critical Skill for Experienced Engineers DevFeed: [Why Project Management Is a Critical Skill for Experienced Engineers]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-07-11T00:00:00Z Content type: opinion Language: en Sources: [Swizec Teller]() Topics: [Development](), [Software](), [Users]() Tags: [development](), [project-management](), [software](), [users]() ### AI overview The article argues that experienced engineers often struggle when given ownership of a project defined by goals rather than preassigned tasks. It presents breaking complex problems into actionable work, clarifying the definition of done, and understanding user impact as critical engineering skills. ### Source excerpt In the last few months every engineer I hired stumbled in exactly the same way: Project management. They learned quickly, but that first big project has become a rite of passage. ## Using AI to Reduce the Burden of Status Reporting DevFeed: [Using AI to Reduce the Burden of Status Reporting]() Original publisher: [Read original article]() Author: Daniel Doubrovkine (dblock@dblock.org) Published: 2025-08-29T09:00:00Z Content type: opinion Language: en Sources: [Daniel Doubrovkine]() Topics: [Artificial Intelligence](), [Development](), [Software]() Tags: [ai](), [management](), [people](), [project-management](), [reporting](), [software-development]() ### AI overview The article argues that hierarchical software organizations can create excessive status-reporting work and meetings. It proposes using AI to automate most of that reporting while preserving the coordination benefits of organizational hierarchy. ### Source excerpt One of the negative side effects of having any top-down command structure is that every additional layer risks introducing a new level of bureaucracy, which then actively subtracts value. Consider the Politburo of the USSR with dozens of offices of skilled bureaucrats. Because most produced no actual value, the best apparatchiks spent their entire time managing up to remain in control. Individuals who tried to upend the system either became exhausted and gave up, or were deported to Siberia. The Soviet example also applies to software development. Consider a typical CEO -> CTO -> VP of Engineering -> Director -> Manager -> Technical Lead -> IC command structure. Each project team consists of a technical lead and a handful of individual contributors. The people committed to the project do not need status reports to know what's going on, they are actively working on it. The stakeholders and the hierarchy, however, naturally want progress and status reports. This gets aggregated at Director level, then at VP level, the CTO, and finally the CEO. From the point of view of every manager in this hierarchy collecting status and asking questions feels very natural. After all, it's much more efficient to get a summary of what's going on from a line manager than to read every status update or code change yourself. You have the power to call a meeting, have things explained and summarized to you. You also have the authority to make snap judgments based on this carefully crafted summary and partial information, and the responsibility to tell the team to focus on something they likely already know. This system quickly promotes those who are good at reporting the things their manager wants to hear, and encourages political behavior as people learn to navigate the system rather than focus on outcomes. It's worth acknowledging that these hierarchical structures exist for good reasons. Large organizations need coordination, resource allocation, and strategic alignment. The problem isn't hi ## Supabase Launch Week 15 Hackathon Winner Announcement DevFeed: [Supabase Launch Week 15 Hackathon Winner Announcement]() Original publisher: [Read original article]() Author: Tyler Shukert Published: 2025-08-20T07:00:00Z Content type: news Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [For the Love of Code](), [Artificial Intelligence](), [Figma plugin](), [Figma](), [OpenAI](), [User Stories](), [App]() Tags: [ai](), [announcement](), [app](), [browser](), [code](), [design](), [dev](), [developers](), [development](), [figma](), [figma-plugin](), [frontend](), [gpt](), [hackathon](), [launch](), [llm](), [openai](), [project-management](), [technical](), [user-stories]() ### AI overview Supabase announces the winners of its Launch Week 15 Hackathon, featuring projects that use Supabase with AI, browser applications, design workflows, games, learning tools, and project management. Winning entries include a Figma plugin that converts designs into user stories, an AI-powered spatial knowledge canvas, and an AI-driven project management platform. ### Source excerpt Announcing the winners of the Supabase Launch Week 15 Hackathon. ## Power struggles and long-term strategy in startups DevFeed: [Power struggles and long-term strategy in startups]() Original publisher: [Read original article]() Author: Denis Čahuk Published: 2024-12-30T14:44:46Z Content type: opinion Language: en Sources: [Crafting Tech Teams]() Topics: [Tech Debt](), [Software Engineering](), [Agile](), [Self-organizing Team]() Tags: [agile](), [case-studies](), [collaboration](), [communication](), [complexity](), [cto](), [engineering](), [leadership](), [management](), [pitfalls](), [project-management](), [recommendations](), [roadmaps](), [safety](), [software-development](), [startups](), [team-dynamics](), [tech-debt]() ### AI overview This podcast discussion examines power struggles, short-term thinking, technical debt, and operational inefficiencies in startups and scale-ups. It covers team dynamics, project management, unplanned work, communication, psychological safety, and aligning engineering efforts with business goals. ### Source excerpt Mario Tomić, fractional CTO joined Adrian Stanek and Denis Čahuk for an exchange of situational studies and examples of power struggles and lack of long term strategy in startups. Highlights below 👇 ## Conduct a technical migration within less than 6 months -- Part 3 (final) DevFeed: [Conduct a technical migration within less than 6 months -- Part 3 (final)]() Original publisher: [Read original article]() Author: Fabien RAYNAUD Published: 2024-12-02T09:47:16Z Content type: tutorial Language: en Sources: [JobTeaser]() Topics: [migration](), [Next.js](), [Developer experience](), [Automation](), [maintenance]() Tags: [automation](), [developer-experience](), [maintenance](), [migration](), [next-js](), [nextjs](), [project-management](), [software-development]() ### AI overview The final part of a three-part article about conducting a technical migration at JobTeaser, based on the author's experience with a Next.js migration. It focuses on preparing the organization, organizing the project, preserving developer experience, maintaining automation and documentation, and training the team. ### Source excerpt Conduct a technical migration within less than 6 months -- Part 3 (final)based on Next.js migration, performed at JobTeaser What is this 3-parts article about: sharing my own experience with handling a technical migration 📖 some additional elements that I find relevant and could help (identified with 📖 emoji) but not personally tested What this presentation is NOT about: technical step-by-step Next.js migration the perfect and only way to do a migration I tried to be as exhaustive as possible, but I didn't even complete all the points personally. So the presentation is a mix of my personal experience and all the things that could help to do it "qualitatively". Pick what is necessary for you and your ecosystem. 3 main parts: Buying time and sponsorship to be able to perform such a migration = creating a good environment to navigate easily to success Organize your project = keep an eye on and communicate about what was done and what needs to be done ▶ Preserve the developer experience = ensure use, sustainability, and future maintenance of the migration You are now ready to focus on the implementation but do not hesitate to make a step aside and check if the learning curve is not too big for newcomers on the migrated part. Preserve the Developer's Experience Finally, it is important to preserve the Developer's Experience throughout the migration process. This means minimizing disruption to the development environment and ensuring that developers can continue to work efficiently. It also means preparing the next step of the project (outside migration) and making it efficient as soon as possible. Analyze and preserve the current development environment of the team Check the used tools and the compatibility after the migration, and communicate if you need to remove one Keep automation as much as possible, nobody wants to get back to manual stuff after a migration Take time to document (update) what you are keeping, newcomers would thank you for that Train the team to be ## Conduct a technical migration within less than 6 months -- Part 2 DevFeed: [Conduct a technical migration within less than 6 months -- Part 2]() Original publisher: [Read original article]() Author: Fabien RAYNAUD Published: 2024-12-02T09:46:56Z Content type: tutorial Language: en Sources: [JobTeaser]() Topics: [migration](), [Next.js](), [Developer experience](), [maintenance]() Tags: [developer-experience](), [implementation](), [maintenance](), [migration](), [next-js](), [nextjs](), [project-management](), [software-development]() ### AI overview Part 2 of a three-part article about conducting a Next.js technical migration at JobTeaser. It focuses on organizing the migration project by defining a realistic MVP scope, prioritizing tasks, assigning work, communicating progress, and setting deadlines. ### Source excerpt Conduct a technical migration within less than 6 months -- Part 2based on Next.js migration, performed at JobTeaser What is this 3-parts article about: sharing my own experience with handling a technical migration 📖 some additional elements that I find relevant and could help (identified with 📖 emoji) but not personally tested What this presentation is NOT about: technical step-by-step Next.js migration the perfect and only way to do a migration I tried to be as exhaustive as possible, but I didn't even complete all the points personally. So the presentation is a mix of my personal experience and all the things that could help to do it "qualitatively". Pick what is necessary for you and your ecosystem. 3 main parts: Buying time and sponsorship to be able to perform such a migration = creating a good environment to navigate easily to success ▶ Organize your project = keep an eye on and communicate about what was done and what needs to be done Preserve the developer experience = ensure use, sustainability, and future maintenance of the migration Now that you have convinced the right people and made a big-picture plan, time to jump into the project, whether you are part of the implementation team or not. Organize your project The second step is to organize the project. This includes cleaning the scope of the migration regarding the most important tasks and secondary ones that could be done later. It's also about having a clean place to organize, prioritize, and communicate the project execution. Define the "real" scope of the migration = MVP with only the mandatory tasks: Be prepared for the next steps. You won't be able to perform all the tasks from the initial plan by yourself or with the initial team, only the most important ones Listing and specifying secondary tasks is important for the next steps of the project (after the migration) Continue your technical watch on the subject and adjust the migration if necessary, nobody wants an already deprecated solution. A ## Conduct a technical migration within less than 6 months -- Part 1 DevFeed: [Conduct a technical migration within less than 6 months -- Part 1]() Original publisher: [Read original article]() Author: Fabien RAYNAUD Published: 2024-12-02T09:46:26Z Content type: tutorial Language: en Sources: [JobTeaser]() Topics: [migration](), [Next.js](), [Developer experience](), [Front end]() Tags: [developer-experience](), [frontend](), [migration](), [next-js](), [nextjs](), [project-management](), [software-development](), [technical]() ### AI overview Part 1 of a three-part article shares a personal experience conducting a technical migration to Next.js at JobTeaser. It covers securing sponsorship and time, organizing the project, preserving developer experience, and a timeline involving an audit, production ecosystem, and first use case. ### Source excerpt Conduct a technical migration within less than 6 months -- Part 1based on Next.js migration, performed at JobTeaser What is this 3-parts article about: sharing my own experience with handling a technical migration 📖 some additional elements that I find relevant and could help (identified with 📖 emoji) but not personally tested What this presentation is NOT about: technical step-by-step Next.js migration the perfect and only way to do a migration I tried to be as exhaustive as possible, but I didn't even complete all the points personally. So the presentation is a mix of my personal experience and all the things that could help to do it "qualitatively". Pick what is necessary for you and your ecosystem. 3 main parts: ▶ Buying time and sponsorship to be able to perform such a migration = creating a good environment to navigate easily to success Organize your project = keep an eye on and communicate about what was done and what needs to be done Preserve the developer experience = ensure use, sustainability, and future maintenance of the migration Timeline of the migration 🔍 Concrete "real life" timing 2 weeks to build an audit in August, done in autonomy and presented to frontend chapter, management, and tech leadership 3 months to put a minimalist ecosystem into production, from November to January, done mainly in autonomy with the help of the Devex and Infra team, and also from hyped frontend engineers 2 months for the release of the first "real life" use case, from February to March, by a squad of 3 engineers + 2 others squads starting their own features on the new stack Buying time and sponsorship to do the migration The first step is buying time and sponsorship for the migration. This is essential to ensure that the necessary resources and funding will be available for the initiative, aka the right environment, to perform the migration properly. This part is more about digging into the pros and cons of this migration and being able to explain it so people will ack ## The Linear method: Opinionated software DevFeed: [The Linear method: Opinionated software]() Original publisher: [Read original article]() Author: Alia Fite Published: 2024-05-29T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Software](), [coinbase](), [Meta]() Tags: [coinbase](), [development](), [figma](), [frameworks](), [meta](), [product-development](), [productivity](), [project-management](), [scale](), [software](), [startups](), [workflows]() ### AI overview The article introduces Linear's opinionated software philosophy: purpose-built tools guide teams toward a strong default workflow instead of offering unlimited flexibility. It explains how this approach supports product development, productivity, and scaling, and describes the founding team's motivation to improve issue tracking and project management. ### Source excerpt The Linear team runs on strong opinions that might seem counterintuitive to outsiders. Here's how those principles show up in both the product and their processes. ## Comparing Agile vs Waterfall Methodology DevFeed: [Comparing Agile vs Waterfall Methodology]() Original publisher: [Read original article]() Author: admin Published: 2024-05-10T15:45:54Z Content type: comparison Language: en Sources: [Posts on Chris Banes]() Topics: [Agile](), [Development](), [software-development](), [Software Engineering]() Tags: [agile](), [development](), [project-management](), [software-development](), [uncategorized]() ### AI overview This article compares Agile and Waterfall software development methodologies. It explains Agile as a flexible, iterative approach using sprints, collaboration, feedback, and course correction, while noting challenges involving communication, delivery timelines, and project management. ### Source excerpt This article is written for anyone interested in software development methodologies, from project managers and developers to entrepreneurs and business owners. The process behind software development can be complex, but there are two main methodologies that developers use: Agile and Waterfall. In this article, we'll break down agile vs waterfall methodology to help you understand [...] ## 12 Career Lessons for Software Engineers DevFeed: [12 Career Lessons for Software Engineers]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2023-11-04T12:06:59Z Content type: article Language: en Sources: [Thinking in Tech]() Topics: [Software Engineering](), [Development](), [Learning](), [engineering-culture]() Tags: [career](), [coaching](), [coding](), [communication](), [leadership](), [learning](), [project-management](), [software-engineering]() ### AI overview A software engineering career article presents 12 lessons drawn from the author's 12 years of experience, emphasizing ownership, long-term planning, continuous learning, communication, and skills beyond coding. ### Source excerpt I learned in 12 years of my Software Engineering career ## My time as a Year Up intern at Slack DevFeed: [My time as a Year Up intern at Slack]() Original publisher: [Read original article]() Author: lcarmen2 Published: 2023-04-20T04:00:03Z Content type: article Language: en Sources: [Slack Design]() Topics: [Slack]() Tags: [career](), [internship](), [internships](), [project-management](), [slack](), [who-we-are]() ### AI overview A first-person account of Lucila Hernandez Del Carmen's path from a credit specialist to a Design Operations intern at Slack through the Year Up program. She describes the training, internship placement, and supportive workplace experience documented in the supplied excerpt. ### Source excerpt It may be weird to say my life changed because of an app most people use to fall down multi-hour rabbit holes to watch people dance or try out a viral recipe like NyQuil chicken, but it did. My name is Lucila Hernandez Del Carmen, I'm a Year Up alumnus-turned-Slack Design Operations intern for the [...] The post My time as a Year Up intern at Slack appeared first on Slack Design. ## Теперь YouTrack интегрируется с GitLab CI/CD DevFeed: [Теперь YouTrack интегрируется с GitLab CI/CD]() Original publisher: [Read original article]() Author: ana-bartasheva (JetBrains) Published: 2021-05-28T10:41:33Z Content type: release Language: ru Sources: [JetBrains RU]() Topics: [CI/CD](), [GitLab](), [teamcity](), [Jenkins]() Tags: [ci](), [ci-cd](), [develop](), [gitlab](), [gitlab-ci](), [merge](), [project-management](), [youtrack](), [youtube]() ### AI overview JetBrains YouTrack's release adds GitLab CI/CD integration, allowing tasks to be updated automatically based on GitLab pipeline results. The release also introduces similar-task detection in YouTrack Lite and a text editor improvement in YouTrack Classic. ### Source excerpt Привет, Хабр! На связи команда JetBrains YouTrack, и у нас для вас новый релиз! Мы дополнили интеграцию с GitLab -- теперь YouTrack не только отслеживает коммиты и merge-реквесты, но и поддерживает интеграцию с GitLab CI/CD. А это значит, что задачи в YouTrack смогут обновляться автоматически -- по результатам автоматизированных сборок в GitLab CI/CD. Также мы дополнили релиз интересными улучшениями для работы с задачами. За подробностями добро пожаловать под кат! Читать далее ## How to Successfully Hand Over Systems DevFeed: [How to Successfully Hand Over Systems]() Original publisher: [Read original article]() Published: 2021-04-20T00:00:00Z Content type: tutorial Language: en Sources: [SoundCloud Backstage Blog]() Topics: [systems](), [Template](), [Pull Request]() Tags: [documentation](), [engineering-management](), [how-to](), [operations](), [project-management](), [systems](), [work](), [workshops]() ### AI overview This article presents SoundCloud's guideline for handing system ownership from one team to another during organizational change. It recommends collaborative planning, documentation, meetings, pairing sessions, workshops, tasks, and PR reviews so the new team can understand, maintain, change, and improve the system. ### Source excerpt In a product company, changes are inevitable so as to best support the strategy and the vision. Often during such a change, new teams are... ## Как перенести на TypeScript большую кодовую базу React UI-компонентов DevFeed: [Как перенести на TypeScript большую кодовую базу React UI-компонентов]() Original publisher: [Read original article]() Author: Wint95r (Badoo) Published: 2020-09-09T10:07:01Z Content type: tutorial Language: ru Sources: [Badoo EN](), [Badoo RU]() Topics: [React](), [TypeScript](), [Front end](), [ui]() Tags: [badoo](), [frontend](), [javascript](), [project-management](), [react](), [types](), [typescript](), [ui](), [web-developement]() ### AI overview A Badoo UI developer describes migrating 630 React UI components to TypeScript. The article explains the reasons for the migration, including compile-time type safety, improved code reliability, and reuse across projects, as well as the phased process for introducing TypeScript to UI developers. ### Source excerpt Привет! Меня зовут Иван Греков, я работаю UI-разработчиком в frontend-команде Badoo. Главные задачи нашей команды -- создание новых и поддержка существующих пользовательских интерфейсов для сайтов и приложений Badoo и Bumble. Когда в конце 2019 года мы начали параллельно работать над несколькими проектами, мы задумались над повышением стабильности кода и возможностью его многократного использования. Для этого мы решили переписать наши 630 React UI-компонентов на TypeScript. Я расскажу о том, как мы работали над ними без перерыва в доставке фич и как организовали поэтапный переход на TypeScript для UI-разработчиков, которым этот язык был в новинку. Читать далее ## Strategy-Implementation Mismatch DevFeed: [Strategy-Implementation Mismatch]() Original publisher: [Read original article]() Published: 2018-12-14T07:24:14Z Content type: opinion Language: en Sources: [Blog by Michael Dubakov]() Topics: [Development](), [developer tooling](), [Agile](), [Software Engineering]() Tags: [article](), [development](), [jira](), [management](), [okr](), [project-management](), [software-development](), [tools](), [tracking]() ### AI overview The article argues that the gap between strategic goals and day-to-day implementation is a broader process problem, not something caused specifically by JIRA. It discusses how frameworks such as Extreme Programming, SAFe, OKR, and GIST connect strategy with execution, and notes that existing tools typically separate strategic planning from work tracking. ### Source excerpt JIRA is easy to hate. The latest article trashes JIRA and calls it an anti-pattern for software development. The main problem is work... ## Project Necromancy DevFeed: [Project Necromancy]() Original publisher: [Read original article]() Published: 2018-06-05T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Microservice](), [Back end](), [Git](), [Code]() Tags: [architecture](), [backend](), [code](), [development](), [git](), [project-management]() ### AI overview SoundCloud describes reviving a project that had been canceled and left dormant after a new microservice was added to its backend architecture. The team preserved the partially finished feature code in a git branch, and changing product priorities later made parts of the functionality important again. ### Source excerpt Or, how to raise a project from the dead with tools you probably have lying around at home. ## Managing Unplanned and Support Tasks DevFeed: [Managing Unplanned and Support Tasks]() Original publisher: [Read original article]() Published: 2018-03-26T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Process](), [Automation](), [systems](), [Slack]() Tags: [automation](), [bug](), [engineering](), [engineering-management](), [project-management](), [slack](), [support](), [systems](), [work]() ### AI overview The article describes how SoundCloud's Content Engineering Team developed a process for handling unplanned and support tasks. It explains how these tasks consume feature-development time, reduce visibility into team work, and create stress and context switching, then discusses problems with an open Slack-based request process and a single point of contact. ### Source excerpt One challenge engineering teams often face is dealing with work that doesn't revolve around developing new features but that still requires the team's attention and time. The Content Engineering Team here at SoundCloud is no exception, so we iterated on a process to deal with unplanned and support tasks to end up with fewer interruptions and more time to spend on implementing planned features. ## Deliver software faster by managing work in progress, not by adding overtime DevFeed: [Deliver software faster by managing work in progress, not by adding overtime]() Original publisher: [Read original article]() Published: 2017-09-27T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Software](), [Deployment](), [data](), [coding]() Tags: [bugs](), [code](), [deployment](), [development](), [engineering](), [engineering-management](), [metrics](), [monitor](), [product-development](), [project-management](), [reduce](), [software](), [strategy](), [workflow]() ### AI overview This article describes SoundCloud's efforts to improve product development flow by measuring lead time and cycle time and reducing work in progress. Its proposed strategy includes committing to fewer products, features, and tasks at once, reducing code inventory, and monitoring and reducing bugs instead of relying on overtime. ### Source excerpt Product development flow (flow) is the rate at which our products are developed, from idea to deployment. Good flow means that products should pass through the development cycle quickly and continuously. ## How Many Hours for Multithreading the Server? DevFeed: [How Many Hours for Multithreading the Server?]() Original publisher: [Read original article]() Published: 2014-09-02T18:25:58Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [coding](), [Software](), [servers]() Tags: [business](), [multithreading](), [project-management](), [server](), [software-developer]() ### AI overview The article argues that software developers often cannot reliably estimate the hours required for individual project steps, especially when the work is new. It distinguishes detailed task estimates from whole-project commitments and discusses how padded estimates can produce misleading schedules. ### Source excerpt How many hours for multithreading the server? Or: dealing with overly detailed project planning Many developers, me included, dread that moment. Someone sits down with you and wants to know how many "hours" each step of the project will take. And of course the thing is, if you are doing something that has been done many times before, you might be able to provide a detailed estimate. People that build houses work like this, but they still often get it wrong. ## Visual Management Software DevFeed: [Visual Management Software]() Original publisher: [Read original article]() Published: 2014-04-22T12:10:12Z Content type: opinion Language: en Sources: [Blog by Michael Dubakov]() Topics: [Software](), [dashboards](), [data](), [GUI]() Tags: [dashboards](), [data](), [interactive](), [project-management](), [reports](), [software](), [visualization]() ### AI overview The article argues that existing project management tools make information difficult to find, visualize, and modify. It presents information visualization as the ability to extract, represent, and manipulate project data interactively, including through lists, boards, and timelines. ### Source excerpt Targetprocess [Next page]()