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

PowerApps 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 PowerApps Portal and shifted to the PowerApps 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. for 100 dail…

ScreenMeet Remote Support Tool for Dynamics 365 Customer Service

I met Lou Guercia when he was president and CEO of Scribe Software, the leading CRM integration tool.  Scribe was acquired by TIBCO Software in 2018.  I recently reconnected with Lou and learned about ScreenMeet, the company he joined as chief operating officer.   The following is a description of the product provided by ScreenMeet:

ScreenMeet is a cloud-based remote support tool designed to integrate with Dynamics 365 Customer Service. By enabling customer service and IT support organizations to address critical technical issues directly from their CRM or ticketing platform, it streamlines the process and provides a fully browser-based support experience.

You can also use ScreenMeet with other CRM products or even on its own without a CRM.

Here is a short video demo of ScreenMeet with Dynamics integration:


ScreenMeet - Cloud-based Remote Support Integrated with Dynamics 365 Customer Support Once integrated with a Dynamics 365 CS organization, the ScreenMeet widget appears on Case pa…

Microsoft PowerApps and Microsoft Flow Licensing for Beginners

NOTE: Since this post was written, Microsoft has updated pricing.  For current pricing, see https://powerapps.microsoft.com/en-us/pricing

Next month marks two years since Microsoft announced the preview of its Flow workflow automation product.  Since then, PowerApps and Microsoft Flow have been gaining in popularity.

We at InfoStrat are receiving more questions from customers on how PowerApps and Flow are licensed by Microsoft.  This is a brief overview with links to authoritative Microsoft resources with all the details.

What are PowerApps and Flow? Microsoft PowerApps is a framework derived from Dynamics 365 (formerly Dynamics CRM) that allow you to build apps either with or without a form interface.  PowerApps works with Microsoft Flow.

Microsoft Flow is is a cloud software tool to build automated workflows that connect to many Microsoft and non-Microsoft systems and services.  For instance, you could write a workflow which would create a record in Dynamics 365 whenever a new file …