home

JIRA Dashboard : https://www.atlassian.com/blog/jira-software/5-steps-to-build-a-killer-dashboard

https://www.atlassian.com/blog/jira-software/7-steps-to-a-beautiful-and-useful-agile-dashboard

Project roadmap, timeline and resource constraints || Process exists to ensure right stakeholders are engaged, agreed upon project roadmap is defined, and resource pool, delivery timeline and risks are identified || Project roadmap, timeline and resource constraints || Requirement document reviewed and signed off from all major stakeholders (business, development and testing teams) || Inputs from Architrect Team || Design review template to be shared by Architecture Tech Form with Inputs from Architec team will take this up with the Team members. Additional Focus on Security Reusability Scalablity Performance techniques || Code Review Check list Code Coverage peer-review comments along with bucketing on RCA for findings Feature Demo review for business If the code does not meet the standards team has the power to take a call on release || Code Review check List Defects from DEV/QA/UAT/Prod Defect Dencity by Module per Week Security Check Llist || Test Results and Coverage Score card on Non-FRs Security Checking || Review of Test Plan, Strategy, Coverage, and Results Review of Non-FRs score card or compliance report with Security as the most important aspect Security Check list || Production Deployment Check List Details Instruction on Deployments Special Instruction Secuirty Check Rollback Plan Inputs from Code Review check list Test case report QA Signoff UAT Signoff Security Signoff || Share point location/Confluence to keep audit log, which can be referred when need for debugging the application || Number of Customer found defects New feature request || Tracking production defects and ensuring root cause analysis done on the same Assess and feed feature requests to next release’s project requirements ||
 * Stream || Development Stage || Governance Team || Governing Body Tools ||
 * BA || Business Problem || The source of problem statement
 * ^  || Requirement Gathering || Use Case and Requirements
 * Tech Forum || Architecture || Rely on Architecture Team || Inputs from Architecture Team ||
 * ^  || Design || Design guidelines
 * ^  || Implementation || List to be provided by Architect Team
 * ^  || Testing || Test Plan and Strategy
 * ^  || Documentation || Share learning with other team members || Confluence ||
 * ^  || Deployment || Deployment Instructions
 * ^  || Service / Maintenance || Ease of troubleshooting