background preloader

Home

Home

http://www.scrumalliance.org/

Related:  Scrum

User Stories and User Story Examples by Mike Cohn What is a user story? User stories are short, simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. They typically follow a simple template: As a < type of user >, I want < some goal > so that < some reason >. Distributed Scrum Teams: Never End a Sprint on Friday Scrum team members know that things get very busy near the end of an iteration. The coding and quality activities need to be wrapped up, demo preparation occurs, the sprint review is held, the sprint retrospective is held, and the next sprint planning meeting is held. If the onsite team team prefers to end iterations on Friday, they might naturally assume they have all day Friday until evening for these activities. However, look at what that would do to a remote sub-team in India – it would mean working until early hours on Saturday morning. A better practice is to split the end of sprint activities across two days, ideally during the overlap time dedicated for sub-team synchronization.

Glossary of Scrum Terms The Sprint planning meeting is a negotiation between the team and the product owner about what the team will do during the next sprint. The product owner and all team members agree on a set of sprint goals, which is used to determine which product backlog items to commit from the uncommitted backlog to the sprint. Often new backlog items are defined during the meeting. This portion of the sprint planning meeting is time-boxed to four hours.

Agile adoption failure? You’ve got a cultural mismatch. Bob wanted to chat. “We can’t seem to make this work”, he said. “I just don’t think scrum works for a team like ours.” I had provided scrum training and a bit of coaching for his team a few months back to get them going. The Burn-Down Chart: An Effective Planning and Tracking Tool Burn-downs charts are among the most common sprint tracking mechanisms used by Agile practitioners. Though their application and usage varies (some plot a burn-down chart using story points, whereas others use task count), plotting burn-down using effort remaining is the most effective and efficient way of using burn-down charts. This article looks at creating and updating a burn-down chart using the effort-remaining approach, interpreting burn-down under different scenarios, and examining common mistakes to avoid while using burn-downs.

Your Family, Agile, and You: Using An Action Map To Make Sense Of The To Do List What do we do when we have a lot of tasks we need to complete? We write them down. So we start writing down the tasks and prioritizing them. But it doesn’t always work. 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 Before we can start to use Scrum on a project, there needs to be a Product Backlog.

Scrum Effort Estimation and Story Points Posted by admin under Scrum Basics In waterfall, managers determine a team member’s workload capacity in terms of time. That is, managers estimate how long they anticipate certain tasks will take and then assign work based on that team member’s total available time. This is problematic because it does not distinguish between a story that is very hard to complete and one that is undemanding; it only considers how long the work will take. To put it another way, coding a feature and organizing the heaps of documentation on your desk are activities that likely take the same amount of time, but there’s no question that the former would require much more sustained concentration and effort. Because of that fact, they should be recognized as incredibly different tasks, requiring different levels of effort.

The Agile Manifesto The Agile Manifesto was written in February of 2001, at a summit of seventeen independent-minded practitioners of several programming methodologies. The participants didn't agree about much, but they found consensus around four main values. Supplementing the Manifesto, the Twelve Principles further explicate what it is to be Agile. About Self Organizing Teams/ Posted 4/11/2016 12:05:46 PM by CLEMENTINO DE MENDONCA, Professional Scrum Trainer with Scrum.org A question from a budding Scrum Master, who is transitioning from a background as a traditional project manager: “In order to promote team bonding and self-organization, from now on I am going to try something new with the team. In the sprint planning meeting, instead of me breaking down the tasks for user stories between each team member, I am going to just identify tasks and hours needed and leave it at that, and then I will ask each team member to “pick” tasks from the sprint backlog on their own, and later, as soon as they complete a previously picked task.” He goes on to say: “The behavior I want to encourage is the following: 1.

Related:  Agile, Scrum2016