I developed this document during Phase One of the ProviderOne Project while in my role as the Senior Provider Relations Consultant at the Washington State Healthcare Authority. ProviderOne is Washington's Medicaid and social services billing and payment system. The original goal of the guide was to prepare Medicaid providers for billing the new system to ensure they receive accurate, timely payments. It is a stand alone reference guide and it can be used as classroom curriculum. This guide has evolved over the years. You can see it online today in HTML format. This version is the last one I was managing before moving to a new role on the ProviderOne project. I worked closely with project staff, multiple internal business groups, external customer focus groups, and stakeholders to complete this work over the course of a year.
I created this project planning documentation while working at the State of Washington. The goal of the project was to create an online dynamic FAQ for our customers, which were the organization's 18K+ employees. The first document defines the roles needed for project success, what each role would be responsible for producing, and the timing of those deliverables. The second document is a high level timeline. These documents were used to show sponsors what was needed for a successful outcome. I also used the role document as a strategy to engage staff. Staff who had no prior project experience felt their current workloads were not considered when leadership assigned them to the project. I had the designated staff select the role they wanted in an attempt to empower them and create ownership of those outcomes.
This is a pdf of an Excel template I created for gathering system requirements. I borrowed elements from a variety of resources. I used what I thought added the most value. I often add a requirement identifier column, sometimes several depending on the size of the project. I add filters on the priority and applicable requirement identifier columns, like "business unit".