Presentation Agile 2 and on how to form teams.pptx

Agile development presentation

1. AGILE SOFTWARE ENGINEERING NAME: AKASHWARA RAMANNA STUDENT ID: 2110-21393 NAME: LAXMAN RYE NEERMAULL STUDENT ID: 2110-22956 NAME: SARAVANEN THANJAPPAN STUDENT ID: 2110_22982

2. Scrum Simulation Activity Group : AKASHWARA RAMANNA , LAXMAN RYE NEERMAULL , SARAVANEN THANJAPPAN Scrum Master: AKASHWARA RAMANNA Product Owner: LAXMAN RYE NEERMAULL Development Team: SARAVANEN THANJAPPAN

3. OBJECTIVES Form team and roles Determine project concept Create product backlog Plan sprint Daily standups Sprint review and retrospective

4. PROJECT TITLE: Web app for online food orders Goals OF THE WEB APP: User accounts Browse menu Add/remove items from cart Online payment Order tracking

5. PRODUCT BACKLOG As a customer, I want to be able to create an account so I can save my information for future orders. As a customer, I want to be able to browse the menu so I can select items to order. As a customer, I want to add items to a cart so I can place an order. As a customer, I want to specify quantities for each item in my cart so I get the right amount of each item. As a customer, I want to be able to remove items from my cart so I can update my order.

6. 6) As a customer, I want to specify delivery options so I can choose pickup or delivery. 7) As a customer, I want to be able to apply promo codes to my order so I can get discounts. 8) As a customer, I want to be able to pay online so I can quickly place my order. 9) As an employee, I want to be able to view and update order statuses so I can track order progress. 10) As a manager, I want to be able to view order reports so I can monitor sales and revenues.

7. Sprint Plan Duration OF SPRINT: 5 days The 3 main USER STORIES TO COMPLETE: As a customer, I want to be able to create an account so I can save my information for future orders. As a customer, I want to be able to browse the menu so I can select items to order. As a customer, I want to add items to a cart so I can place an order.

8. Daily Standups Day 1: AKASHWARA(Scrum MASTER): Completed database schema. LAXMAN RYE(PRODUCT OWNER): Finalized UI mockups. SARAVANEN(DEVELOPMENT TEAM): Researched APIs for payment processing. SARAVANEN(DEVELOPMENT TEAM): Set up development environment. Day 2: AKASHWARA(Scrum MASTER): Integrated user authentication. LAXMAN RYE(PRODUCT OWNER): Designed menu pages. SARAVANEN(DEVELOPMENT TEAM): Started implementation of shopping cart. SARAVANEN(DEVELOPMENT TEAM): Implemented API for retrieving menu data.

9. Day 3: AKASHWARA(Scrum MASTER): Assisted with debugging cart issues. LAXMAN RYE(PRODUCT OWNER): Created draft of promo code functionality. SARAVANEN(DEVELOPMENT TEAM): Shopping cart now adding items correctly. SARAVANEN(DEVELOPMENT TEAM): Menu API now returning data. Day 4: AKASHWARA(Scrum MASTER): Created backlog tickets for next sprint. LAXMAN RYE(PRODUCT OWNER): Started on account creation pages. SARAVANEN(DEVELOPMENT TEAM): Cart retains items across sessions. SARAVANEN(DEVELOPMENT TEAM): Menu API connected to front-end.

10. Day 5: AKASHWARA(Scrum MASTER): Planned sprint review meeting. LAXMAN RYE(PRODUCT OWNER): Account creation form accepts inputs. SARAVANEN(DEVELOPMENT TEAM): Cart fully implements add/remove items. SARAVANEN(DEVELOPMENT TEAM): Menu page displays API data.

11. Sprint Review COMPLETED STORIES: As a customer, I want to be able to create an account so I can save my information for future orders. As a customer, I want to be able to browse the menu so I can select items to order. As a customer, I want to add items to a cart so I can place an order. ALL OBJECTIVES MET.

12. Retrospective Notes The daily standup meetings enhanced team communication and enabled close collaboration throughout the sprint. Regular status updates kept all members aligned on blockers and progress. For future sprints, breaking down user stories into smaller, more manageable tasks could improve visibility into work in progress. Additional research and design spikes on complex back.

13. Summary KEY LEARNINGS: Backlog grooming - Properly grooming and prioritizing the product backlog ensures the team is working on the most valuable features first. Right-sized stories - Breaking epic stories down into smaller, manageable chunks leads to more accurate sprint planning and completion. Daily standups - Consistent daily syncing on blockers and progress is crucial for transparency and alignment. Focus over speed - Resist overloading sprints in a rush to finish. Prioritize quality over quantity.