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
Copy file name to clipboardExpand all lines: legal/policies-and-conditions/intersect-administration-policies/delivery-assurance-process-and-best-practice-policy.md
+14-9Lines changed: 14 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
**1. Policy title:** Delivery Assurance Process and Best Practice Policy
4
4
5
-
**2. Version:** 1.0
5
+
**2. Version:** 1.1
6
6
7
7
**3. Effective date:** 15 June 2025
8
8
@@ -12,6 +12,8 @@
12
12
13
13
**6. Policy sponsor:** Intersect Executive Director
14
14
15
+
_Updated on 15th July 2025_
16
+
15
17
***
16
18
17
19
**7. Purpose:**
@@ -44,7 +46,7 @@ This policy is founded on principles of openness, accountability, and the right
44
46
**12. Roles and responsibilities:**
45
47
46
48
***The person responsible for producing the work,** e.g. Project Lead / Technical Owner - Responsible for executing the work. They confirm via the MAF that the completed milestone accurately reflects the milestone description and meets all defined acceptance criteria.
47
-
***Third-party Assurance signature -** Responsible for the secondary verification, ensuring the milestone has been reviewed and that its delivery meets the acceptance criteria defined in the contract (examples of this are below).
49
+
***Third-party Assurance signature -** Responsible for the secondary verification, ensuring the milestone has been reviewed and that its delivery meets the acceptance criteria defined in the contract (examples of this are below).
48
50
***Intersect Delivery Assurance** - Responsible for overseeing the administrative process, ensuring adherence by both the vendor and the second attestor.
49
51
50
52
**13. Procedures:**
@@ -58,14 +60,17 @@ This policy is founded on principles of openness, accountability, and the right
58
60
***Timeline** - provide a realistic timeline that when the milestone will be completed by. Build in contingency to these dates where appropriate.
59
61
***Acceptance criteria:** Each milestone should have clear and testable acceptance criteria. These serve as the basis for milestone review and approval. Good acceptance criteria should be:
60
62
***Measurable and objective** – They can be independently verified by reviewers.
61
-
* Output-driven – Evidence of delivery should be visible and public where appropriate (eg GitHub commits, documentation, videos, working demos).
63
+
***Output-driven** – Evidence of delivery should be visible and public where appropriate (e.g. GitHub commits, documentation, videos, working demos).
62
64
***Binary** – Criteria should define whether the milestone is complete or not, leaving no room for interpretation.
63
-
***Third-party assurance:** To ensure adequate delivery assurance and oversight, each milestone is required to have a second capable vendor/person/organization who can help attest to the quality delivered and the milestone being complete. From the beneficiary’s perspective, this approach provides increased transparency to the Community and objective verification strengthening the quality of the milestone being delivered. This assurer does not need to be the same person throughout the contract if the beneficiary believes that a better person is suited to a particular milestone. Alternatively, if providing public evidence to the Community better demonstrates the milestone's achievement (eg, a Video, an X-post), this is also acceptable but the beneficiary may be asked to justify the reasoning behind this decision.\
64
-
\
65
-
**When selecting the third-party assurer, please ensure:**
66
-
* The assurance provider is genuinely independent of the delivery team, from a different company, and independent of any key stakeholders with vested interests.
67
-
* They have the necessary expertise relevant to the deliverable being assessed.
68
-
* They are independent of an Intersect Committee.
65
+
***Third-party assurance:** To ensure adequate delivery assurance and oversight, each milestone is required to have a second capable vendor/person/organization who can help attest to the quality delivered and the milestone being complete. From the beneficiary’s perspective, this approach provides increased transparency to the Community and objective verification strengthening the quality of the milestone being delivered. This assurer does not need to be the same person throughout the contract if the beneficiary believes that a better person is suited to a particular milestone. Alternatively, if providing public evidence to the Community better demonstrates the milestone's achievement (eg, a Video, an X-post), this is also acceptable but the beneficiary may be asked to justify the reasoning behind this decision.
66
+
67
+
**Please note** that **by putting "The Community" as your third party assurer**, you are committing to providing clear, understandable, public evidence that your milestone has been achieved to the Community. You should have clear feedback loops (e.g. github repository, public forum) for the Community to provide open and visible commentary on your milestone achievements, with evidence that where practically possible feedback is acted upon in a timely manner.\
68
+
\
69
+
**When selecting the third-party assurer, please ensure:**
70
+
71
+
* The assurance provider is genuinely independent of the delivery team, from a different company, and independent of any key stakeholders with vested interests.
72
+
* They have the necessary expertise relevant to the deliverable being assessed.
73
+
* They are independent of an Intersect Committee.
69
74
70
75
Intersect Delivery Assurance team will verify with the vendor that the third party assurer is acceptable and falls within these conditions.
0 commit comments