A user story helps agile software development teams capture a simple, high-level description of user requirements, written from the user perspective. For agile software development, writing good user stories is essential. Here's why.

These five agile estimation techniques help prioritize a backlog so sprint planning is simple and fast. The bottom line? The most important work goes first.

Estimation is a common challenge for agile software development teams. Story points have become the go-to measure to estimate the effort, and are often used to gauge performance. But what are the risks of relying too heavily on velocity as a guide?

Agile sprint planning sets up the success of each sprint. A great sprint planning session involves prioritizing backlog items and identifying your team capacity.

Agile meetings get everyone on the same page for an agile sprint or Scrum. To make them effective, keep empowering all voices and incorporating feedback.

Learn how to ensure your product backlog is in excellent health by following the DEEP acronym.

A sprint backlog should be continually updated to reflect market changes and customer needs. Here’s how sprint backlogs and their updates fit into agile teams.

Backlog refinement, a must-do for any agile team that doesn’t want to waste money, keeps the backlog updated and accurate. Here’s what to do and avoid in the process.

What A User Story Map Achieves that a Flat Product Backlog Can’t