Advanced Web Development in PHP - Understanding Project Development Methodologies (Scrum and Kanban)
Download as PPSX, PDF1 like479 views
The document covers advanced web development methodologies, focusing on Agile practices like Scrum and Kanban. It outlines principles of Agile software development, customer and project team rights, and key components of Scrum including roles, backlogs, and estimation techniques. Additionally, it explains the Kanban system for managing workflow and how combining Scrum with Kanban can enhance project management efficiency.
Advanced Web Development in PHP - Understanding Project Development Methodologies (Scrum and Kanban)
- 1. Advanced Web Development in PHP Module II: Understanding Project Development Methodologies (Scrum and Kanban) Rasan Samarasinghe ESOFT Computer Studies (pvt) Ltd. No 68/1, Main Street, Embilipitiya.
- 2. Contents 1. Agile Software Development 2. Agile Manifesto 3. Customerâs Bill of Rights 4. Project Teamâs Bill of Rights 5. What is Scrum? 6. Scrum Timeline 7. Team Roles in Scrum 8. Product Backlog 9. User Story 10. Release Backlog 11. Time Estimation 12. Time Estimation Techniques 13. Sprint Backlog 14. Burndown Charts 15. Daily Standups 16. Sprint Retrospectives 17. Kanban 18. Kanban Board 19. Kanban WIP Limits 20. Scrum + Kanban
- 3. Agile Software Development Agile is a time boxed, iterative approach to software delivery that builds software incrementally from the start of the project, instead of trying to deliver it all at once near the end.
- 4. Agile Manifesto by Kent Beck We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: That is, while there is value in the items on the right, we value the items on the left more. Individuals and interactions over Processes and tools Working software over Comprehensive documentation Customer collaboration over Contract negotiation Responding to change over Following a plan
- 5. Customerâs Bill of Rights by Steve McConnell I have the right: 1. To set objectives for the project and have them followed. 2. To know how long the software project will take and how much it will cost. 3. To decide which features should be included in software. 4. To make reasonable changes to requirements throughout the course of the project and to know the costs of making those changes.
- 6. Customerâs Bill of Rights by Steve McConnell 5. To know the projectâs status clearly and confidently. 6. To be apprised regularly of risks that could affect cost, schedule, or quality, and to be provided with options for addressing potential problems. 7. To have ready access to project deliverables throughout the project.
- 7. Project Teamâs Bill of Rights by Steve McConnell I have the right: 1. To know the project objectives and to clarify priorities. 2. To know in detail what product Iâm supposed to build and to clarify the product definition if it is unclear. 3. To have ready access to the customer, manager, marketer, or other person responsible for making decisions about the softwareâs functionality. 4. To work each phase of the project in a technically responsible way, especially to not be forced to start coding too early in the project.
- 8. Project Teamâs Bill of Rights by Steve McConnell 5. To approve effort and schedule estimates for any work that I will be asked to perform. This includes the right to provide only the kinds of cost and schedule estimates that are theoretically possible at each stage of the project; to take the time needed to create meaningful estimates; and to revise estimates whenever the projectâs requirements change. 6. To have my projectâs status reported accurately to customers and upper management. 7. To work in a productive environment free from frequent interruptions and distractions, especially during critical parts of the project.
- 9. What is Scrum? An iterative and incremental Agile Software Development framework for managing software projects.
- 10. Scrum Timeline
- 11. Team Roles in Scrum
- 12. Product Backlog The Product Backlog contains the wish list of all the User Stories that would make the product great.
- 13. User Story âą In Scrum, features are known as User Stories âą Written from the perspective of the end-user. âą The Product Owner, representing the users and customers of the product, decides which User Stories make it into the Product Backlog.
- 14. Release Backlog The goal of Release Backlog is to deliver a subset of the Product Backlog After identifying which User Stories will go into a particular Release, they become part of a Release Backlog.
- 15. Time Estimation Then User Stories are prioritized by the Development Team, who also estimate the amount of time involved to complete each item.
- 16. Time Estimation Techniques Hours: A simple technique is to create estimating buckets where User Stories fall into a complexity bucket. Story Points: Estimate work in comparison to the complexity of a well known but simple component.
- 17. Sprint Backlog Each Sprint takes a manageable chunk of the Release Backlog and gets it to a Ship-Ready state!
- 18. Sprint Backlog At the end of each Sprint, you should have a fully tested product with all the features of the Sprint 100% complete.
- 19. Burndown Charts The Burndown Chart provides a day-by-day measure of the amount of work that remains in a given Sprint or Release. The slope of the graph or Burndown Velocity is the average rate of productivity for each day.
- 20. Burndown Charts Knowing whether the project is on time or not early in the schedule, can help teams make the proper adjustments necessary to get the project on track.
- 21. Daily Standups Short daily standup meetings (The Daily Scrum) ensure everything is on track and everyone has the tools they need.
- 22. Daily Standups Team members list the work they have completed since the last meeting, any obstacles in their way, and what they are going to do next.
- 23. Sprint Retrospectives After each Sprint, a longer Retrospective meeting helps fine-tune the process.
- 24. Sprint Retrospectives This is a time for each team member to reflect on what went right and areas of improvement.
- 25. Kanban âą Kanban is a lean scheduling system in manufacturing emphasis on just-in-time delivery while not overloading the software developers. âą Kanban systems usually start with a board and visual cards that represent items in your product backlog.
- 26. Kanban Board On the board, you place the cards into columns that represent their current step in the workflow, ranging from âNewâ to âCompleteâ. The steps in-between are entirely up to you, so keep it simple and efficient.
- 27. Kanban Board
- 28. Kanban Board As your team keeps finishing work, those cards keep moving to the right, and more importantly, you keep delivering features to your customers.
- 29. Kanban WIP Limits Kanban Work in Progress (WIP) limits on the number of items that can live in any one workflow step at any given time.
- 31. Scrum + Kanban Scrum provides the structure for organizing feedback, short-term planning, stack ranking, an inspect-and-adapt mindset, and other organizational improvements. Kanban provides a steady flow of tasks that reach 100% completion by helping your team manage day- to-day development with a minimum of overhead and blocking issues.