In the dark depths of the software development realm, where lines of code intertwined like cobwebs, there existed a mysterious and ancient practice known as “User Story Slicing.” This spine-tingling tale will send shivers down your code-breaking spine.
The Haunting of User Story Slicing
In the eerie world of software sorcery, every feature or method added to the solution bore a haunting secret. They all had a dual existence, a Slice by Happy vs. Unhappy Path. The “happy path” was the beacon of light, where the feature danced flawlessly through the code, like a phantom without a care in the digital night.
But beware, for in the heart of this web, a shadowy abyss known as the “unhappy path” lay in wait. It emerged when errors, exceptions, or omissions crawled out of the depths of the code crypt. It was a sinister journey filled with lurking bugs and cryptic conundrums.
Picture a chilling scenario, a standard authentication User Story for a cursed website with members-only content:
“As a member, I want to log in with my account so that I can access members-only content.”
As we dared to assume a standard login procedure, we uncovered a tale of terror, with a happy path and several sinister, “unhappy” paths.
Happy Path: 👻 “As a member, I want to log in with my account so that I can access members-only content (Happy)”
Spooky Unhappy Paths: 💀 “As a member, I want to be able to request a new password when my login fails, so that I can try to log in again (Unhappy)” 🎃 “As a new member, I need the option to register a new account so that I can access secured content (Unhappy)” 🕷️ “As a site owner, I want to block users with 3 failed login attempts in a row so I can protect the site against hackers (Unhappy)”
The unholy “unhappy path” revealed the dark omissions and exceptions lurking in our process. It was a realm where ghoulish errors could awaken at any moment.
By identifying these sinister paths, we ensured that the delivery team fully comprehended the frightful functionality demanded by the customer. The detailed and granular user stories offered a chance for more accurate Acceptance Criteria for each cursed slice. These sliced User Stories allowed the sinister product owner to prioritize functionality at a more ghostly level. For instance, in the first release, where only a handful of souls may wander, locking accounts after 3 failed logins might not be of spectral importance. The password reset feature might be deemed overkill, as an Operations or Support specter could easily reset a user’s password upon the receipt of an email plea.
And so, dear readers, stay tuned for the unveiling of six more sinister methods for slicing User Stories, as we descend deeper into the haunted labyrinth of software development. Your nightmares may never be the same again… 💀👻🕸️
Learn more in the blog post below:
https://prodataman.com/2016/09/20/slicing-user-stories-method-1/
#UserStorySlicing #SpookyCode #HauntedDevelopment #SoftwareHorror #HappyVsUnhappyPath #GhoulishFeatures
