Making small but intentional tweaks on how you do things normally can lead to significant impact. Let’s apply this to traditional agile user stories, and watch how they transform and become more impactful.
In agile, we traditionally write user stories this way:
As a … (user or persona)
I want … (capability)
So that… (user’s goal or need)
It follows the format: User > Capability > User’s Goal or Need
Here is an example:
As a customer service representative, …
I want a shortcut that allows me to access the list of “next best” steps when I enter a specific…
When reporting a bug, it will likely get the attention it deserves IF you state the issue from the point of view of the user.
When you encounter an issue and want to report it, remember to describe the difficulty you experienced, or your inability to get a task done, or the incorrect data you got that caused your application to behave incorrectly.
Why? By describing the user experience, the dev team assessing the bug you reported can better understand the user’s pain point and the bug’s impact — and even empathize with the user.
It goes without saying that…
First of all, what is a Test Pyramid?
The Test Pyramid is an industry best practice which suggests that, when building up your test automation suite,
*(see the brief definitions of these test terms at the bottom of this article)
So you looked at your code and architecture, and you decide it’s time to refactor it or replace it with a more reliable algorithm or architecture. It’s going to be a big refactoring project, it will definitely involve big changes.
You know these updates must be done — it will make the product faster, more secure, easier to scale in future projects. There is no doubt this is the right way to go.
But one big thing worries you. How are you going to make these changes in a way that does not end up breaking your existing users? …
25+ years of hands-on experience in software, and currently the head of Quality Services org at Pegasystems.