Best Methodology - Agile

Agile is Evolutionary methodology used in present IT industries . The limitations in the other model are addressed in this model. IT companies adopted AGILE through Agile Manifesto. In agile Manifesto we have 12 principles and 4 values. The four values are 1. Individual Interaction over processes and tools 2.Working software over comprehensive documentation. 3.customer collaboration over contract negotiation 4. Responding to change over following a plan. Scrum Team defines the project resources are grouped . Here BA,S Developers, Testers will be grouped . Here 6-8 Members will form Groups. Here we have Scrum Team, User story Workshops, Product Backlog, Sprint Backlog , Burn down charts, Sprint Meetings . User Story - Client directly interact with developers , they share their requirements in the form of user stories . They writer the user stories on post it note on story board. Here the syntax for user stories are As a i want to < what is the purpose > so that < output >. Once the developer picks up one user stories they have to submit back to client within 2 weeks that 2 weeks we called it as sprint. After the sprint client do UAT. Here in users stories we have Acceptance criteria , Business Values and Complexity Points. Acceptance criteria This area will have mandatory information that are needed in this story . Business values means how much the user stories are important to a business owner that are measure in currency notes like 10,20,50,100,200,500. There values are given by product owner . Complexity points means how complex the user stories for developing . This is measure by poker cards i.e ? 1,2,3,5,8,13,20.....100..BIG . The complexity points are defined by developers. Post UAT the user stories are moved to product backlog .In product backlog the user stories are prioritized by using MOSCOW techniques . The moving of user stories from Product back log to sprint backlog is called sprint planning. In sprint backlog we have product backlog item, tasks , wip and done. Task is nothing but unit of work done by 1 developers in 1 scrum day . In Sprint backlog the meetings will be conducted i.e Sprint Planning, Daily scrum day meeting. Sprint Review meeting, Sprint Retrospective meeting, product grooming meeting. Daily stand-up meeting or scrum day meeting defines What did you today? Tomorrow what you will work on? Any challenges (or ) When you will complete user story. Sprint review meeting once sprint is completed they will conduct . Here all the developers , stakeholders, product owner and other third parties will be part of meeting. Here they will discuss what went right, what went wrong , what are the challenges face and what are improvement areas for next sprint. Here sprint burndown charts and product burn down charts are drawn. In Sprint Retrospective Meeting Only developers will be part of meeting. They will discuss about lessons learned and what challenges faced. Once all the product backlog items are moved from wip to done stake then the shippable product component will be delivered to client. Waterfall model follows sequential methodology i.e The entire project is delivered at the end of the year or time line. In this model each phase should be completed before the next phase can begin. At the end of each phase , a review takes place to determine if the project is on the right path and whether or not to continue or discard the project. We have stages of waterfall 1.Requirement Gathering 2 Requirement Analysis 3. Design 4. Development -coding 5.Testing 6.Unit Component, system, system integration - UAT 7. Process - Configuration Management - PM 8.Deployment & Implementation 9. Release Engineers. In Requirements Gatherings the requirements are gather from stakeholder by Business analysis and Project Manager . Here BRD - Business Requirements Document will be prepared. In required Gathering BA will do stakeholder analysis , applying of elicitation Techniques, sort requirements, prioritize requirements, validating requirements. Once the requirements are collected, the BA analyses them to understand feasibility, dependencies, business rules and expected functionality. The BA works closely with the PM, Technical Architect and Database Architect. The major documents prepared are Functional Requirements Specification (FRS), System Study Document (SSD), Software Requirements Specification (SRS) and Requirements Traceability Matrix (RTM).In this stage, the technical team decides how the application will be structured, designed and connected. Solution Architects, Technical Architects, Database Architects, Network Architects and GUI Designers participate. The documents prepared include High-Level Design (HDD), Architecture Design Document (ADD), Solution Document, Low-Level Design (LDD) and Component Design Document (CDD).Development – After the design is approved, developers and programmers start writing the actual code. They develop application screens, business logic, databases and integrations. Technical Architects and Database Developers provide guidance. The major deliverables include source code, database scripts, application modules and development documentation. Testing-Before delivering the application, the testing team verifies whether all functionalities work as expected. Testers, QA Engineers, Developers and BAs participate. Testing includes Unit Testing, System Testing, System Integration Testing (SIT) and User Acceptance Testing (UAT). Documents include Test Plans, Test Scenarios, Test Cases, Defect Reports, Test Execution Reports and UAT Sign-off. The goal is to deliver a reliable application with minimum defects. Configuration Management – Controlling Every Change-Throughout development, changes to source code, documents and configurations must be properly controlled. The Project Manager, Configuration Manager and Technical Team manage this process. Documents include Configuration Management Plans, Version Control Records and Change Request Documents. Deployment – Moving the Application to Production Once testing is completed and approvals are received, Release Engineers, DevOps Engineers and Infrastructure Teams move the approved application code from the development or testing environment to the production environment. Documents include Deployment Plans, Release Notes, Installation Guides and Rollback Plans. Implementation – Making the Application Live. Implementation is the stage where the application is started for the first time in the production environment and made available for actual business operations. Release Engineers, Business Teams and Support Teams participate. Documents include Implementation Plans, User Manuals, Training Documents, Go-Live Checklists and Implementation Sign-off. Maintenance and Support- The SDLC journey does not end with the application going live. The Support Team takes responsibility for monitoring performance, resolving production issues, fixing bugs and implementing approved enhancements. Resources include Application Support Engineers, Technical Support Teams and Database Support Teams. Documents include Incident Reports, Problem Management Records, Change Requests, Maintenance Reports and Support Logs.