Planning poker is an important part of estimating time spent on a project. But how do companies that recently went remote do planning poker? Here’s how we do planning poker for remote teams.
User stories content on the Revelry Blog: Navigate our lab notes by using the tag system.
At Revelry, we use BDD for all members of the team — and yes, that team includes our clients — so that everyone is clear about the intended user experience in the final product. Revelry’s flavor of BDD is a process for describing software features that is biased toward user’s actions and the results of those actions.
Instead of living in fear that you’re the one asking bad questions, consider that your questions will probably lead your team to deliver better outcomes.
It may be simple to use pronouns like “this, that, these, those, and they”, but Thomas Knoll says that these are ambiguous and dangerous words. And you should murder them.
Here’s a template for writing a user story that helps you imagine that you’re the user, so that you can think about how you would want to use the system. The template is a tool to prevent you from retreating back into the developer’s perspective.
Feel like your user stories are getting stale? Check out the Revelry process to write user stories that sets our team up for success!