tagged: agile-requirements

What Is Quality?

Agile teams build high-quality products. Agile team members write high-quality code. Agile teams produce functionality quickly by not sacrificing quality.

Each of these is something I’ve said before. And if you haven’t said these exact things, you’ve likely...

Handling Requirements from Architects Outside the Team

I was recently asked what I thought about using the "Wise Architects" in a company to provide technical oversight to the multiple teams on a project.

A common objection to this is that the architects are outside the team and should not, therefore, have any say in how the team builds whatever it is that they are building.

This argument doesn't hold water, though, as there are…

Recommendations, Not Rules

I seem to be encountering more and more people who want to codify agile into a set of rules. I've seen this lately in authors of books, blogs or PDFs about agile or Scrum that say "You must do this" or "If you don't do this or all of that then you're not doing it right." Over the last few months I also encountered this in conversations with a few Project Management Offices…

A Requirements Challenge

I have always done highly iterative development and have always worked in short iterations. Initially this was because the domains I worked in early in my career gave me no choice but to work that way. Later I discovered the philosophical reasons for working this way. I also soon learned that keeping the software close to bug free was best. This was all back in the 1980s and…

Non-functional Requirements as User Stories

A common challenge with writing user stories is how to handle a product's non-functional requirements. These are requirements that are not about specific functionality ("As a user of a word processor, I want to insert a table into my document."), but are rather about an attribute or characteristic of the system. Examples include reliability, availability, portability,…

Writing User Stories for Back-end Systems

I was asked recently how to go about writing user stories for a back-end financial system. This is an interesting example and is a question I get asked a lot, so I thought I should answer it here. This example brings up a couple of key interesting challenges:

  • While there may be users of the system they are not often not direct users (i.e., with hands on the keyboard waiting…

Instant Access

Sign up to get Mike’s blog posts delivered right to your inbox as they publish.

Sign Up Now