A user story is a tool in Agile software development used to capture a description of a software feature from a user's perspective. The user story describes the type of user, what they want and why. A ...

In an earlier post, Salah wrote about applying lean development practices borrowed from the startup world to transform our Product Development group. By shifting our focus from a content-driven ...

In software development teams, it is easy to confuse software requirements with user stories. After all, both describe what the stakeholder expects from the application in terms of design, ...

Fundamentally, agile user stories are short, simple tools to document a single action or intention desired by the targeted user to achieve a goal. The simplest user stories have a format, “As a user ...

A monthly overview of things you need to know as an architect or aspiring architect. Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with ...

While no one’s disputing that automation is here to stay, whether it should infiltrate every aspect of software testing seems open to debate. My own take is that automation shouldn’t be applied ...

Some of the critical problems for any team working in an Agile way are managing the backlog of user stories, converting epics into stories, preventing scope creep, and -- most importantly -- picking ...

As near as I can tell, everyone who's doing Agile is writing requirements in the user story format of "As <role> I need to <do something> so that I can <achieve some goal>." For example, "As a ...

Struggling to get SEO recommendations implemented by developers? User stories can be a powerful tool. Here's how to write them. When you work in SEO long enough, you start noticing that the success of ...