In Agile circles, it’s been a truism that “user stories are placeholders for a conversation.” Today, I’d argue that saying applies to pretty much anything important that gets written down.It used to be common for businesses to have a culture that accepts people issuing a written edict and assuming everyone will be able to understand exactly what’s intended. Those days are over. Leaders can’t create plans and throw them over the proverbial wall and expect desired results. Developers can’t create a product and toss it over to QA.Everything we generate—emails, requirements, strategies, user stories, and more—should be written with the assumption that a conversation will be needed to ensure our intent is understood. This is especially true if someone else needs to take action based on what we write.To read this article in full, please click her
Read More