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.

Photo by Photography Maghradze PH from Pexels

Traditional User Story Format

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…


Have you ever reported a critical bug only to see it get tossed around, and not get attended for a long period of time? Well, the bug report you created may not have made an impression.

Photo by Dastan Khdir from Pexels
Photo by Dastan Khdir from Pexels

Surprise! Even in the world of bug reporting, you need to make a good first impression. So how do you make a bug report make a good first impression? Here is a simple guideline you should always remember.

State the user experience!

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…


Photo by Designecologist from Pexels

What can the Boston 4th of July fireworks teach us about the importance of the Test Pyramid?

The Test Pyramid is an industry best practice which suggests that, when building up your test automation suite,

  • most of your tests should be unit tests*,
  • the least should be UI-based functional tests*,
  • and in between, you should have API-based functional tests*.

*(see the brief definitions of these test terms at the bottom of this article)


Photo: Pixabay (Pexels)

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? …

Mary Ann Nazario-Belarmino

25+ years of hands-on experience in software, and currently the head of Quality Services org at Pegasystems.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store