What is a Proper Agile Iteration (Sprint)? Part 1: User Story *

How user stories are used in a proper software project?

I share my view of “Proper Agile Iteration (Sprint)” in this series:

• Part 1: User Story *

• Part 2: Testing and Coding (upcoming)

• Part 3: Done Done (upcoming)

• Part 4: Continuous Testing (upcoming)

• Part 5: Showcase (upcoming)

• Part 6: ‘Production’ Deployment (upcoming)

• Part 7: Sustained Pace (upcoming)

(I have applied the above in some client projects I led and all of my own app development, with great success)

As we all know, a User Story in Agile is a customer requirement (feature or change request).

A common mistake is managing user stories in a digital form, such as in Jira.

The image source: https://www.atlassian.com/software/jira

Some readers might object, “How can you say that? I thought digital user stories were a hallmark of Agile.” Well, that’s a misconception. Let me share quotes from two co-authors of the Agile Manifesto.