Photo credit: Eric (CC) A common mistake made by business analysts and product owners writing requirements for agile projects is ignoring the as-is state explicit when describing the to-be state in their new user stories. To explain what I mean by this, and the negative consequences this issue carries, let’s take as an example an ... Read moreWhen writing agile requirements, pay attention to the “status quo”
↧