What is the format for writing an agile story card?

Although various companies and their agile teams might use their own “agile” format of story writing, a very popular and common way of agile story card writing is to follow three lines that mentions who is the user, what the user wants to do and what is the business value of doing that action or achieving that goal.

This is in sharp contrast to most of the waterfall model requirements writing where most of the time the requirements are written with System of Application in view rather the users in the view. It’s not uncommon to see those waterfall model requirements to be documented as “System shall…”.

One of the reasons behind the success of the agile model of programming is the care for the user role and the business value more than the waterfall one (despite the pros and cons of each type).

The diagram above shows a typical format of a agile story card.

Roles and Responsibilities of Business Product Owner in Agile Teams

Product owner is one of the most important roles in any agile teams. Sometimes this role is also called BPO referring to Business Product Owner. Product owner is one of the three key roles of the agile team (namely Product Owner, Scrum Master & The Team) and is a someone tasked with creating vision for the product and governing what is being released.

Here are some of the key roles a product owner typically does in an agile team.

  1. Defines the features of the product being developed by conveying or creating the vision and goals
  2. Creates and maintains the product backlog
  3. Prioritizes the features according business or market values so that they are analyzed, developed and tested according to those priorities
  4. Helps the team if any clarifications are required around the features /epics or stories.
  5. Is responsible for the profitability of the product.
  6. Is responsible for making any adjustment to the features being developed for the priority of the development every iteration as needed.
  7. Participates in the various key meetings such as Daily Scrums, Retrospectives, and probably explains the business values to the stakeholders when a Show and Tell meeting is conducted.
  8. Makes decision on acceptance or rejection of the work results
  9. Represents the customer and engages the customers or interfaces with them as required.
  10. Is responsible for communicates the project status to external stakeholders
  11. Has authority to terminate the iteration or sprint if a sudden change in direction is required.

On the fun side, also take a look at the following two great cartoons about product owner roles. (Disclaimer: The images have been borrowed under fair usage. The original author name(s) appear on the cartoon itself)

First one:

An the other one: