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.
More from: Agile Development
- Pair Programming – A Comprehensive Guide To Get You Going
- Why The Idea Of Test Driven Development (TDD) Royally Upsets Me
- 12 Basic Principles That Underlie The Agile Manifesto With Text From Original Manifesto
- 12 Practices That Make Up Extreme Programming In Agile Software Development Methodology
- 15 Agile Best Practices – Are you following these in your team?
- What is the format for writing an agile story card?
- How the Agile Teams and Organizations Mature and Become Fluent
- N-Things You Can Do With Continuous Integration Tools Hudson and Jenkins
- List of some popular agile methodologies of software development practices
- The chicken and pig cartoon for Agile Project Management – high resolution version recreated
- Why is Fibonacci series numbers used in Agile Planning and Estimations?
- What Makes An Agile Story Good? It’s the INVESTment.
- Roles and Responsibilities of Business Product Owner in Agile Teams
- 100 Plus Agile Terms – A Comprehensive List
- 15 plus best practices for continuous integration of your software
- Iterative development benefits in the Agile software development