Agile Methodologies.pdf
0 likes215 views
The document outlines Agile methodologies, focusing on two key approaches: Kanban and Scrum. It describes the principles of Agile, including customer collaboration and responsiveness to change, and provides detailed insights into the structure and roles within Scrum teams, including the roles of Product Owner and Scrum Master. Additionally, it covers practical aspects of Kanban for managing workflows and the Scrum process involving sprints, planning, and retrospective meetings.
Agile Methodologies.pdf
- 2. OUTLINE OF TOPICS Introduction to Agile Kanban Scrum Overview
- 4. Definition - agile able to move quickly and easily
- 5. Project Management- agile an approach to planning and working on projects
- 6. CUSTOMER COLLABORATION OVER Contract Negotiation Agile Manifesto WORKING PRODUCT OVER Comprehensive Documentation INDIVIDUAL INTERACTIONS OVER Processes and Tools RESPONDING TO CHANGE OVER Following a Plan
- 8. Definition - kanban A Japanese word that means "signboard"
- 9. Definition - kanban An agile method used to manage a continuous queue of work items.
- 11. Limit Work in Progress Turn work into bite sized pieces Prioritize your task Key Concepts
- 12. Limiting Work in Progress
- 13. How? Specify the minimum and/or maximum number of issues allowed in a certain Kanban Board.
- 14. Why? Better Flow Visualize and identify bottlenecks Prevents procrastination
- 16. Workspace A single account can be attached to multiple trello teams.
- 17. Boards A free Trello workspace can have a maximum of 10 boards. Board can be made manually or using templates.
- 18. Templates You can use a pre-built template for your boards.
- 19. Power Ups The additional services provided by Trello that includes integration, card sync across multiple boards, etc.
- 20. Hands On
- 22. Scrum is an agile, lightweight process that can be used to manage and control software and product development using iterative, incremental practices An empirical approach based in process control theory Intended to give the team control of its time and destiny
- 23. Agile Methods Continuous attention to technical excellence and good design Self-organizing teams Customer satisfaction by rapid, continuous delivery of useful software Working software is the principal measure of progress Delivered frequently
- 24. Scrum Process
- 25. Scrum Teams Typically 5-9 people Cross-functional: Programmers, testers, user experience designers, etc. Members should be full-time May be exceptions (e.g., database administrator) Teams are self-organizing Membership should change only between sprints
- 26. Product Owner Define the features of the product Decide on release date and content Be responsible for the profitability of the produc Prioritize features according to market value Adjust features and priority every iteration, as needed Accept or reject work results
- 27. Scrum Master Responsible for ensuring that Scrum values, practices, and rules are enacted and enforced Represents management and the team to each other Makes decisions and removes impediments Sometimes making decisions without complete information (better some decision rather than no decision) Keep the team working at the highest possible level of productivity
- 28. Sprints Scrum project makes progress in a series of Sprints Time boxed Period (2 - 4 weeks) During Sprint, the team does: Analysis Design Code Test Product is potentially releasable after every Sprint
- 29. Sprints Team selects items from the product backlog they can commit to completing Sprint backlog is created Tasks are identified and each is estimated (1 Point - 1 Day) Plan is made collaboratively, not done alone by the Scrum Master High-level design is considered
- 30. Sprint Meetings Daily Stand-up Sprint Planning Meeting Sprint Retrospective
- 31. Daily Stand-up Parameters Daily 15-minutes Stand-up Not for problem-solving Only team members, Scrum Master, product owner can talk. Helps avoid other unnecessary meetings
- 32. Sprint Planning Before the sprint Fix backlog 2 to 4 hours Story Point estimation
- 33. Sprint Retrospective After the sprint Reflection Improvement for team What went well What could be better in the next sprint
- 34. Q&A