Story BasicsThe basic thing about a real story is that it's a metaphor for the work being done. It is not a requirement but a reminder to collaborate about the topic of the story - in other words in agile development (good agile at least), the documentation is secondary to the collaboration. So the story doesn't make you agile, it's the underlying philosophy.
Examples of good stories:
Story:Generate an Emergency Department Referral
Description:As a provider, I want the option to generate an Emergency Department Referral (EDR) when I close a visit note so that I can share pertinent medical information with other IHE community members.
An IHE Community interface has been configured.
The interface can be configured to send an EDR automatically to the IHE Community.
The interface can be configured to send and EDR to an referral specialist or office staff member.
The interface can be configured to indicate who to send the EDR request.
When a user closes a visit note, provide an option on the Visit Checkout screen to generate an EDR. This option will indicate that the provider intends to create an ED Referral.
Story:Strip special characters from policy fields before creating electronic transmission claim file.
As a front desk/billing user, I would like to be able to scan insurance cards through OCR and not have to go back and edit certain fields due to dashes in the policy IDs.
In addition, I would also like this information to be formatted correctly for my electronic transmission so that I do not get claim rejections.
Provide the ability for dashes to be removed from the member ID and group ID when creating the file for electronic transmission. This process was also necessary by interfacing products to remove dashes from policy IDs to prevent rejections. Investigation may include researching how other products accomplished this task.
Also, users should be able to utilize OCR scanning without having to edit patient information manually (removing dashes).
Story:Need a way to print multiple patients on a label sheet
As a System user I would like to be able to print multiple patients on one label sheet so that I don’t have to look at multiple pages.
At least 6 patients print on one label sheet.
Critique of bad stories:
Story:Add capability to select the Welch-Allyn Exercise ECG Test
This requirement was requested during the W-A certification demo 2/17/09.
***Description doesn’t specify who or why this is important. What needs to be done? Can’t tell.
Story:Cursor should default in assign to field instead of patient field when creating a new procedure task message in FNC.
***Could be shortened to “Default cursor to assign” The rest can be in the description. Overall this may be TOO small to be a story and could be rolled into another related piece of work.
As a System user, I would like the cursor to default in the assign to field instead of the patient field when creating a new procedure task message. The patient name is already in the field since I'm creating the message, so I would prefer the cursor to default in the assign to field.
***Could shorten this to:
As a System user, the cursor will default to assign field when creating a new procedure task message so that I can be more efficient.
***missing. Can add this: