https://engineering-leadership-preview.hinshelwood.com/tags/product-developer/ Recent content in Product Developer on Engineering Leadership in AI & Software Hugo en Tue, 16 Jun 2026 17:40:35 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/ Thu, 10 Dec 2020 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/ Staggered iterations slow feedback, increase technical debt, and reduce software quality, making delivery less agile and more expensive. Instead, form cross-functional teams that deliver working software every iteration, integrate all required work including testing into each sprint, and automate as much as possible. Shift away from staged handoffs to continuous, team-owned delivery to improve value and quality. https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/ Thu, 03 Dec 2020 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/ Professional Scrum teams must deliver high-quality, working software every sprint, prioritizing quality over speed or feature quantity to build trust and protect the organization’s reputation. Developers are accountable for quality and should use automation, DevOps practices, and continuous improvement to avoid technical debt and defects. Managers should empower teams to focus on quality, address technical debt in retrospectives, and consider upskilling developers through professional training. https://engineering-leadership-preview.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/ Thu, 17 Dec 2020 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/ If your team starts Sprint Planning with backlog items that are not well understood or sized to fit within a sprint, you are setting up for failure. Regular backlog refinement is essential so developers can confidently select and deliver work, and lack of refinement often leads to missed goals and confusion. Make sure your team spends enough time refining upcoming backlog items so they are clear, appropriately sized, and ready for selection in the next two sprints. https://engineering-leadership-preview.hinshelwood.com/guides/scrum-guide/ Mon, 01 Feb 2010 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/guides/scrum-guide/ A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to complex problems. https://engineering-leadership-preview.hinshelwood.com/recipes/daily-scrum-recipe/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/recipes/daily-scrum-recipe/ Guidance for running effective Daily Scrum meetings, focusing on collaboration, transparency, and actionable planning to help teams achieve their Sprint Goals. https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-incorporate-a-design-sprint-in-scrum/ Fri, 16 Aug 2019 12:35:31 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/how-do-you-incorporate-a-design-sprint-in-scrum/ Design Sprints should not be treated as separate or special sprints in Scrum; instead, design and UX work should be integrated into regular sprints as part of the team’s ongoing activities or handled during backlog refinement for future work. All team members should collaborate on these tasks, leveraging individual skills without creating silos or specialist-only phases. Development managers should ensure design activities are visible, collaborative, and aligned with sprint goals, using communities of practice to share knowledge across teams. https://engineering-leadership-preview.hinshelwood.com/tags/product-developer/ Mon, 20 Jan 2025 10:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/product-developer/ Product Developer is a role and an accountability within Scrum and product development frameworks. All Product Developers together should possess all the skills needed to create Increments, with their combined skill set often referred to as cross-functional. Product Developers may be human or automated, committed to creating, researching, inspecting, and adapting any aspect of a releasable Increment each Sprint. Their primary focus is on the current Sprint, with some capacity invested in future-looking refinement and examining result feedback. Product Developers adhere to the Definition of Output Done and strive for net improvement, achieving the best results when they focus solely on one Product. They should adopt appropriate behaviors including collaborator, creator, and champion of technical quality, discovery, delivery, and value validation. Product Developers are collectively accountable for creating an emergent plan in the Sprint Backlog, instilling quality, creating usable Increments, learning through data, adapting their plan toward the Sprint Goal, holding each other accountable as professionals, and driving net improvement.