Class#2 – Agile Methodologies PDF

CLASS#2 – AGILE METHODOLOGIES RECAP What did we explain last session? What do we have planned for today? Any questions/difficulties about the last session? WHAT? WHY? 1. What is Agile? A set of principles for software development Emphasizes flexibility, collaboration, and customer satisfacti...

CLASS#2 – AGILE METHODOLOGIES RECAP What did we explain last session? What do we have planned for today? Any questions/difficulties about the last session? WHAT? WHY? 1. What is Agile? A set of principles for software development Emphasizes flexibility, collaboration, and customer satisfaction 2. Why Agile? Responds to change quickly Delivers functional software frequently  AGILE VALUES (MANIFESTO) https://agilemanifesto.org/principles.html (Read it) AGILE FRAMEWORKS 1. Scrum 2. Kanban 3. eXtreme Programming 4. Lean Software Development 5. Scaled Agile Framework (SaFE) 6. Spotify Model (Not a framework) 7. And more … SCRUM – WHAT DO YOU KNOW ABOUT IT? KEY PERSONAS IN SCRUM - Product Owner - Scrum Master - Dev Team (Dev/Test/UI-UX/DevOps,…) Scrum Team will be no larger than 10 people. SCRUM CEREMONIES 1. Standups 2. Sprint planning 3. Backlog refinement 4. Sprint Review 5. Retrospectives Backlog refinement  Goal Prerequis ite Delivera ble  Inspect & adapt. Improve communications Identify Goal impediments to development Highlight and promote quick decision-making. JIRA board Prerequisi Constant time and te place Team alignment Deliverab JIRA board updated le Progress towards the sprint goal STANDUPS Is it a status meeting? Can a team run a stand up without a scrum master? STANDUPS – HOW TO DO IT? - 15 mins - Ask 3 questions:  What did you do yesterday?  What will you do today?  What (if anything) is blocking your progress? Walking/Crawling/Running - IN REALITY, I’ve rarely asked these 3 questions  !  Align the Developers and the Goal Product Owner on what to build next. Team capacity Prerequisi te Backlog sized and prioritized Committed Deliverab le Scope for the new sprint SPRINT PLANNING – HOW TO DO IT? Occurs every sprint (ideally every 2 weeks) – Pre-scheduled Max 4 hours Check team capacity vs Highest Priorities User Stories Take as much stories at you can fit as per the timebox and the team capacity. Example: Sprint Planning Excel sheet  Show tangible work Goal increment to stakeholders Get feedback Team and Prerequis ite stakeholders attendance Delivera Working ble demo SPRINT REVIEW – HOW TO DO IT? Occurs end of sprint (ideally every 2 weeks) – Pre-scheduled (Can change as per stakeholder’s time availability) Ideally 1 or 1.5 hours Team members present their work. Scrum master & Product Owner facilitate to collect feedback.  Team agreement Goal on issues, improvement s, internal feedback Prerequisi te NA Actions for Deliverab le better ways of working RETROSPECTIVE – HOW TO DO IT? Too many different styles: What went bad? What Went Well? Actions to improve? Start doing, Stop doing, Continue Doing Starfish Retro ⭐ And a lot more … Sources: Miro Templates, https://www.funretrospectives.com/, … etc  Ensures backlog is Goal prioritized and updated and ready for sprints. Product Prerequis Roadmap, ite User story mapping Sized & Delivera ble Prioritized backlog BACKLOG REFINEMENT – HOW TO DO IT? As frequent as needed, with max 8 hour per sprint Ready runway of 2 sprints ahead -- Definition of ready Main responsibility of the Product Owner to keep the backlog refined, scrum master helps to facilitate. Use guiding questions: What is the desired outcome? What will you be able to do when this PBI is done? Who is this for? Who is going to use the value created by this PBI? Be specific. What value will this create? What kind of value will we get from this PBI? Check out my Defining Value in Agile article for more on this. How much effort will it take? "What problem are you trying to solve?" PRIORITIZATION METHODS (DECISION MAKING) 1. MoSCoW 2. Impact vs Effort Matrix 3. Kano model 4. Relative weighting method (custom defined criteria x score x ranking.. ) 5. RICE model (Reach, Impact, Confidence, Effort) MOSCOW METHOD MOSCO W EXAMP LE IMPACT VS EFFORT KANO MODE L ESTIMATES & SIZING Story Points 🃏 (planning Poker game) T-Shirt Sizing 👕 (Small, Medium, Large, Extra Large) Hours Estimates ⏰ Affinity Mapping* 🌍 PLANNING POKER GAME Estimate the size of building this classroom AFFINITY MAPPING EXERCISE REPORTING IN SCRUM Burn down Burn up Velocity VELOCITY 1.Estimation statistic 2.Commitment 3.Completed 4.Sprints Click icon to add picture LET’S MOVE TO KANBAN KANBAN KANBAN What is Kanban? Definition: A visual workflow management method. means ‘visual sign,’ ‘visual card,’ or ‘signboard.’ Origin: Developed by Toyota in the late 1940s to improve manufacturing efficiency. Why Kanban? Focuses on visualizing work, limiting work in progress, and optimizing flow. KANBAN PRINCIPLES Start with what you do now Agree to pursue improvement through evolutionary change Respect the current process, roles, responsibilities, and titles Encourage acts of leadership at all levels KANBAN PRACTICES 1. It is a “Pull” System 2. Visualize the workflow 3. Limit Work in Progress (WIP) 4. Manage flow 5. Make process policies explicit 6. Improve collaboratively 7. Implement feedback loops REPORTING IN KANBAN Lead time vs Cycle Time Throughput LEADTIME VS CYCLE TIME THROUGH PUT REVIEW GAME (AGILE 101) RETROSPECTIVE (FORM) What went well in today’s class? What can be done to make it better?