Problem Solving Paradigms in Software Development
3 likes859 views
This document discusses various problem solving paradigms including the Design Squiggle, Stacey Matrix, Waterfall SDLC, Agile Manifesto, Scrum Framework, Design Thinking, Lean Startup, Cynefin Framework, and Scientific Method. It provides an overview of each approach and links to additional resources. The Agile section specifically outlines the 12 principles of the Agile Manifesto and describes the Scrum framework, including roles, events, artifacts, and values.
Problem Solving Paradigms in Software Development
- 1. PROBLEM SOLVING PARADIGMS Tathagat Varma Sr. Director, Strategy & Operations, Walmart Labs Doctoral Candidate (EFPM) at ISB, Hyderabad
- 2. Agenda ■ The Design Squiggle ■ Stacey Matrix ■ Waterfall SDLC ■ Agile Manifesto ■ Scrum Framework ■ Design Thinking ■ Lean Startup ■ Cynefin Framework ■ Scientific Method!
- 8. Principles behind Agile Manifesto ■ Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. ■ Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. ■ Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. ■ Business people and developers must work together daily throughout the project. ■ Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. ■ The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. ■ Working software is the primary measure of progress. ■ Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. ■ Continuous attention to technical excellence and good design enhances agility. ■ Simplicity--the art of maximizing the amount of work not done--is essential. ■ The best architectures, requirements, and designs emerge from self-organizing teams. ■ At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. https://agilemanifesto.org/principles.html
- 10. SCRUM FRAMEWORK
- 11. SCRUM PILLARS https://medium.com/serious-scrum/empiricism-transparency-33adad8fbba2
- 12. SCRUM VALUES
- 13. SCRUM ROLES https://www.scrum.org/resources/blog/how-do-3-scrum-roles-promote-self-organization • Product Owner • DevelopmentTeam • Scrum Master
- 14. Scrum Events ■ The Sprint ■ Spring Planning ■ Daily Scrum ■ Sprint Review ■ Sprint Retrospective
- 15. Scrum Artifacts ■ Product Backlog ■ Spring Backlog ■ Increment
- 18. DESIGN THINKING
- 20. PROBLEM SOLVING