[{"data":1,"prerenderedAt":459},["ShallowReactive",2],{"/en-us/the-source/authors/amanda-rueda/":3,"footer-en-us":34,"the-source-navigation-en-us":342,"the-source-newsletter-en-us":369,"amanda-rueda-articles-list-authors-en-us":381,"amanda-rueda-articles-list-en-us":412,"amanda-rueda-page-categories-en-us":458},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"config":8,"seo":10,"content":12,"type":26,"slug":27,"_id":28,"_type":29,"title":11,"_source":30,"_file":31,"_stem":32,"_extension":33},"/en-us/the-source/authors/amanda-rueda","authors",false,"",{"layout":9},"the-source",{"title":11},"Amanda Rueda",[13,24],{"type":14,"componentName":14,"componentContent":15},"TheSourceAuthorHero",{"config":16,"name":11,"role":19,"bio":20,"headshot":21},{"gitlabHandle":17,"linkedInProfileUrl":18},"amandarueda","https://www.linkedin.com/in/amandamrueda/","Senior Product Manager","Amanda Rueda is a Senior Product Manager at GitLab, specializing in strategic product vision, agile planning, and leveraging AI to enhance workflows and user experiences. Amanda is a thought leader in agile planning and product management workflows, and enjoys building GitLab features that drive team collaboration, transparent project management, and high-performing teams.",{"altText":11,"config":22},{"src":23},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463383/osecw1pzbxvb7fhqhiky.png",{"componentName":25,"type":25},"TheSourceArticlesList","author","amanda-rueda","content:en-us:the-source:authors:amanda-rueda.yml","yaml","content","en-us/the-source/authors/amanda-rueda.yml","en-us/the-source/authors/amanda-rueda","yml",{"_path":35,"_dir":36,"_draft":6,"_partial":6,"_locale":7,"data":37,"_id":338,"_type":29,"title":339,"_source":30,"_file":340,"_stem":341,"_extension":33},"/shared/en-us/main-footer","en-us",{"text":38,"source":39,"edit":45,"contribute":50,"config":55,"items":60,"minimal":330},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":40,"config":41},"View page source",{"href":42,"dataGaName":43,"dataGaLocation":44},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":46,"config":47},"Edit this page",{"href":48,"dataGaName":49,"dataGaLocation":44},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":51,"config":52},"Please contribute",{"href":53,"dataGaName":54,"dataGaLocation":44},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":56,"facebook":57,"youtube":58,"linkedin":59},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[61,88,161,229,291],{"title":62,"links":63,"subMenu":69},"Platform",[64],{"text":65,"config":66},"DevSecOps platform",{"href":67,"dataGaName":68,"dataGaLocation":44},"/platform/","devsecops platform",[70],{"title":71,"links":72},"Pricing",[73,78,83],{"text":74,"config":75},"View plans",{"href":76,"dataGaName":77,"dataGaLocation":44},"/pricing/","view plans",{"text":79,"config":80},"Why Premium?",{"href":81,"dataGaName":82,"dataGaLocation":44},"/pricing/premium/","why premium",{"text":84,"config":85},"Why Ultimate?",{"href":86,"dataGaName":87,"dataGaLocation":44},"/pricing/ultimate/","why ultimate",{"title":89,"links":90},"Solutions",[91,96,101,106,111,116,121,126,131,136,141,146,151,156],{"text":92,"config":93},"Digital transformation",{"href":94,"dataGaName":95,"dataGaLocation":44},"/topics/digital-transformation/","digital transformation",{"text":97,"config":98},"Security & Compliance",{"href":99,"dataGaName":100,"dataGaLocation":44},"/solutions/security-compliance/","security & compliance",{"text":102,"config":103},"Automated software delivery",{"href":104,"dataGaName":105,"dataGaLocation":44},"/solutions/delivery-automation/","automated software delivery",{"text":107,"config":108},"Agile development",{"href":109,"dataGaName":110,"dataGaLocation":44},"/solutions/agile-delivery/","agile delivery",{"text":112,"config":113},"Cloud transformation",{"href":114,"dataGaName":115,"dataGaLocation":44},"/topics/cloud-native/","cloud transformation",{"text":117,"config":118},"SCM",{"href":119,"dataGaName":120,"dataGaLocation":44},"/solutions/source-code-management/","source code management",{"text":122,"config":123},"CI/CD",{"href":124,"dataGaName":125,"dataGaLocation":44},"/solutions/continuous-integration/","continuous integration & delivery",{"text":127,"config":128},"Value stream management",{"href":129,"dataGaName":130,"dataGaLocation":44},"/solutions/value-stream-management/","value stream management",{"text":132,"config":133},"GitOps",{"href":134,"dataGaName":135,"dataGaLocation":44},"/solutions/gitops/","gitops",{"text":137,"config":138},"Enterprise",{"href":139,"dataGaName":140,"dataGaLocation":44},"/enterprise/","enterprise",{"text":142,"config":143},"Small business",{"href":144,"dataGaName":145,"dataGaLocation":44},"/small-business/","small business",{"text":147,"config":148},"Public sector",{"href":149,"dataGaName":150,"dataGaLocation":44},"/solutions/public-sector/","public sector",{"text":152,"config":153},"Education",{"href":154,"dataGaName":155,"dataGaLocation":44},"/solutions/education/","education",{"text":157,"config":158},"Financial services",{"href":159,"dataGaName":160,"dataGaLocation":44},"/solutions/finance/","financial services",{"title":162,"links":163},"Resources",[164,169,174,179,184,189,194,199,204,209,214,219,224],{"text":165,"config":166},"Install",{"href":167,"dataGaName":168,"dataGaLocation":44},"/install/","install",{"text":170,"config":171},"Quick start guides",{"href":172,"dataGaName":173,"dataGaLocation":44},"/get-started/","quick setup checklists",{"text":175,"config":176},"Learn",{"href":177,"dataGaName":178,"dataGaLocation":44},"https://university.gitlab.com/","learn",{"text":180,"config":181},"Product documentation",{"href":182,"dataGaName":183,"dataGaLocation":44},"https://docs.gitlab.com/","docs",{"text":185,"config":186},"Blog",{"href":187,"dataGaName":188,"dataGaLocation":44},"/blog/","blog",{"text":190,"config":191},"Customer success stories",{"href":192,"dataGaName":193,"dataGaLocation":44},"/customers/","customer success stories",{"text":195,"config":196},"Remote",{"href":197,"dataGaName":198,"dataGaLocation":44},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"text":200,"config":201},"GitLab Services",{"href":202,"dataGaName":203,"dataGaLocation":44},"/services/","services",{"text":205,"config":206},"TeamOps",{"href":207,"dataGaName":208,"dataGaLocation":44},"/teamops/","teamops",{"text":210,"config":211},"Community",{"href":212,"dataGaName":213,"dataGaLocation":44},"/community/","community",{"text":215,"config":216},"Forum",{"href":217,"dataGaName":218,"dataGaLocation":44},"https://forum.gitlab.com/","forum",{"text":220,"config":221},"Events",{"href":222,"dataGaName":223,"dataGaLocation":44},"/events/","events",{"text":225,"config":226},"Partners",{"href":227,"dataGaName":228,"dataGaLocation":44},"/partners/","partners",{"title":230,"links":231},"Company",[232,237,242,247,252,257,262,266,271,276,281,286],{"text":233,"config":234},"About",{"href":235,"dataGaName":236,"dataGaLocation":44},"/company/","company",{"text":238,"config":239},"Jobs",{"href":240,"dataGaName":241,"dataGaLocation":44},"/jobs/","jobs",{"text":243,"config":244},"Leadership",{"href":245,"dataGaName":246,"dataGaLocation":44},"/company/team/e-group/","leadership",{"text":248,"config":249},"Team",{"href":250,"dataGaName":251,"dataGaLocation":44},"/company/team/","team",{"text":253,"config":254},"Handbook",{"href":255,"dataGaName":256,"dataGaLocation":44},"https://handbook.gitlab.com/","handbook",{"text":258,"config":259},"Investor relations",{"href":260,"dataGaName":261,"dataGaLocation":44},"https://ir.gitlab.com/","investor relations",{"text":263,"config":264},"Sustainability",{"href":265,"dataGaName":263,"dataGaLocation":44},"/sustainability/",{"text":267,"config":268},"Diversity, inclusion and belonging (DIB)",{"href":269,"dataGaName":270,"dataGaLocation":44},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":272,"config":273},"Trust Center",{"href":274,"dataGaName":275,"dataGaLocation":44},"/security/","trust center",{"text":277,"config":278},"Newsletter",{"href":279,"dataGaName":280,"dataGaLocation":44},"/company/contact/","newsletter",{"text":282,"config":283},"Press",{"href":284,"dataGaName":285,"dataGaLocation":44},"/press/","press",{"text":287,"config":288},"Modern Slavery Transparency Statement",{"href":289,"dataGaName":290,"dataGaLocation":44},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"title":292,"links":293},"Contact Us",[294,299,304,309,314,319,324],{"text":295,"config":296},"Contact an expert",{"href":297,"dataGaName":298,"dataGaLocation":44},"/sales/","sales",{"text":300,"config":301},"Get help",{"href":302,"dataGaName":303,"dataGaLocation":44},"/support/","get help",{"text":305,"config":306},"Customer portal",{"href":307,"dataGaName":308,"dataGaLocation":44},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"text":310,"config":311},"Status",{"href":312,"dataGaName":313,"dataGaLocation":44},"https://status.gitlab.com/","status",{"text":315,"config":316},"Terms of use",{"href":317,"dataGaName":318,"dataGaLocation":44},"/terms/","terms of use",{"text":320,"config":321},"Privacy statement",{"href":322,"dataGaName":323,"dataGaLocation":44},"/privacy/","privacy statement",{"text":325,"config":326},"Cookie preferences",{"dataGaName":327,"dataGaLocation":44,"id":328,"isOneTrustButton":329},"cookie preferences","ot-sdk-btn",true,{"items":331},[332,334,336],{"text":315,"config":333},{"href":317,"dataGaName":318,"dataGaLocation":44},{"text":320,"config":335},{"href":322,"dataGaName":323,"dataGaLocation":44},{"text":325,"config":337},{"dataGaName":327,"dataGaLocation":44,"id":328,"isOneTrustButton":329},"content:shared:en-us:main-footer.yml","Main Footer","shared/en-us/main-footer.yml","shared/en-us/main-footer",{"_path":343,"_dir":9,"_draft":6,"_partial":6,"_locale":7,"logo":344,"subscribeLink":349,"navItems":353,"_id":365,"_type":29,"title":366,"_source":30,"_file":367,"_stem":368,"_extension":33},"/shared/en-us/the-source/navigation",{"altText":345,"config":346},"the source logo",{"src":347,"href":348},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1750191004/t7wz1klfb2kxkezksv9t.svg","/the-source/",{"text":350,"config":351},"Subscribe",{"href":352},"#subscribe",[354,358,361],{"text":355,"config":356},"Artificial Intelligence",{"href":357},"/the-source/ai/",{"text":97,"config":359},{"href":360},"/the-source/security/",{"text":362,"config":363},"Platform & Infrastructure",{"href":364},"/the-source/platform/","content:shared:en-us:the-source:navigation.yml","Navigation","shared/en-us/the-source/navigation.yml","shared/en-us/the-source/navigation",{"_path":370,"_dir":9,"_draft":6,"_partial":6,"_locale":7,"title":371,"description":372,"submitMessage":373,"formData":374,"_id":378,"_type":29,"_source":30,"_file":379,"_stem":380,"_extension":33},"/shared/en-us/the-source/newsletter","The Source Newsletter","Stay updated with insights for the future of software development.","You have successfully signed up for The Source’s newsletter.",{"config":375},{"formId":376,"formName":377,"hideRequiredLabel":329},1077,"thesourcenewsletter","content:shared:en-us:the-source:newsletter.yml","shared/en-us/the-source/newsletter.yml","shared/en-us/the-source/newsletter",{"amanda-rueda":11,"andre-michael-braun":382,"andrew-haschka":383,"ayoub-fandi":384,"bob-stevens":385,"brian-wald":386,"bryan-ross":387,"chandler-gibbons":388,"dave-steer":389,"ddesanto":390,"derek-debellis":391,"emilio-salvador":392,"erika-feldman":393,"george-kichukov":394,"gitlab":395,"grant-hickman":396,"haim-snir":397,"iganbaruch":398,"jlongo":399,"joel-krooswyk":400,"josh-lemos":401,"julie-griffin":402,"kristina-weis":403,"lee-faus":404,"ncregan":405,"rschulman":406,"sabrina-farmer":407,"sandra-gittlen":408,"sharon-gaudin":409,"stephen-walters":410,"taylor-mccaslin":411},"Andre Michael Braun","Andrew Haschka","Ayoub Fandi","Bob Stevens","Brian Wald","Bryan Ross","Chandler Gibbons","Dave Steer","David DeSanto","Derek DeBellis","Emilio Salvador","Erika Feldman","George Kichukov","GitLab","Grant Hickman","Haim Snir","Itzik Gan Baruch","Joseph Longo","Joel Krooswyk","Josh Lemos","Julie Griffin","Kristina Weis","Lee Faus","Niall Cregan","Robin Schulman","Sabrina Farmer","Sandra Gittlen","Sharon Gaudin","Stephen Walters","Taylor McCaslin",{"allArticles":413,"visibleArticles":457,"showAllBtn":329},[414],{"_path":415,"_dir":416,"_draft":6,"_partial":6,"_locale":7,"config":417,"seo":421,"content":425,"type":452,"slug":453,"category":416,"_id":454,"_type":29,"title":422,"_source":30,"_file":455,"_stem":456,"_extension":33,"date":426,"description":423,"timeToRead":427,"heroImage":424,"keyTakeaways":428,"articleBody":432,"faq":433},"/en-us/the-source/platform/why-your-development-team-should-plan-small-to-deliver-big","platform",{"layout":9,"template":418,"articleType":419,"author":27,"featured":6,"gatedAsset":420,"isHighlighted":6,"authorName":11},"TheSourceArticle","Regular","source-lp-navigating-a-smooth-transition-to-agile-planning",{"title":422,"description":423,"ogImage":424},"Why your development team should plan small to deliver big","Discover how strategic quarterly product planning can drive meaningful progress toward long-term goals and maximize your organization's success.","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751464024/paqecyxpszplzdwohg9d.png",{"title":422,"date":426,"description":423,"timeToRead":427,"heroImage":424,"keyTakeaways":428,"articleBody":432,"faq":433},"2025-01-22","5 min read",[429,430,431],"Strategic quarterly planning is key to achieving organizational objectives. It aligns resources, focuses teams on high-impact work, and drives meaningful progress toward long-term goals.","Successful quarterly planning involves aligning goals with the company's vision, incorporating diverse insights, breaking down large projects into smaller increments, and continually tying execution to long-term success metrics.","Effective planning practices include employing the Hoshin Kanri framework for goal alignment, championing iterative planning, leveraging early team involvement, prioritizing customer feedback, and measuring success with the right metrics.","_Plan smaller than you think you can deliver._\n\nThis counterintuitive advice might seem to contradict everything you know about ambitious goal-setting. Yet when it comes to planning your software development roadmap, this principle often leads to greater success. Why? Because effective quarterly planning isn't about cramming in more features or technical objectives - it's about strategically connecting daily engineering execution to long-term product vision.\n\nWhen organizations transform quarterly planning from a routine exercise into a powerful driver of progress, they discover proven approaches: breaking down ambitious goals into achievable steps, tying execution to company vision, and keeping customer feedback at the core of every decision.\n\n## What makes quarterly planning truly strategic?\nQuarterly planning is more than just setting goals and priorities for the next few months. It’s about aligning those goals and priorities with the overall vision and strategy of the organization. Quarterly planning should be guided by a clear understanding of the company’s long-term objectives and how each team’s work contributes to those objectives. To that end, strategic quarterly planning should:\n\n- Link daily tasks to high-impact business outcomes\n- Break large projects into smaller increments that all deliver value\n- Incorporate insights from teams with diverse expertise\n- Be rooted in the needs of actual users and customers\n- Connect day-to-day execution with long-term success metrics\n\nThis approach makes it easier to track progress, adapt to changes dynamically, and celebrate successes that align with the company's vision. **At the end of a successful quarterly planning cycle, teams should have a clear set of outcomes and artifacts, such as well-defined objectives, a prioritized roadmap, assigned tasks, and agreed-upon metrics for success**. Now, let’s explore how to build and implement strategic quarterly planning that drives results and keeps teams motivated and aligned.\n\n## Tips for successful quarterly planning\nThrough conversations with leaders and peers across industries, I’ve identified some key practices to help organizations of all sizes unlock their full potential during the quarterly planning process.\n\n### Align quarterly goals with the bigger picture\nA recurring theme in my conversations with Product Managers (PMs) is the need to tie quarterly objectives back to the broader company goals. If you can see how your work fits into the grand scheme, it’s easier to prioritize what matters most. One PM told me, _“Quarterly planning isn’t just about getting stuff done; it’s about making sure we’re still heading toward our North Star.”_\n\nThat’s where a framework like _[Hoshin Kanri](https://www.leanproduction.com/hoshin-kanri/)_ can come in handy. Originating from Japanese management practices, Hoshin Kanri ensures every part of the organization is aligned with the company’s most critical goals. It breaks down big-picture objectives into actionable, measurable steps and cascades them across teams. By linking daily tasks to strategic outcomes, the framework gives everyone on the team a clearer sense of purpose and an understanding of how their work contributes to organizational success.\n\n_**Pro tip**: Utilize a platform that connects company [objectives and key results (OKRs)](https://docs.gitlab.com/ee/user/okrs.html) to your product roadmap as a powerful way to create alignment and focus across teams and highlight connections between development tasks and big-picture goals directly within the tool._\n\n### Plan less to accomplish more: The art of iteration\nRemember that counterintuitive advice from earlier about planning smaller? Here’s why it works: Inevitably, work always expands. Even the most detailed quarterly plans can’t anticipate every challenge, opportunity, or shifted priority. That's why planning smaller delivers bigger results. For teams to succeed, leaders must champion a culture that encourages incremental planning. Empowering teams to think [iteratively](https://handbook.gitlab.com/handbook/values/#iteration) - breaking down ambitious goals into smaller, achievable steps without fear of falling short - fosters a mindset of learning and adapting to rapid feedback.\n\nConsider _[vertical slicing](https://careers.webjet.com.au/category/agile/)_: breaking a project into smaller pieces that deliver end-to-end value. Let’s say your team is building a dashboard for tracking product metrics. Optimize your plan to deliver small vertical slices that provide user value in each iteration:\n\n1. Build the data pipeline to collect and display one key metric, such as user engagement.\n1. Add functionality for filtering and sorting the data.\n1. Introduce visualizations for trends over time.\n1. Extend the dashboard with customization options based on user feedback.\n\nBy delivering functional increments, you allow for smaller reviews, early testing, faster feedback, and incremental value delivery, all while staying aligned with larger goals.\n\n_**Pro tip**: Use your tool's nested work item framework to create clear workstreams and enable efficient progress tracking. For example, in GitLab, this translates to using epics, issues, and tasks to maintain alignment with overarching objectives._\n\n### Bring in the entire team early\nPlanning in isolation - failing to involve contributors early in the process - is a common mistake I see customers make during their planning cycles. Engineers, designers, and other key stakeholders bring unique insights that can shape better solutions and prevent surprises later.\n\n[Experts](https://www.producttalk.org/2024/06/product-trios/) indicate that teams with diverse expertise are more likely to generate innovative ideas. Engineers can flag technical constraints or opportunities early, while designers ensure the user experience remains central to decision-making. Early collaboration reduces downstream friction, keeps the team focused on the problem to solve, and accelerates delivery.\n\n_**Pro tip**: A single end-to-end software development platform with real-time visibility helps teams avoid siloed decisions, collaborate effectively, and ensure alignment from day one._\n\n### Keep customer feedback at the heart of planning\nWithout listening to your customers, you’re navigating based on assumptions. Product owners who regularly engage customers stay closer to what really matters, ensuring that planning decisions are rooted in actual user needs.\n\nThis is where another key planning method, _[Dual-Track Agile](https://medium.com/@daviddenham07/dual-track-agile-the-secret-sauce-to-outcome-based-development-601f6003ea73)_, really shines. Dual-Track Agile separates product development into two parallel tracks:\n\n- **Discovery**, where teams gather insights, validate ideas, and explore potential solutions\n- **Delivery**, where teams build and ship validated solutions\n\nDual-Track Agile allows teams to focus on gathering insights from users and customers without stopping or slowing down the process. For example, while one team interviews customers and prototypes ideas, another can work on developing features based on validated needs - ensuring that teams are always working on the right problems while maintaining a steady delivery cadence.\n\n_**Pro tip**: Use a tool that supports [seamless collaboration, prioritization, and insight-sharing across workstreams](https://about.gitlab.com/solutions/visibility-measurement/) so your teams can use customer feedback to inform every decision, keeping work aligned with user needs and business goals._\n\n### Measure success with the right metrics\nMetrics are more than just numbers - they guide how closely your quarterly objectives remain aligned with your company’s strategic goals.\n\nFor development teams, _[DORA metrics](https://about.gitlab.com/solutions/value-stream-management/dora/)_ offer powerful insights into efficiency and reliability. Teams can identify bottlenecks, improve workflows, and ensure delivery aligns with planned timelines. When paired with business indicators, such as customer satisfaction and feature adoption, these operational metrics connect day-to-day execution with long-term success.\n\nAdopting a reliable measurement practice helps you course-correct during the quarter and informs the retrospective process. By reflecting on what worked and what didn’t, you can continuously improve your approach to quarterly planning and maintain focus on strategic objectives.\n\n_**Pro tip**: By surfacing DORA metrics and other value stream analytics in a [comprehensive insights dashboard](https://about.gitlab.com/blog/data-driven-devsecops-exploring-gitlab-insights-dashboards/), you can easily track the time it takes to go from an idea to production with customizable, data-driven views._\n\n## Wrapping up: Make quarterly planning work for you\nQuarterly planning isn’t just about organizing tasks or hitting deadlines - it’s about aligning your team’s efforts with your company’s most strategic goals.\n\nBy tying goals to the bigger picture, embracing customer insights, and creating a culture of collaboration, you position your organization to meet quarterly objectives and drive long-term growth and success.",[434,437,440,443,446,449],{"header":435,"content":436},"Why should development teams plan smaller than they think they can deliver?","Planning smaller allows teams to remain adaptable and focused on delivering incremental value. While it may feel counterintuitive, smaller plans leave room for unforeseen changes and allow teams to iterate more effectively. This approach encourages continuous learning, fosters a culture of agility, and ultimately leads to bigger, more sustainable outcomes.",{"header":438,"content":439},"What makes quarterly planning truly strategic for software development teams?","Strategic quarterly planning aligns day-to-day work with long-term business goals. It connects team execution to company vision, prioritizes customer needs, and breaks down ambitious goals into manageable tasks. Successful quarterly planning results in clearly defined objectives, prioritized roadmaps, and meaningful metrics that reflect real progress.",{"header":441,"content":442},"How can development teams stay aligned with company objectives during planning?","Teams can stay aligned by using frameworks like Hoshin Kanri, which break down top-level goals into actionable steps. Linking individual tasks to broader business outcomes ensures that all team efforts contribute to the organization's success and allows for better prioritization and focus across projects.",{"header":444,"content":445},"Why is it important to involve the entire team early in the planning process?","Involving engineers, designers, and stakeholders from the beginning brings diverse expertise to the table and leads to better planning outcomes. Early collaboration helps surface technical limitations, informs user experience considerations, and reduces friction later in the development cycle.",{"header":447,"content":448},"How does customer feedback enhance quarterly planning?","Regular customer engagement ensures that planning decisions reflect real user needs. By adopting methods like Dual-Track Agile, which separates discovery from delivery, teams can continuously validate ideas while maintaining development momentum. This keeps teams focused on solving the right problems and delivering solutions that matter.",{"header":450,"content":451},"What role do metrics play in successful quarterly planning?","Metrics help track progress and ensure alignment with strategic goals. Operational metrics like DORA provide insight into delivery efficiency, while customer-centric metrics such as satisfaction and feature adoption offer a broader perspective on impact. Together, they enable continuous improvement and informed decision-making throughout the quarter.","article","why-your-development-team-should-plan-small-to-deliver-big","content:en-us:the-source:platform:why-your-development-team-should-plan-small-to-deliver-big:index.yml","en-us/the-source/platform/why-your-development-team-should-plan-small-to-deliver-big/index.yml","en-us/the-source/platform/why-your-development-team-should-plan-small-to-deliver-big/index",[414],{"ai":355,"platform":362,"security":97},1753207407577]