Merge pull request #90 from usds/KevinWehmuellerUSDS-patch-1

Update modifications.mdx

tech-far-hub/content/contract-administration/modifications.mdx

@@ -31,7 +31,7 @@ The FAR generally requires a new contract for any work that is considered beyond
 
 To give offerors a “reasonable anticipation” of this linkage, contracting officers can make clear in their [solicitations]( https://techfarhub.usds.gov/solicitation/contract-design/) that Agile techniques will be used. This will alert offerors that creation and refinement of technical requirements will occur post-award using a highly-disciplined process of planning, testing and customer feedback. Furthermore, the Government should alert offerors to technical constraints (e.g., platforms) that may be applicable to the effort, and that software requirement changes are expected to be refined and managed as part of agile planning. 
 
-Language such as the following could be included in the [requirements document] ]( https://techfarhub.usds.gov/pre-solicitation/requirements-development/) that explicitly states that the Government expects that it’s understanding of the problem space will evolve as a result of the agile development process, and that priorities could potentially shift based on that evolution:
+Language such as the following could be included in the [requirements document]( https://techfarhub.usds.gov/pre-solicitation/requirements-development/) that explicitly states that the Government expects that it’s understanding of the problem space will evolve as a result of the agile development process, and that priorities could potentially shift based on that evolution:
 
 As is customary in agile development, priorities (as they relate to the modernization of ABC system) may shift over time based on the natural evolution of the Government’s and contractor’s understanding of the problem space through continued discovery, user research, stakeholder engagement, and validated learning. These shifting priorities will be accounted for through collaboration between the Government (Product Owner, agency stakeholders, etc.) and the contractor to establish a shared understanding of the work, which will be planned for and communicated through standard agile practices such as product roadmapping, backlog prioritization and sprint planning. For example, XYZ agency may decide during performance that additional functionalities for ABC system may need to be added to the roadmap/backlog due to newly emerging real-time circumstances, at which time the Government would work with the contractor to plan for and prioritize that work. This process will be managed by the ABC system product owner at XYZ agency and achieved through a regularly updated product roadmap/backlog process in conjunction with the contractor team.