> For the complete documentation index, see [llms.txt](https://www.pmguidebook.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pmguidebook.com/process-skills/development/development-execution-and-methodologies.md). # Development Execution and Methodologies Development execution and methodologies refer to the processes and techniques used to guide the development of a product or feature. This includes selecting and implementing a development methodology (such as Agile, Scrum, Linear Method, or Waterfall), coordinating with the development team, tracking progress, and managing issues and changes. The goal is to ensure that the development process is efficient, effective, and aligned with the product requirements and business objectives. While there’s multiple types and iterations of these methodologies, it’s important to note that the best version is the one that everyone on the team can get behind and execute effectively. If there’s no structure in place, generally it’s recommended to follow Agile “by the book” and reassess over time by adjusting or removing parts of the methodology that don’t work for your team. If you’re looking for a more modern approach, I recommend you give the Linear Method a try, which is by the project management tool called Linear. ## Example Let's continue with the professional networking example. As the requirements and designs for the "Enhanced Job Filtering" feature become clearer, the PM works with the team to guide its development. Their team uses the Agile methodology, which allows for iterative development and frequent feedback. This methodology allows the team to test different filtering options and adjust based on user feedback. The Product Manager works closely with the development team to break down the various aspects of the feature from the PRD and design into smaller, manageable tasks, which are then organized into epics and sprints. An epic is a large body of work that can be broken down into a number of smaller tasks, or stories. For example, there might be an epic focused on updating the website interface to work with the new search functionality and a second epic to update the backend to search the database using the new filters. Sprints are typically two weeks long, which is long enough for a developer to finish a meaningful amount of work and short enough to be able to commit fully to completing the outlined task. Depending on the size and complexity of the feature, it could take multiple sprints to complete all of the engineering tasks required to finish. For the “Enhanced Job Filtering” feature, the team might estimate 2 epics and a total of 3 sprints (or 6 weeks). During each sprint, they test working increments against agreed behaviors, such as combining filters and handling an empty result. They review the actual results alongside the code, rather than waiting until every engineering task is complete to find out whether the flow works. A working prototype can inform this scope, but its speed of creation does not determine the time needed for integration and release. Throughout the development process, the Product Manager attends daily stand-up meetings with the team to track progress, address issues, and make necessary adjustments. As a team, they use tools like Linear or Jira to manage tasks and track progress, and Slack for communication. The PRD, engineering tasks, designs, and tests need to stay consistent about the problem and intended behavior. The PM keeps the requirements and important decisions current, linking to implementation detail rather than duplicating every task. If a test changes the team's understanding of a filter, that decision should be reflected where the next person will rely on it. ## Pain Points Coordinating the development process can be challenging, especially when dealing with complex features or tight deadlines. It requires effective communication, problem-solving skills, and the ability to adapt to changes. Selecting the right development methodology and using it effectively is also crucial, as it can significantly impact the speed and quality of development. ## Practical Exercise Think about a product or feature you want to develop. How would you break down the development process into manageable tasks? ## Related Research Topics * Agile development methodology \[ [Google](https://www.google.com/search?q=Agile%20development%20methodology%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Agile%20development%20methodology%20in%20product%20management) ] * ShapeUp \[ [Google](https://www.google.com/search?q=ShapeUp+in+product+management) | [Perplexity](https://www.perplexity.ai/?q=The%20Linear%20Method%20in%20product%20management) ] * Scrum \[ [Google](https://www.google.com/search?q=Scrum%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Scrum%20in%20product%20management) ] * Kanban \[ [Google](https://www.google.com/search?q=Kanban%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Kanban%20in%20product%20management) ] * Waterfall \[ [Google](https://www.google.com/search?q=Waterfall%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Waterfall%20in%20product%20management) ] * The Linear Method \[ [Google](https://www.google.com/search?q=The%20Linear%20Method%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=The%20Linear%20Method%20in%20product%20management) ] * Code Complete \[ [Google](https://www.google.com/search?q=Code%20Complete%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=ShapeUp%20in%20product%20management) ] * Definition of Done in software engineering \[ [Google](https://www.google.com/search?q=Definition%20of%20Done%20in%20software%20engineering%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Definition%20of%20Done%20in%20software%20engineering%20in%20product%20management) ] --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.pmguidebook.com/process-skills/development/development-execution-and-methodologies.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.