background preloader The Home of Scrum And Your Source For Scrum Training, Assessment, And Certification - Home The Home of Scrum And Your Source For Scrum Training, Assessment, And Certification - Home

Scrum Methodology & Agile Scrum Methodologies History: The Agile Manifesto On February 11-13, 2001, at The Lodge at Snowbird ski resort in the Wasatch mountains of Utah, seventeen people met to talk, ski, relax, and try to find common groundand of course, to eat. What emerged was the Agile Software Development Manifesto. Representatives from Extreme Programming, SCRUM, DSDM, Adaptive Software Development, Crystal, Feature-Driven Development, Pragmatic Programming, and others sympathetic to the need for an alternative to documentation driven, heavyweight software development processes convened. Now, a bigger gathering of organizational anarchists would be hard to find, so what emerged from this meeting was symbolica Manifesto for Agile Software Developmentsigned by all participants. The only concern with the term agile came from Martin Fowler (a Brit for those who dont know him) who allowed that most Americans didnt know how to pronounce the word agile. Alistair Cockburns initial concerns reflected the early thoughts of many participants. ©2001 Jim Highsmith

What Is Scrum? According to the State of Agile Survey, approximately 60 percent of projects are Agile.1 After all, Agile frameworks help companies accelerate time to market, increase productivity, and respond to changes in priorities. Of all the Agile frameworks, Scrum is the most widely adopted. Professionals from around the world and in a variety of industries are using Scrum to position their teams for greater success. Join the global movement that is transforming the world of work, and bring Scrum to your workplace. To bring Scrum out of the classroom and into practice, you'll need a Certified Scrum Coach (CSC). Certified Scrum Trainers (CSTs) are licensed to teach Certified ScrumMaster® (CSM) and Certified Scrum Product Owner (CSPO) courses within your workplace environment. Scrum Alliance has developed a program for instructors and training organizations that offer certification and noncertification courses pertinent to Agile and Scrum professionals. 1 VersionOne.

Agile Alliance Scrum Master in Under 10 Minutes! - Scrum Methodology Video In Scrum, product features are known as user stories, and they are written from the perspective of the end-user. The product backlog contains the wish list of all the user stories that would make the product great. The product owner represents the users and customers of the product and decides which user stories or items make it into the product backlog. The goal of a given release is to deliver a subset of the product backlog, known as the release backlog. Each sprint (or short duration milestone) takes a manageable chunk of the release backlog and gets it to a ship-ready state! The progress of the team is monitored using a burndown chart—one of the best project visibility tools. Short daily standup meetings (also known as the Daily Scrum) ensure everything is on track and everyone has the tools they need. After each sprint, a longer sprint retrospective meeting helps fine-tune the process.

The Founding of the Agile Alliance These are my own personal recollections. I’m probably wrong about some of it. If any of the other folks involved have a clearer memory of the events, please don’t hesitate to comment. In the spring of 2000 Kent Beck called a meeting at the Rogue River Lodge near his home in Medford, Oregon. In one of the sessions we discussed the creation of an organization to drive and support the adoption of XP. Apparently I was not alone. In the meantime I contacted my friend and advisor Dave Thomas of OTI fame. Later that fall I met with Martin at a cafe in Chicago. The invitation drew an enthusiastic response from the invitees. Alistair became the de-facto organizer. The meeting was very well attended by 17 out of ~20 invitees. I kicked off the meeting with a brief introduction and an appeal to the similarities between all the various lightweight processes. Martin Fowler and Ward Cunningham quickly became the de-facto facilitators of the meeting. One of the early discussions was about a .

Learning Scrum through Games While this is the session I ran in 2011 it has been replaced by: Learning Scrum Through Games – Goldilocks Iterations II. Last week at Agile Tour Toronto I had the privilege of working with my friend Paul Heidema to help introduce the basic concepts of Scrum in 60 minutes. This is a really interesting challenge, what’s the minimum amount you can teach people and still give them a taste of Scrum. We invited our teams to create Children’s Books of the Goldilocks story. Comments from participants: A number said it was surprising how well teams of complete strangers came together after two sprints.Several didn’t like the way I set them up for a mini “failure” by not playing the Product Owner role poorly and not communicating my needs. Attached below – are our materials: Feel free to use this simple simulation to help teach the very basic concepts of Scrum. About the Author Mark is an independent Certified Scrum Trainer since 2011 and Agile coach.

Principles behind the Agile Manifesto We follow these 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. 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. 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.