You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 8, 2017. It is now read-only.
Jay Huie, 18F - no affiliation with Agile BPA Activities
Section of RFQ documents
Section 6.6.3 of the PWS List of Deliverables states that the Transition Plan is due; 3 business days after the conclusion of the second-to-last sprint
However, Section 6.7.1 of the PWS Transition Plan states that the Transition Plan is due; Two weeks prior to call order conclusion, provide a brief Transition Plan for all deliverables, products, and materials in coordination with the COR/ACOR, 18F Product Lead and Product Owner.
Question/Comment
If my calendar math is correct than those are not quite the same date / specification (i.e. they may be off by 3 days) and may need to be (re) aligned.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Question/Comment on e-QIP Prototype RFQ
Name and affiliation
Jay Huie, 18F - no affiliation with Agile BPA Activities
Section of RFQ documents
Section 6.6.3 of the PWS List of Deliverables states that the Transition Plan is due; 3 business days after the conclusion of the second-to-last sprint
However, Section 6.7.1 of the PWS Transition Plan states that the Transition Plan is due; Two weeks prior to call order conclusion, provide a brief Transition Plan for all deliverables, products, and materials in coordination with the COR/ACOR, 18F Product Lead and Product Owner.
Question/Comment
If my calendar math is correct than those are not quite the same date / specification (i.e. they may be off by 3 days) and may need to be (re) aligned.
The text was updated successfully, but these errors were encountered: