DRAFT Governance Microconsulting Work Statement

[mjunda]

Please use this thread for feedback on the Governance Microconsulting Work Statement (MWS). Hoping for feedback by the end of this week (4/20). We are looking for input in the following areas:

1. Is the requirement scoped adequately for the micopurchase threshold?
2. Is there anything that can be added to the Definition of Done to confirm a robust product and work acceptance?
3. What would a reasonable turnaround time be for responses?
4. Are there any dependencies or additional information required in order to complete this task?
5. Any other pertinent input for this MWS.
6. Please specifically indicate in your response whether you would be interested in submitting a response to this opportunity once the Final Draft is posted. Thank you for participating!

[kaitlin]

For scoping, I would suggest that bullets 1-3 are broken out into their own solicitation from bullets 4 and 5, especially since they cover really different aspects of a governance strategy (technical vs. staffing/engagement). Bullets 4 and 5 should also be informed by the deliverables of the evangelist work statement that was posted here this week.

Drafting a data standard for all VA data (bullet 2) is out of the scope of a microconsulting engagement. Perhaps a small slice of data used across the agency is a better candidate (such as how DD-214s are represented in API endpoints versus claim data, benefits data, etc.).

For the staffing and engagement bullets (4-5), it would be good to identify some goals for the overall program, such as "5% adoption rate for software companies that service claims for states and counties". This kind of information can help inform the staff skills/size recommendations. Or alternatively, you may want to add a component to the MWS that adds identifying these targets and researching the full market as deliverables. If the Lighthouse team already has some market information or research, that would be good information to include in the MWS.

If the solicitation were de-scoped some we would be interested in submitting a response. Two weeks would be a reasonable amount of time for us to respond.

Best, Kaitlin Devine Director of Innovation Ad Hoc

[cscairns]

We're good with it as-is given the strategic level of the work, and plan to respond.

Chris Cairns and Kin Lane Skylight

[cscairns]

One suggestion does come to mind. It might be worth doing a precursor microconsulting engagement that explores the various types of API governance models being used in the private and public sectors. I think it would be informative to understand what the characteristics of those models are, who is using them, what's working and isn't working, and what the results have been.

I think you'll find some companies out there who have done and can do primary research in this area.

Furthermore, because you're requiring the microconsulting deliverables to be shared in the open, many other agencies would benefit from this research as well.

[mjunda]

Thank you @kaitlin and @cscairns! Appreciate the input.

[cosentino1]

Hello,

Yes, we feel that this is adequately scoped for the micropurchase threshold as long as it remains at the “outline” level.

It may be useful to include acceptance by 2-3 named stakeholders to the Definition of Done. This will ensure different perspectives from within VA and encourage by-in from stakeholders whose input would be beneficial during the engagement. We agree that 2 weeks would be a reasonable amount of time.

Ideally, there would be limited access provided to the DVP architect/development team to ensure that outline ties to appropriately to experienced gained through the DVP Pilot. If there are other micropruchase awardees on contract at the time, it would be useful to collaborate with them as well.

We welcome the opportunity to respond. This dovetails well with work we’re performing already for Enterprise Shared Services. Our one concern would be creating an OCI that would prohibit competing for the actual governance work in the future.

Thanks, Joe.

Sprezzatura