Agile and Scrum Introduction

Transcript

1. Agile and Scrum
2. http://agilemanifesto.org/
3. http://agilemanifesto.org/iso/sv/manifesto.html
4. Main principles Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Working software is the primary measure of progress http://agilemanifesto.org/principles.html
5. Constant change Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
6. A business oriented approach Business people and developers must work together daily throughout the project
7. A people oriented approach 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. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
8. A learning oriented approach 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. Scrum Scrum is an Agile framework for completing complex projects. Simple but not easy. Roles - ScrumMaster, Product Owner and Scrum Team Artifacts - Product Backlog, Sprint Backlog and Burndown Chart Time Boxes - Everything (especially meetings) in Scrum is timeboxed.
10. Roles - ScrumMaster - is the coach and the gatekeeper. - Product Owner - is the subject matter expert.. - Scrum Team - is the group doing the work.
11. Time Boxes - Sprint Planning Meeting - 8 hour max. - Sprint Commitment Meeting - 4 hour max. - Sprint Review Meeting - 4 hour max. - Sprint Retrospective Meeting - 3 hour max. - Daily Scrum Meeting - 15 minutes.
12. Artifacts - Product Backlog - a bucket for all the requirements. - Sprint Backlog - a subset of the Product Backlog - repository of the highest priorities deemed by the Product Owner. - Burndown Chart - a chart that indicates how much work is remaining in the Sprint - updated on a daily basis .
13. Scrum framework in 30 seconds - A product owner creates a prioritized wish list called a Product Backlog. - During Sprint Planning, the Team pulls a small chunk from the top of that wish list, a Sprint Backlog, and decides how to implement those pieces. - The Team has a certain amount of time — a Sprint (usually two to four weeks) — to complete its work, but it meets each day to assess its progress (Daily Scrum). - Along the way, the ScrumMaster keeps the team focused on its goal. - At the end of the Sprint, the work should be potentially shippable: ready to hand over to a Customer, put on a store shelf, or show to a Stakeholder. - The Sprint ends with a Sprint Review and Sprint Retrospective. - As the next Sprint begins, the Team chooses another chunk of the product backlog and begins working again (Sprint Planning).
14. Scrum framework in 30 seconds
15. Popular Choice = Scrum + XP XP supplements the Scrum process with practices like: - Automated unit testing - Refactoring - Continuous integration - Behavior Driven Design - Test Driven Development This is a great combo because it leverages the popularity of Scrum with the sound engineering practices of XP.
16. Why do we bother? Working software is the primary measure of progress