Writing Effective User Stories

The 3 Cā€™s (Card, Conversion, Confirmation) of User Stories
Role ā€“ The user should be an actual human who interacts with the system.
Action ā€“ The behavior of the system should be written as an action.
Benefits ā€“ The benefit should be a real-world result that is non-functional or external to the system.

  • 1 Day
  • Foundation Level

User Story Mapping

A user story map helps you arrange user stories into a useful model for understanding the functionality of a system, identifying holes and omissions in your backlog, and effectively plan holistic releases that deliver value to users and business with through releases.

  • 1 Day
  • Intermediate Level

Relative Estimation Techniques

Traditionally we use to estimate efforts to develop a functionality, where in agile we estimate Business values or Complexity of a user story level. And estimate efforts in Task level. The unit of estimating user story for its value or complexity is story points, and the unit of estimating a task for its effort is Hours.

  • 1 Day
  • Foundation Level