Technical Bug vs Functional Bug

The unclear boundary

bug

For developers, everything starts with a user story. He picks a ticket and works on it, until it is done. He then promote to staging environment. With a bit of chance it passes the QA gate, he then shops to production. Fortunately, there is an issue. It is not working as expected from the product owner. We don’t think that’s how users want to use the application.

Use-case

Let’s take the subscription process as an example.

1. The user see an offer that interest him.
2. He consent with general conditions
3. He initiate the subscription to open a savings account
4. He set an amount of transfer to do an initial depot
5. He validate his identity with an OTP
6. He finally sign a contract to open the account

What could go wrong? Where is the issue? Why would there an issue?

To understand what is the issue, let’s first describe what are the work items team would take on during the software development process.

The Hierarchy of work items

Themes

Well there could be many issues at every step during the subscription. If we look at the use-case, we would see that we can not have a single user story. Else it would be very big… that would be the whole project. Actually it’ a theme, or epic. We can split into features.

1. The onboarding theme : create an attractive page to display the offer, display the UGC, check if the user has already an account, invite the user to accept the chi and consent to store cookies
2. The subscription theme : get to know anything about the user (KYC), request consent to store/share the KYC. Request the amount of initial deposit, initial the transfer, validate the identification with OTP, then make sure the user sign the contract
3. Account opening theme : validation with id card or passport, check the amount reception, check/materialize the contract, check the user’s profile against conformity, create an account with an IBAN.