Presention Guidelines === ### Subject - A detailed explanation/presentation of your project - A detailed explanation/presentation of your learning for totally new tech - Learning needs handsOn or code sharing ### Audience - Only Engineers - Talk in Engineering Mainly ### Time - 30 Minutes ( 25 Minutes Talk + 5 Minutes QA) - team leaders should ask more frequently - encourage why & how cultures. good question to activate more ### Outlines/Agenda [Backend] - Business vs Technical - the goal of projects (business). -> why - tech -> how - Team Structure, Team Building - team building idea, methods. good teams solve issues quicker - Technical Architecture diagram and explanation - API design (Mock APIs Vs Real API) - Explain (Database design - ER diagram ) - Consideration [Infrastructure (Requirement and Design)] - Consideration [Design,Sequence,Process flow diagram] - Consideration (Preformance Requirement) - Consideration (Security Requirement) - Consideration (Third Party Security Testing Requirement) - Consideration (Maintenance and operation requirement) - Pro and Cons of Used framework - Pro and Cons of Used Technology - Problems You faced - Learning - Code Sharing - Engineering Demos (Mapped with Code) ### Outlines/Agenda [FrontEnd] - Business vs Technical - Team Structure, Team Building - Design Tools (Designs Confirmations with Design Team) - Mock APIs Vs Real API (Depends - If client is handling backend) - Design Patterns and explanation - External Frameworks and library used (to support the design pattern or business) - Caching Strategy etc - CI/CD (Deployment, Push to testflight) - Debugging Tool (?) - Consideration (Preformance Requirement) - Consideration (Security Requirement) - Consideration (Third Party Security Testing Requirement) - Consideration (Maintenance and operation requirement) - Analytics and Event logging - Pro and Cons of Used framework - Pro and Cons of Used Technology - Problems You faced - Learning - Code Sharing - Engineering Demos (Mapped with Code)