#61 – The Journalist PO

Authors’ Comments:

Who doesn’t hate clickbait? We do, that’s for sure.

But, back to the topic; The concept of User Stories originates from Extreme Programming and is the ‘agile’ way of describing requirements that are not really requirements, but our best guess on what work needs to be done. One way of making proper, understandable user stories is by using the three C’s, Card, Conversation and Confirmation.

As PST Barry Overeem describes in his 2015 Scrum.org blog post “A Common Pitfall With User Stories”, however, we need to watch out that 1) the Cards, on which the user stories are written, don’t become merely digitel tokens stored in your tool, 2) the Conversation actually happens, so the User Stories are created together instead of the PO just writing on their own, and 3) the Confirmation is aligned with the development team, PO, stakeholders, customers and dependant parties for both the Acceptance Criteria and Definition of Done. Ideally, User Stories are created by the Scrum team talking to the actual users.