Posts for: #Sprint

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.

[Read more]

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.

[Read more]

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.

[Read more]

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.

[Read more]

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.

[Read more]