Skip to main content

User Stories for Dynamics 365 for Government Contractors

[COVID-19 Note: When the COVID-19 crisis took hold over the United States, I stopped blogging.  Now that we have become more accustomed to our current social distancing and have a clearer forecast of the end of the crisis, I am back.]

One of our most popular InfoStrat solutions is Dynamics 365 for Government Contractors.  At some point, most government contractors reach a point where they are no longer content to track their sales pipeline in a spreadsheet and the adopt a customer relationship management (CRM) product to manage the capture process.

Unfortunately, the most popular CRM products such as Salesforce and Microsoft Dynamics 365 do not contain the opportunity fields, capture processes or reporting that a government contractor needs. They do not reflect all the stages for a government sale such as presolicitation, request for information, request for quote, best and final offer, oral presentations, downselecting and more.

User stories which describe your sales processes are essential to determine the scope of the project and create a roadmap for an implementation.  User stories are descriptions of a process from the point of view of a user role.  They do not include technical details of the implementation but they capture business rules and data elements that are tracked for a specific scenario.

To create user stories for Dynamics 365 for Government Contractors, first identify how many capture processes you follow.  Do different programs have distinct business processes or track different data?  If they use the same processes and data, you can create fewer user stories.  Often our clients have some variation among programs which change the ways that they interact with grantees.

Here are some user stories that you are likely to need:
  1. Opportunity creation.  When do you create an opportunity and start tracking it?  Who creates opportunities?  Should any opportunities be created automatically, such as when a solicitation is posted by a customer? Is there more than one kind of opportunity that you track which requires substantially different fields and forms, such as the difference between a task order and a blanket purchase agreement?
  2. Opportunity process. What are the stages for an opportunity?  Do you have gate reviews, such as a bid/no bid meeting? Do different types of opportunities require different processes?
  3. Opportunity closing. When do you move an opportunity from Active to Closed? Which users can close an opportunity?  Do you want to automatically close opportunities based on events such as not bidding when an RFP due date passes?
  4. Project or order creation. After you win an opportunity, what do you want to happen?  Create new project codes in your timesheets? Create an order in your ERP system?  Both?
  5. Sales quotas. Do you assign sales representatives quotas?  How are territories defined?  When is quota retired?  How are option years and future contract modifications handled in terms of sales recognition?
Dynamics 365 for Government Contractors plus contains standard data elements and workflows which meet substantially all of typical government contractor requirements, but you are likely to want to customize them to match your business rules as closely as possible. 

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of such as  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Replacing Microsoft InfoPath with Power Apps

Source: Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan

Power Apps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as Power Apps Portal and shifted to the Power Apps side of the Microsoft product family. Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users. The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription." Pricing starts at $200/mo