User story is one of the popular way of writing requirement in Agile. Lot of Agilists prefer the User Story format. However, that is not the only way of writing requirements in Agile projects. You could write requirements in many ways, for e.g.Use Cases, Business Requirement Specification, BDD etc
Scrum is a framework. That means, Scrum describes the boundries and some minimal things that you need to do to create a product. What Scrum says is that you need to write requirements in a Product Backlog. Now Scrum does not tell you whether you write using User Story or a Use case or a BDD format. All that Scrum requires is that requirements be written.
Thus Scrum is non-prescriptive about writing requirements in a specific format. However, User Story still remains a very popular way of writing requirement in Scrum.
Contact Us
Blog Menu
- Agile
- Scrum
- Scaled Agile Framework®
- Real Life Scenarios
- Busting Myths Around Scrum
- Is Daily Scrum Status Meeting?
- Is Scrum Master a PM ?
- Does Sprint Backlog represent Commitment?
- Important to decide DOD at Start?
- Myths around Sprint Length
- Myths around Sprint Planning
- Is sprint Review a Sign-off Meeting?
- Myths about Cross Functionality and Self-Management
- Should we create Multiple Backlogs?
- Scrum is useful for only Small Projects?
- PO should not be invited in Sprint Retrospective
- Sprint review being the review of the developers done by PO
- Antipatterns in Scrum
- Agile Transformation
- Agile Metrics
- Agile Testing
- Product Management
- Generally Accepted Product Management Techniques
- Lean
- DevOps
- DevOps Myths
- DevOps Anti-Patterns
- Benefits of DevOps
- DevOps Culture
- DevOps Organisation Structure
- DevOps Principles
- DevOps and Software Development Process
- Automation for Effective DevOps
- DevOps and Other Methodologies and Frameworks
- Continuous Integration
- Continuous Delivery
- Deployment Pipeline
- Continuous Deployment
- Automation Testing
- Configuration Management in DevOps
- DevOps perspective of Infrastructure and Environments
- End of Service or Product Life
- DevOps Toolchain
- Amazon – AWS
- PRINCE2
- PRINCE2 Principles
- PRINCE2 Themes
- PRINCE2 Processes
- Product based Planning Technique in PRINCE2
- Tracking Business Case in PRINCE2
- Project Product Description & Product Description
- What is Risk as per PRINCE2 and How to Manage it?
- How to Embed PRINCE2 in the Organisation
- PRINCE2 Project Organisation and Scrum
- Difference Between PRINCE2® and PRINCE2 Agile®
- Tailoring PRINCE2 to suit your Project Environment
- Track Progress in a Typical PRINCE2® Project
- PRINCE2 Agile
- ITIL