Happy Path Use Case Scenario
The purpose of this page is to discuss the 'Happy Path User Case Scenario' document. It is quite possibly the most important document that you will create. Please take the effort to create one! The purpose of the happy path document is to capture your company's operations in an concise and easy-to-read format. You will use this document extensively during the go live process. Here are some details that describe the happy path:
- It is an outline (bullet list)
- Every sentence begins with 'User' or 'System', for example:
- User receives call from prospect
- User creates quote
- System routes quote to manager for approval
- User ...
- It is OK to replace 'User' with the name of a Role
- It encapsulates 80% of your company's operations. If you are a larger company (say over $100M USD) or a diverse company, then you might have more than one happy path.
- It is no longer than 2 pages!! This is a very important fact. If it grows beyond two pages, the document becomes hard to user, learn, update, etc...
- The person creating the first draft may not know everything. Do your best. Your users will refine it over time. I promise!!
- You will use this document in achieving one of your first big milestones: executing your happy path in the GardenWorld sample client. Passing this milestone means you are ready to create your own client with your organization's name.
- You will tape it up in your war room and hang a pencil next to the document. Each time someone recommends a change, you tape up a new version.
- It is the base document for your corner-case user scenarios.
- This document merges your company's operational terms with iDempiere's terms
- As you start to execute your happy path in iDempiere, color code each bullet
- Green: works as expected
- Yellow: works with work around
- Red: cannot do your job
- You should be able to show your color coded happy path to your peers and they be able to very quickly derive the status of the project.
Here is an example happy path
- Sales Rep receives request for service
- Sales Rep creates lead and opportunity in system
- Sales Rep create a Request for site survey
- Site Surveyor updates Request and sends it back to Sales Rep
- Sales Rep create Quote
- Sales Rep create quote Request for approval from Sales Manager
- Sales Manager approves Request/Quote and sends Request back to Sales Rep
- Sales Rep send Quote to customer
- Customer accepts Quote
- Sales Rep send Request to Project Manager to start a new project
- Project Manager creates Project from template (copies phases and lines) - see example template here...
- Project Manager iterates on Project line items - Example
- Project Manager sends Request to Construction to get city approval to dig on site
- Construction receives approval and attaches the scanned approval to the Request
- System updates the Project Line per the status of the Request
- etc...
- Project Manager creates budget for Project and sends Request to Accounting for budget approval
- Accounting adds project budget to forecast tool.
- Accounting approves Request for budget
- Project Manager creates Replenishment for project Products
- Project Manager creates Request for Replenishment to Inventory Management
- Inventory Management approves Replenishment and converts to Purchase Orders
- Inventory Management receives Product from vendor via Material Receipt
- Inventory Management issue Material Receipt to Project WIP
- This step is repeated for all products/vendors
- Project Manager create report against all active Projects and expedites accordingly
- Project Manager creates AR Invoice to Customer
- Customer pays AR Invoice
- Accounting receives AR Receipt against AR Invoice
- Project Manager completes Project
- Accounting converts Project WIP to Fixed Asset
- Project Manager creates new support Project to maintain the Fixed Asset (tracks revenue vs support costs)
- Accounting closes month
- Accounting produces Financial Statements
- CEO gives everyone a raise