Agile Methodology - BSIT3A Presentation PDF
Document Details
null
Group 1 BSIT-3A
Tags
Summary
This document covers Agile and Waterfall methodologies, commonly used in software development, including user stories and sprint planning. The document also provides an overview of the planning poker process. This presentation includes various terminologies, examples, and user stories related to these methodologies.
Full Transcript
Waterfall, Agile, and Hybrid Methodologies PREPARED BY GROUP 1 BSIT-3A What is Waterfall Methology Stages of Waterfall Methodology 1. Requirement Analysis All possible requirements of the system to be developed 2. System Design Provides a blueprint that gui...
Waterfall, Agile, and Hybrid Methodologies PREPARED BY GROUP 1 BSIT-3A What is Waterfall Methology Stages of Waterfall Methodology 1. Requirement Analysis All possible requirements of the system to be developed 2. System Design Provides a blueprint that guides the development process 3. Implementation / Programming The phase where the actual development or coding takes place 4. Integration and Testing Ensure the software meets the initial requirements and is free of defects 5. Deployment The software is deployed to the production environment 6. Maintenance Involves resolving any issues that arise in the production environment Advantages, Disadvantages, and When to use it Advantages Disadvantages When to use it -Uncertain and have Simplicity and Clarity difficulty in changes once a -Require specific, phase is completed extensive documentation -Have fixed, unchanging -Limited Flexibility requirement A Iterative development process Which of the following is a key characteristic of the B Flexible phase transitions Waterfall methodology? C Linear and sequential approach D Minimal documentation A Iterative development process Which of the following is a key characteristic of the B Flexible phase transitions Waterfall methodology? C Linear and sequential approach D Minimal documentation References https://www.techtarget.com/searchsoftwarequality/def inition/waterfall-model? https://www.lucidchart.com/blog/is-agile-waterfall- hybrid-right-for-your-team? https://www.youtube.com/watch?v=bNLcRdrSQAU AGILE METHODOLOGY What is AGILE Methodology? AGI L E M A N I F E S T O Lays out four core values And 12 principles that describe the processes and priorities of an agile team Working software over Individuals over processes comprehensive documentation and tools The software that Agile teams Agile teams value team develop should work. Additional collaboration and teamwork over work, like documentation, is not working independently and doing 4 pillars as important as developing good things "by the book”. software. Agile values customer input over rigid contract details, allowing AGILE Agile prioritizes flexibility, enabling teams to adapt strategies and workflows customers to guide project without disrupting the direction. project. Customer collaboration Responding to change over over contract negotiation following a plan THE 12 AGILE PRINCIPLES 1. Make customers happy through early and continuous delivery of useful software. 2. Embrace changing requirements, even in later stages. 3. Deliver work frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale. 4. Stakeholders and developers must work together daily throughout the project. 5. Build projects around motivated individuals, giving them the environment and support they need, and trusting them to get the job done. 6. Face-to-face conversations are the most effective method of communication. THE 12 AGILE PRINCIPLES 7. The main measure of progress is working software. 8.The working pace should be constant yet sustainable. 9.Pay continuous attention to technical excellence and good design. 10.Keep things as simple as possible. 11.The best results come from self-organizing teams. 12. The team reflects on how to become more effective at regular intervals, adjusting behavior accordingly. What are the benefits of the Agile development methodology? Customer Focus Adaptability Collaborative Teamwork TYPES OF AGILE METHODOLOGIES Scrum Kanban Lean Extreme Programming Adaptive Project (XP) Framework (APF) AGILE METHODOLOGIES VS. TRADITIONAL APPROACHES AGILE TRADITIONAL Iterative Linear Flexible scope Fixed scope Adaptive Rigid Continuous feedback Limited feedback Incremental Sequential AGILE IN SOFTWARE DEVELOPMENT CONCEPT RELEASE INCEPTION MAINTENANCE ITERATION RETIREMENT AGILE METHODOLOGY IN NON-SOFTWARE PROJECTS MARKETING EVENT CAMPAIGNS PLANNING PRODUCT DEVELOPMENT IMPLEMENTING AGILE METHODOLOGY Choose the Right Agile Manage Stakeholder Framework Expectations Plan the Project Assemble Your Measure Success Agile Team S T I O N WHAT IS ONE OF THE KEY BENEFITS Q UE OF THE AGILE METHODOLOGY? A) Focuses solely on long-term project goals B) Encourages strict adherence to initial plans C) Prioritizes customer feedback and adaptability D) Relies on limited communication between team members R E C T C OR R WHAT IS ONE OF THE KEY BENEFITS N S W E OF THE AGILE METHODOLOGY? A A) Focuses solely on long-term project goals B) Encourages strict adherence to initial plans C) Prioritizes customer feedback and adaptability D) Relies on limited communication between team members REFERENCES HTTPS://WWW.WRIKE.COM/PROJECT- MANAGEMENT-GUIDE/FAQ/WHAT-IS-AGILE- METHODOLOGY-IN-PROJECT-MANAGEMENT/ TTPS://ASANA.COM/RESOURCES/AGILE- METHODOLOGY 1 2 3 Reference Thank You Intro Rules Round 1 Round 2 Round 3 Final Results Let's play AGILE POKER PLANNING Intro Rules Round 1 Round 2 Round 3 Final Results Commonly used Terminologies: BACKLOG -The list of tasks or items to be completed. USER STORY -A short description of a feature from the end-user’s perspective. STORY POINTS -A unit of measure for expressing the overall effort required Intro Rules Round 1 Round 2 Round 3 Final Results Product Backlog and Sprint Backlog Intro Rules Round 1 Round 2 Round 3 Final Results Commonly used Terminologies: BACKLOG -The list of tasks or items to be completed. USER STORY -A short description of a feature from the end-user’s perspective. STORY POINTS -A unit of measure for expressing the overall effort required Intro Rules Round 1 Round 2 Round 3 Final Results STORY POINTS 1 2 3 5 8 13 20 40 100 ∞ Intro Rules Round 1 Round 2 Round 3 Final Results 3 FACTORS TO CONSIDER Risk Complexity Repetition Intro Rules Round 1 Round 2 Round 3 Final Results Commonly used Terminologies: SPRINT -A set period during which specific work has to be completed and made ready for review. VELOCITY -The amount of work a team can complete in a single sprint. Intro Rules Round 1 Round 2 Round 3 Final Results Introduction: Explain the Planning Poker process. HOW TO PLAY Present User Stories: Discuss each user story. Estimate: Team members select and reveal estimates. Discuss Estimates: Discuss differences and refine understanding. Re-Estimate: Revote if necessary. Finalize and Record: Record the agreed estimate and proceed. Review and Retrospective: Reflect on the process for improvements. Intro Rules Round 1 Round 2 Round 3 Final Results HOW TO PLAY Intro Rules Round 1 Round 2 Round 3 Final Results User Story 1: User Authentication PRODUCT BACKLOG User Story 2: Profile Picture Upload User Story 3: Advanced Reporting Dashboard Intro Rules Round 1 Round 2 Round 3 Final Results User Story 1: User Authentication THE SYSTEM SHOULD ERROR MESSAGES THE USER SHOULD BE VALIDATE THE USER'S SHOULD BE SHOWN REDIRECTED TO THEIR EMAIL AND PASSWORD FOR INCORRECT EMAIL DASHBOARD UPON AGAINST THE OR PASSWORD ENTRIES. SUCCESSFUL LOGIN. DATABASE. Intro Rules Round 1 Round 2 Round 3 Final Results User Story 2: Profile Picture Upload THE SYSTEM SHOULD THE USER CAN UPLOAD THE UPLOADED IMAGE AUTOMATICALLY AN IMAGE FILE IN SHOULD BE DISPLAYED RESIZE THE IMAGE TO JPEG, PNG, OR GIF ON THE USER'S PROFILE FIT THE PROFILE FORMAT PAGE. PICTURE DIMENSIONS Intro Rules Round 1 Round 2 Round 3 Final Results User Story 3: Advanced Reporting Dashboard THE DASHBOARD DATA SHOULD BE THE USER SHOULD BE ABLE SHOULD INCLUDE REFRESHED IN REAL- TO FILTER REPORTS BY GRAPHS, CHARTS, AND TIME WITHOUT DATE RANGE, USER TYPE, TABLES DISPLAYING NEEDING A PAGE AND OTHER RELEVANT KEY METRICS RELOAD. CRITERIA. Intro Rules Round 1 Round 2 Round 3 Final Results MAKING A PLAN/ESTIMATION User Story 1: User User Story 2: Profile User Story 3: Advanced Authentication Picture Upload Reporting Dashboard Round 1 Round 2 Round 3 Story points: ? Story points: ? Story points: ? Intro Rules Round 1 Round 2 Round 3 Final Results User Story 1: User Authentication PRODUCT BACKLOG User Story 2: Profile Picture Upload User Story 3: Advanced Reporting Dashboard Intro Rules Round 1 Round 2 Round 3 Final Results References: HTTPS://BLACKWHALEBW.COM/PRODUCT- BACKLOG-MANAGEMENT-101-KEY-PRINCIPLES- AND-BEST-PRACTICES/ HTTPS://DIGITAL.AI/GLOSSARY/COMMON-AGILE- TERMS/ HTTPS://AGILESTATIONERY.COM/PAGES/PLANNI NG-POKER Intro Rules Round 1 Round 2 Round 3 Final Results THANK YOU FOR PLAYING!