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.
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.
How to Scale the Scrum Product Owner The product owner is the person in charge of the product. For products of modest complexity and small projects, it may be feasible to have one individual playing the product owner role. But how do we deal with product ownership on large Scrum projects that develop complex products?
An Overview of the Scrum Process Scrum is a simple framework that does not demand any special tools or software. Here we explain how a project typically is run using Scrum. Product Backlog Introduction to Scrum - An Agile Process Scrum is an agile way to manage a project, usually software development. Agile software development with Scrum is often perceived as a methodology; but rather than viewing Scrum as methodology, think of it as a framework for managing a process. In the agile Scrum world, instead of providing complete, detailed descriptions of how everything is to be done on a project, much of it is left up to the Scrum software development team. This is because the team will know best how to solve the problem they are presented.
Scrum (development) Scrum is an iterative and incremental agile software development framework for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal", challenges assumptions of the "traditional, sequential approach" to product development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines in the project. A key principle of Scrum is its recognition that during a project the customers can change their minds about what they want and need (often called "requirements churn"), and that unpredicted challenges cannot be easily addressed in a traditional predictive or planned manner. Later, Schwaber with others founded the Scrum Alliance and created the Certified Scrum Master programs and its derivatives. Each sprint is started by a planning meeting.
The SCRUM Blog: 5 Big Issues When Scaling Scrum I think it's a safe bet to say that if you're reading this blog then there is a good chance that you're at least interested in Scrum. The problem is that for many organizations, even the basic concepts in Scrum begin to break down as we scale it up to the entire organization. Imagine a daily stand-up when the development team consists of hundreds of developers and even more testers. These problems are not small and very often can mean the difference between a successful project or a horrific failure. So what are some of the bigger issues at hand? The Sprint Backlog - Example Sprint Task Board - International Scrum Institute Within the Sprint Backlog all activities required to complete the committed entries from the Scrum Product Backlog are stored. All entries have to be estimated on a person-hour base in order to track progress and remaining efforts. The Sprint Backlog is a living artifact and is updated on a daily base. If a team member starts to work on an activity his name is recorded within the sprint backlog.
Stop Using Story Points Sprints, standups and story points have come to symbolize Agile methods much like burgers, fries and cola symbolize fast food. Ready for your Agile Happy Meal? I hope not. Like researchers of fast food, we now know that the Agile Happy Meal contains unnatural ingredients that decrease agility and cause process indigestion. In 2007, a series of experiments led my colleagues and me to increase our agility by dropping story points and velocity calculations. Those same experiments led us to replace fixed-length sprints with a flow-based workflow, and move from standup meetings to frequent team huddles. Software Development: Agile, Team Size and Dynamics I’ve long ranted about Amazon’s 2-Pizza Team, which is defined as the following: a team where the team size is no larger than 2 pizzas can feed. Amazon realized early on that in order to cut software development time, the solution was *NOT* to put more people on the project. What is required is a team, where the roles are defined and each member has the right skill for that role, and following a lean, agile, method — all focused on the customer.
Anatomy of a Sprint Backlog At our Certified Scrum Master training classes, Platinum Edge gets a lot of requests from students for an electronic copy of our sprint backlog template. Here is an Excel version of the template, along with a quick breakdown of each part. If you are not familiar with the sprint backlog, the sprint backlog is a list of the tasks associated with the current sprint.