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
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.
Scrum Reference Card
Print version A Management Framework Scrum is a management framework for incremental product development using one or more cross-functional, self-organizing teams of about seven people each.
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.
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.
Glossary of instructional strategies
Current number of strategies and methods: 1271 Last updated: 27 July, 2013 Definitions written by Kelly Jo Rowan. ©1996-2013 Kelly Jo Rowan.
INVEST in Good Stories, and SMART Tasks
(French) In XP, we think of requirements of coming in the form of user stories. It would be easy to mistake the story card for the “whole story,” but Ron Jeffries points out that stories in XP have three components: Cards (their physical medium), Conversation (the discussion surrounding them), and Confirmation (tests that verify them). A pidgin language is a simplified language, usually used for trade, that allows people who can’t communicate in their native language to nonetheless work together. User stories act like this. We don’t expect customers or users to view the system the same way that programmers do; stories act as a pidgin language where both sides can agree enough to work together effectively.
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.
Syrian Journey
The Syrian conflict has torn the country apart, leaving thousands dead and driving millions to flee their homes. Many seek refuge in neighbouring countries but others pay traffickers to take them to Europe - risking death, capture and deportation. If you were fleeing Syria for Europe, what choices would you make for you and your family? Take our journey to understand the real dilemmas the refugees face. The routes, options and outcomes in this Syrian Journey feature were based on real stories uncovered by extensive research as part of a BBC Arabic digital project exploring migration from Syria.
Suggested Topics for Definition of Done Discussion
Ken Schwaber and the rest of us advocate paying attention to what “done” means for a Product Backlog Item (PBIs, or “stories”). For a lot of programmers (like me), “done” often means “It works on my workstation!” The Scrum Master is charged with advocating a “done” that includes everything else needed to build a potentially-shippable product increment. So we need a cross-functional team.
