Download to read offline
Uploaded byPraveen Nair
Introduction to Agile-Scrum
The document outlines a faculty development program on Scrum methodology, led by Praveen Nair, highlighting his extensive background in technology and project management. It covers agile principles, the Scrum framework, and essential practices such as sprint planning, product backlogs, and team roles, while also addressing potential challenges and available certifications. Resources for further learning and supporting tools are also provided.
More Related Content
Similar to Introduction to Agile-Scrum
More from Praveen Nair
Introduction to Agile-Scrum
- 1.
- 2. PRAVEEN NAIR Program Director,Adfolks LLC Enterprise Architecture and Program Management Formerly: Senior Manager,Technology Orion Business Innovation, Kochi Infopark Project Manager, R&D PIT Solutions |TrivandrumTechnopark Development Manager Global Media Insight | UAE
- 3. PRAVEEN NAIR MicrosoftMVPAwardee (MostValuable Professional) Certified PMI PMP (Project Management Professional) SixSigma Azure Cloud Architect Web SolutionsArchitect Business Intelligence Artificial Intelligence Product Design CriticalThinking User Experience Core Council Member – Kerala Microsoft Users Group Technology Blog: https://ninethsense.com/ LinkedIn: https://www.linkedin.com/in/ninethsense/ Twitter: @ninethsense Email: praveen@live.in
- 4. Agenda Agile Methodology– quick revision Scrum Framework Q & A
- 5.
- 6.
- 7. Agile Manifesto https://agilemanifesto.org/ Individuals andinteractions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
- 8. Agile Manifesto –12 Principles 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.
- 9.
- 10. Scrum – Processview
- 11.
- 12.
- 13. User Experience (UX)Design
- 14. Product Backlog DoR: Definitionof Ready DoD: Definition of Done
- 15.
- 16. Sprint • Timeboxed iteration.Usually 2-4 weeks • Sprint Delivery – A fully testable, demoable, working software • Usually no changes are allowed, definitely no major ones.
- 17. People Project Manager Program Manager PMO Imagesource: Danielcoding.net
- 18. ScrumTeam • Self Organized •Cross-Functional • Committed and Available • Accountable Lead Dev Jr. Dev QA BA Example:
- 19.
- 20.
- 21.
- 22.
- 23. Documentation Image source: bmc •General • SOW – Statement of Work • Business Requirements Documents • Product / Project / Software Requirements Document • High/Low Level Design Documents • Test Plans, Test Cases • User Guides, Installation Notes, Release Notes, FAQs, Build Plan • Scrum: • Product Vision • Roadmap • User Stories • Product Backlog • Retrospective • Meeting MoMs • Weekly Reports • Review Reports
- 24.
- 25. Tools Image source: bmc •Jira • Microsoft Project • Azure DevOps • Microsoft Excel / Google Sheets • SharePoint / Organization Assets • Calendar • Mail
- 26.
- 27. More Learning • Internet •LinkedIn Learning • Udemy • Training Programs by Professional Bodies • https://www.scrumalliance.org • https://www.scrum.org/
- 28. Certifications • CSM :Certified ScrumMaster by Scrum Alliance • PSM : Professional Scrum Master by Scrum.org • CSPO: Certified Scrum Product Owner • PSPO: Professional Scrum Product Owner • CSD: Certified Scrum Developer • PSD: Professional Scrum Developer • https://www.scrumalliance.org/get-certified • https://www.scrum.org/
- 29. Disadvantages Image source: bmc •No system is perfect • There is no one size fit for all • Continuous Training is necessary • Too many meetings (?) • If not managed properly, some parts can go wrong • If not monitored/audited properly, process can go wrong
- 30. ThankYou Web: https://ninethsense.com/ LinkedIn: https://www.linkedin.com/in/ninethsense/ Twitter: @ninethsense Email:praveen@live.in Phone: +91 964 588 9033
Editor's Notes
- #5 Scrum Kanban XP Crystal
- #6 My Story – project issues, customer never returns, MVP CR: Change Request Scope Creeps Over Budget Schedule Slips / Project Over Due Unhappy customers Communication Gaps
- #7 Polyglot Monolith vs Microservices SaaS, PaaS, IaaS DBaaS, AIaaS Flexibility
- #10 1986 - concept 1993 – first project 1995 – formal 2001 – agile manifesto Japanese Business Experts Framework or Scaffold, not a process Does not say ‘How’, but about ‘What’ Customize
- #11 Orchestra
- #12 Customize to fit in the organization
- #13 Orchestra
- #14 Orchestra
- #15 Orchestra
- #16 Orchestra
- #24 Teamplates
- #25 Teamplates
- #26 Teamplates
- #30 Teamplates