<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>User-Stories on Scholion</title><link>https://scholion.thluiz.com/tags/user-stories/</link><description>Recent content in User-Stories on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Wed, 30 Sep 2026 17:41:19 +0100</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/user-stories/index.xml" rel="self" type="application/rss+xml"/><item><title>The Hardest thing about Engineering is Requirements</title><link>https://scholion.thluiz.com/notes/the-hardest-thing-about-engineering-is-requirements/</link><pubDate>Sat, 26 Mar 2022 19:52:50 -0300</pubDate><guid>https://scholion.thluiz.com/notes/the-hardest-thing-about-engineering-is-requirements/</guid><description>The post argues that requirements are hard because engineering is really a communication problem. It compares shalls, user stories, use cases, user cases, and rapid prototyping as ways to capture stakeholder intent.</description></item><item><title>6 Practical Agile Techniques You Can Start Using Today</title><link>https://scholion.thluiz.com/notes/6-practical-agile-techniques-you-can-start-using-today/</link><pubDate>Thu, 19 Jun 2014 11:15:13 -0300</pubDate><guid>https://scholion.thluiz.com/notes/6-practical-agile-techniques-you-can-start-using-today/</guid><description>The article argues for small Agile changes that improve speed, quality, and communication: deliver more often, involve testers in requirements, write user stories, use prototypes, and think about testing early.</description></item></channel></rss>