Proposal Bid/No Bid Assessment and Checklist

Customer Name
Project Name
Employee Number of PM
Employee Number of Reviewer*
Validate
Final Inspection Report for PWB Project Id

Actual FI Done Date(dd/mm/yyyy)*

800440340

LLOYDS BANK PLC

LBG IPI Cloud Excellence TNM 2023
2374498

01/11/2023
Select Product / Items (to be filled by Project manager)
Deliverable List (Item Name; Item Type; Item Classification; Item Version No.)
Original Delivery Due Date Revised Delivery Due Date Delivery Milestone Due Date
Deliverable Name (Select from dropdown & press tab) Item Type Item Classification Item Version (dd/mm/yyyy) (dd/mm/yyyy) Planned Duration(In Days)* Size Size Unit Technology Delivery Milestone Name (dd/mm/yyyy)
1
2
3
4
5

Additional deliverables which are yet to be recorded in Ultimatix system (upto 5 items can be included)
Delivery Milestone Name
Original Delivery Due Date Revised Delivery Due Date (Select from dropdown & press Delivery Milestone Due Date
Deliverable Name *(Maximum 50 Characters) Item Type * Item Classification * Item Version * (dd/mm/yyyy) * (dd/mm/yyyy)* Planned Duration(In Days)* Size * Size Unit * Technology * tab) (dd/mm/yyyy)
1
2
3
4
5

BASELINE AUDIT CHECKLIST

Remarks
1 User Stories/ Change Requests/ Requirements are identified and baselined for the release. Items being released are as per the identified requirements and are baselined

2269
2 Any open issues/ defects/ problem reports are tracked and addressed 2270
3 Software Configuration Management (SCM) Standards and Procedures as identified in the Project Plan are complied with.
Access Control and Version Control are implemented as per plan.
2271
4 Traceability between the User Stories/ Requirements, Design, Code and Test Cases exists and can be demonstrated (as applicable) 2273

QUALITY CHECKS (For code items only)

Applicable Status Remarks
1 Static Code Quality Analysis (SCQA) tools have been used and issues resolved 2184 1
2 Static Application Security Testing (SAST) tools have been used and vulnerabilities resolved 2185 2
3 Code coverage in unit testing has been ensured as per the required criteria 2186 3
4 Code has been pair programmed or reviewed by Peer for functionality. SME review has been performed as per defined sampling criteria 2399 4
5 Code has been reviewed by Peer or SME for non-functional requirements including software security and privacy 2400 4
6 The required functional testing (Unit Testing, System Testing, Integration Testing etc.) has been performed and passed 2401 4
7 The required non-functional testing including security, performance and privacy, as applicable, has been performed and passed 2402 4

FINAL INSPECTION CHECKLIST

Remarks
1 Deliverables are adhering to SCM Standards and Procedures, Access and Version Control mechanism as applicable. 2202
2 Software Security Assurance process and Privacy by design principles have been followed. 2203
3 Sufficiency of review and testing of the deliverable(s) is checked using any applicable in-process control mechanism. 2204
4 Defects (eg., Unit Testing, NFRs, Security, Vulnerability and Pentration testing) raised in all phases have been closed. 2205
5 Any open issues / problem reports are tracked and addressed. 2206
6 All requirements are captured in a requirement document and are included in the estimation. 2207
7 Requirements document is signed-off and baselined before proceeding to the design phase. 2208
8 All the requirements are addressed in the design document. 2209
9 Design / Architecture is reviewed for non-functional attributes (eg: security, performance, usability, privacy). 2210
10 Design document is signed-off and baselined. 2211
11 Test plan covers test cases for all the requirements including NFRs, negative, boundary, exception, security and privacy (vulnerability and penetration testing).

2212
12 Test Plan is reviewed and all comments are tracked to closure. 2213
13 The project follows coding standards, including those related to software security and privacy. 2214
14 All Testing cycles are completed as per the plan. 2215
15 Testing ensures sufficient coverage. Non-functional requirements e.g. Performance, Security, Statutory and regulatory requirements, Usability, Privacy have been tested and the test results meet the
requirements defined.
2216
16 All document deliverables are available in customer approved template and reviewed by Documentation Champion. 2217
17 Ensure release readiness activities are planned and completed. 2218

RISK

1
2
3
4
5

Issue Details for Deliverables

Deliverable Name FI Checkpoint * Issue Category * Issue Description * Resolution Remarks * Resolved Date (dd/mm/yyyy) * Resolved By (Emp ID) * Verification Remarks * Verification Date (dd/mm/yyyy) *
1
2
3
4
5

FI REJECTION GUIDELINE (Delivery can be rejected based on below mentioned rejection criteria )

1 Unavailability of traceability matrix of requirements to test cases (FI Reviewer can track the traceability of a randomly chosen requirement end to end.) 2266
2 There are untested test cases as per test plan 2267
3 Test cases selected by FI Reviewer failed (It is recommended that Final Inspection Reviewer do some random testing of test cases) 2268

I have reviewed the FI Rejection Criteria to decide on approval / rejection of the item(s).*

Final Inspection Approved

Success

Page 1 of 4
 Help Content
Note: Enable Macros before modifying the sheet.
1. Enter Employee ID of FI reviewer
2. Enter the Deliverable list (Table 1 has items defined from PWB; Fill the item details in table 2 for new items)
3. Complete the baseline audit
4. Click "Validate" button to validate the sheet
5. Send the filled FI sheet to the FI reviewer through email

FI Reviewer to perform following steps:

1. Fill the FI checklist
2. Mark the Final Inspection Approved as (FI Approved = Y; FI Rejected = N)
3. Click "Validate" button to validate the sheet
4. Click on "Submit FI" button
5. Send back the FI report to the PM through email

Project Manager to perform the final steps:

1. Check the FI report
2. Click "Validate" button to validate the sheet (in case of errors, new template is to be downloaded and all above
steps are to be performed)
3. Mail the FI report to the email id ipms.fi@tcs.com
n table 2 for new items)

downloaded and all above