Discover the best ways to customize your agile workflow. Learn how to adapt your process to your team’s needs, and then configure your tools to support your unique workflow.
Posts for: #Sprint
Breaking down complex stories
Does story size really matter? A developer’s perspective on why breaking down complex stories during the sprint is more important than over-refining them beforehand. Learn how to embrace emergent design and continuous planning.
Scrum team - handling analysis work on future dev?
Practical guidance on how much analysis a Scrum team should do before a sprint and when to keep planning lightweight.
How do you schedule in the sprint the time it takes to debug and fix a bug?
Bugs are inevitable, but how should you schedule time to fix them? This post argues against delaying bug fixes and advocates for prioritizing them immediately to maintain product quality and team efficiency.
When is Your Sprint in Trouble?
Why burndown charts can mislead and how the Daily Scrum and Sprint Goal reveal real sprint health.
Sprint planning and estimating on the sub task level
Should you estimate at the subtask level? A pragmatic take on estimation, planning, and focusing on outcomes instead of numbers.
Daily status meeting
Is your Daily Scrum just a series of status updates? A look at a common misunderstanding of this key Scrum event. Discover why the Daily Scrum is a planning meeting for developers, not a status report, and what it means for team collaboration.
Sprint partitioning
Should you partition your sprint into fixed percentages for features, bugs, and tech debt? An alternative approach to balancing new development with maintenance. Discover why integrating refactoring into your user stories might be a more effective way to improve code quality.
Handling Sprint Spillover Stories in Jira
Struggling with sprint spillover and story points in Jira? Stop the Excel madness and discover a simpler approach. Learn why re-estimating unfinished work as a new story can help you focus on value and not get lost in the numbers.
Agile set up
How do you set up an agile team? It’s not just about sprints. Discover why focusing on goals, feedback, and technical excellence is more important than just adopting a framework like Scrum. Learn about the Agile Fluency Model as a guide for your agile journey.
Feature factory
Why won’t your team commit to Sprint Goals? A look at a common problem: the ‘feature factory’. Discover why developers might resist sprint goals when they’re just being handed tickets, and what it says about your agile process.
My team stopped doing sprints
What happens when a team stops doing sprints? A look at a team that ditched traditional Scrum ceremonies for a more continuous workflow. Discover how they handle planning, priorities, and large-scale work without sprints.
Why are we doing Scrum?
Scrum vs. Kanban: which is more agile? A simple answer to a common question. Discover why agility is about culture, not the framework you use, and how you can be agile with or without Scrum.
How to make Scrum fun?
Is your Daily Scrum a boring status report? Learn the true purpose of this crucial Scrum event. It’s not about standing up or making it ‘fun’ – it’s about effective daily planning for the development team. Discover how to fix a broken Daily Scrum.
Not-finished task estimation
Should you re-estimate unfinished tasks from a sprint? A pragmatic take on story points, velocity, and what really matters in agile development. Learn why re-estimation can be a useful tool to encourage your team to ‘start less, finish more’.
How do you handle unplanned work?
Drowning in technical debt and unplanned work? Read a real-life story of a team that ditched long sprints for a more adaptive, flow-based process. Discover how shortening your feedback cycle can help you navigate a dynamic environment and deliver value.
Story Progression Workflow in Gitlab
Is your GitLab workflow too complicated? See a critique of a waterfall-like story progression and discover an alternative approach based on Continuous Delivery and Extreme Programming. Learn how to shorten feedback cycles and build quality into your development process.
How to develop frontend and backend in the same sprint without code freeze
Struggling to ship features in your two-week sprints? Dissect a common development dilemma: coordinating frontend and backend work without resorting to a feature freeze. Discover practical engineering practices like API contracts and Trunk-Based Development that can help your team merge code multiple times a day and release with confidence.
Velocity problem
Constantly chasing a higher velocity? Challenge the obsession with story points and discover why focusing on product goals and outcomes is the key to truly agile teams. Learn how to shift your team’s mindset and measure what truly matters.