Scrum (development): Wikis

  
  

Encyclopedia

From Wikipedia, the free encyclopedia

The Scrum process.
Software development process
Activities and steps
Requirements · Specification
Architecture · Design
Implementation · Testing
Deployment · Maintenance
Models
Agile · Cleanroom · DSDM
Iterative · RAD  · RUP  · Spiral
Waterfall · XP · Scrum  · Lean
V-Model  · FDD  · TDD
Supporting disciplines
Configuration management
Documentation
Quality assurance (SQA)
Project management
User experience design
Tools
Compiler  · Debugger  · Profiler
GUI designer
Integrated development environment
.Scrum is an iterative, incremental framework for agile software development.^ Scrum is a framework for software development.
  • From JavaOne 2009: Scrum and Team Productivity 25 September 2009 4:28 UTC www.artima.com [Source type: General]

^ What is Agile software development?
  • Agile FAQ - Serena Software - Agile On Demand 15 September 2009 2:44 UTC www.serena.com [Source type: General]

^ Agile software development is STRATEGY...

.Although the word is not an acronym, some companies implementing the process have been known to spell it with capital letters as SCRUM.^ Despite the fact that "Scrum" is not an acronym, some companies implementing the process have been known to adhere to an all capital letter expression of the word, i.e.
  • Development Process | Waterfall | Agile | RUP Process | XP Process | Scrum Process 25 September 2009 4:28 UTC www.osait.com [Source type: Reference]

^ There are several implementations of systems for managing the Scrum process which range from yellow stickers and white-boards to software packages.
  • Development Process | Waterfall | Agile | RUP Process | XP Process | Scrum Process 25 September 2009 4:28 UTC www.osait.com [Source type: Reference]

^ Here are some suggested steps to follow if you are thinking of implementing Scrum for the first time.
  • Do you know what Scrum is? Wondering if you should try Scrum on your next project? The Agile Story: Scrum meets the PMP « cPrime Blog 25 September 2009 4:28 UTC www.cprime.com [Source type: General]

.This may be due to one of Ken Schwaber’s early papers, which capitalized SCRUM in the title.^ SCRUM. This may be due to one of Ken Schwaber's early papers capitalizing SCRUM in the title.
  • Development Process | Waterfall | Agile | RUP Process | XP Process | Scrum Process 25 September 2009 4:28 UTC www.osait.com [Source type: Reference]

^ Ken Schwaber formalized the process for the worldwide software industry in the first published paper on Scrum at OOPSLA 1995 2 .
  • Our SCRUM Training Offering 25 September 2009 4:28 UTC www.mithun.nl [Source type: FILTERED WITH BAYES]

^ Ken Schwaber – Author of Agile Project Management with Scrum View more testimonials from graduates of the Certified ScrumMaster course.

[1]
.Although Scrum was intended for management of software development projects, it can be used to run software maintenance teams, or as a general project/program management approach.^ Scrum project management is LEADERSHIP...

^ Scrum is a framework for software development.
  • From JavaOne 2009: Scrum and Team Productivity 25 September 2009 4:28 UTC www.artima.com [Source type: General]

^ Although Scrum was intended to be for management of software development projects, it can be used in running software maintenance teams, or as a program management approach.
  • Development Process | Waterfall | Agile | RUP Process | XP Process | Scrum Process 25 September 2009 4:28 UTC www.osait.com [Source type: Reference]

Contents

History

.In 1986, Hirotaka Takeuchi and Ikujiro Nonaka described a new holistic approach that would increase speed and flexibility in commercial new product development.^ Scrum derives directly from the Takeuchi and Nonaka paper in the Harvard Business Review, "The New New Product Development Game."
  • Scrum Log Jeff Sutherland: Origins of Scrum 25 September 2009 4:28 UTC jeffsutherland.com [Source type: FILTERED WITH BAYES]

[2] .They compared this new holistic approach, in which the phases strongly overlap and the whole process is performed by one cross-functional team across the different phases, to rugby, where the whole team “tries to go to the distance as a unit, passing the ball back and forth”.^ The team then determines how much of this they can commit to complete during the next sprint.During the sprint, no one is able to change the sprint backlog, which means that the requirements are frozen for a sprint.
  • Development Process | Waterfall | Agile | RUP Process | XP Process | Scrum Process 25 September 2009 4:28 UTC www.osait.com [Source type: Reference]

^ Scrum derives its name from the way the ball is put back into play in a rugby match.
  • Kynetia - Scrum 25 September 2009 4:28 UTC www.kynetia.com [Source type: General]

^ And whichever tactic is chosen, he's guaranteed to upset at least two-thirds of his team as they would have done something completely different.
  • Scrum-half Guide 25 September 2009 4:28 UTC www.wesclark.com [Source type: Original source]

The case studies came from the automotive, photo machine, computer and printer industries.
.In 1991, DeGrace and Stahl, in “Wicked Problems, Righteous Solutions,”[3] referred to this approach as Scrum, a rugby term mentioned in the article by Takeuchi and Nonaka.^ Scrum approach to marketing is believed to be helpful for overcoming problems experienced by marketing executives.
  • Development Process | Waterfall | Agile | RUP Process | XP Process | Scrum Process 25 September 2009 4:28 UTC www.osait.com [Source type: Reference]

^ The term comes from rugby, where a “scrum” is used to restart the game after an event that causes play to stop.
  • Do you know what Scrum is? Wondering if you should try Scrum on your next project? The Agile Story: Scrum meets the PMP « cPrime Blog 25 September 2009 4:28 UTC www.cprime.com [Source type: General]

^ Takeuchi and Nonaka are the godfathers of Scrum and gave it the name.
  • Scrum Log Jeff Sutherland: Origins of Scrum 25 September 2009 4:28 UTC jeffsutherland.com [Source type: FILTERED WITH BAYES]

.In the early 1990s, Ken Schwaber used an approach that led to Scrum at his company, Advanced Development Methods.^ SCRUM. This may be due to one of Ken Schwaber's early papers capitalizing SCRUM in the title.
  • Development Process | Waterfall | Agile | RUP Process | XP Process | Scrum Process 25 September 2009 4:28 UTC www.osait.com [Source type: Reference]

^ An agile software development methodology developed by Ken Schwaber and Jeff Sutherland in the mid-1990s.
  • Scrum: Definition and additional resources from ZDNet 25 September 2009 4:28 UTC dictionary.zdnet.com [Source type: General]

^ Today, Scrum is one of the more well-known Agile software development frameworks in use today.
  • Do you know what Scrum is? Wondering if you should try Scrum on your next project? The Agile Story: Scrum meets the PMP « cPrime Blog 25 September 2009 4:28 UTC www.cprime.com [Source type: General]

.At the same time, Jeff Sutherland, John Scumniotales, and Jeff McKenna developed a similar approach at Easel Corporation and were the first to call it Scrum.^ Jeff Sutherland created the concept of Scrum and first applied it at Easel Corporation in 1993.
  • Camp Scrum 25 September 2009 4:28 UTC campscrum.com [Source type: General]

^ Scrum is an Agile development framework that Jeff Sutherland invented at Easel Corporation in 1993.
  • Scrum Log Jeff Sutherland: Origins of Scrum 25 September 2009 4:28 UTC jeffsutherland.com [Source type: FILTERED WITH BAYES]
  • Scrum Log Jeff Sutherland 25 September 2009 4:28 UTC jeffsutherland.com [Source type: General]

^ Scrum was developed by Jeff Sutherland, John Scumniotales, and Jeff McKenna in 1993 during their work at Easel Corporation.
  • Dr. Dobb's | Scaling Scrum | April 8, 2008 25 September 2009 4:28 UTC www.ddj.com [Source type: General]
  • Dr. Dobb's | Scaling Scrum | April 8, 2008 25 September 2009 4:28 UTC www.ddj.com [Source type: General]

[4] .In 1995 Sutherland and Schwaber jointly presented a paper describing Scrum at OOPSLA ’95 in Austin, TX, its first public appearance.^ Jeff worked with Ken Schwaber to formalize Scrum at OOPSLA'95 .
  • Scrum Log Jeff Sutherland: Origins of Scrum 25 September 2009 4:28 UTC jeffsutherland.com [Source type: FILTERED WITH BAYES]
  • Scrum Log Jeff Sutherland 25 September 2009 4:28 UTC jeffsutherland.com [Source type: General]

^ SCRUM. This may be due to one of Ken Schwaber's early papers capitalizing SCRUM in the title.
  • Development Process | Waterfall | Agile | RUP Process | XP Process | Scrum Process 25 September 2009 4:28 UTC www.osait.com [Source type: Reference]

^ Ken Schwaber formalized the process for the worldwide software industry in the first published paper on Scrum at OOPSLA 1995 2 .
  • Our SCRUM Training Offering 25 September 2009 4:28 UTC www.mithun.nl [Source type: FILTERED WITH BAYES]

.Schwaber and Sutherland collaborated during the following years to merge the above writings, their experiences, and industry best practices into what is now known as Scrum.^ Scrum was developed by Jeff Sutherland, John Scumniotales, and Jeff McKenna in 1993 during their work at Easel Corporation.
  • Dr. Dobb's | Scaling Scrum | April 8, 2008 25 September 2009 4:28 UTC www.ddj.com [Source type: General]
  • Dr. Dobb's | Scaling Scrum | April 8, 2008 25 September 2009 4:28 UTC www.ddj.com [Source type: General]

^ The answer is yes, because Scrum is a process framework and is not really comparable to the PMBOK®, which seeks to standardize project management best practices.
  • Do you know what Scrum is? Wondering if you should try Scrum on your next project? The Agile Story: Scrum meets the PMP « cPrime Blog 25 September 2009 4:28 UTC www.cprime.com [Source type: General]

^ Initially a scrum adoption model will be presented to provide an overview of where the experiences and related practices belong.
  • Scrum Log Jeff Sutherland 25 September 2009 4:28 UTC jeffsutherland.com [Source type: General]

In 2001, Schwaber teamed up with Mike Beedle to describe the method in the book “Agile Software Development with Scrum.”

Characteristics

.Scrum is a “process skeleton” which contains sets of practices and predefined roles.^ Scrum is a process skeleton that includes a set of practices and predefined roles.
  • Development Process | Waterfall | Agile | RUP Process | XP Process | Scrum Process 25 September 2009 4:28 UTC www.osait.com [Source type: Reference]

^ Scrum hangs all of it's practices on an iterative, incremental process skeleton.
  • PMRI - Project Management Research Institute 25 September 2009 4:28 UTC www.collabteam.com [Source type: FILTERED WITH BAYES]

^ The main roles in Scrum are the ScrumMaster who maintains the processes and works similarly to a project manager, the Product Owner who represents the stakeholders, and the Team which includes the developers.
  • Development Process | Waterfall | Agile | RUP Process | XP Process | Scrum Process 25 September 2009 4:28 UTC www.osait.com [Source type: Reference]

The main roles in Scrum are:
  1. the “ScrumMaster”, who maintains the processes (typically in lieu of a project manager)
  2. the “Product Owner”, who represents the stakeholders
  3. the “Team”, a cross-functional group of about 7 people who do the actual analysis, design, implementation, testing, etc.
.During each “sprint”, typically a two to four week period (with the length being decided by the team), the team creates a potentially shippable product increment (for example, working and tested software).^ Assume a sprint length of four weeks.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

^ At the end of each sprint, a working “potentially shippable” product is delivered.
  • Do you know what Scrum is? Wondering if you should try Scrum on your next project? The Agile Story: Scrum meets the PMP « cPrime Blog 25 September 2009 4:28 UTC www.cprime.com [Source type: General]

^ This document contained the defined product features in two-week sprints.
  • Let's implement SCRUM 25 September 2009 4:28 UTC www.nearsoft.com [Source type: General]

.The set of features that go into a sprint come from the product “backlog,” which is a prioritized set of high level requirements of work to be done.^ At the start of each Sprint, teams pick features from a prioritized list of customer requirements, called user stories, so that the features that are developed first are the most important according to the customer.
  • Do you know what Scrum is? Wondering if you should try Scrum on your next project? The Agile Story: Scrum meets the PMP « cPrime Blog 25 September 2009 4:28 UTC www.cprime.com [Source type: General]

^ Scrum teams work from a product backlog, a prioritized stack of requirements maintained by the "product owner" who is responsible for working closely with the team to represent the overall stakeholder community.
  • Dr. Dobb's | Scaling Scrum | April 8, 2008 25 September 2009 4:28 UTC www.ddj.com [Source type: General]
  • Dr. Dobb's | Scaling Scrum | April 8, 2008 25 September 2009 4:28 UTC www.ddj.com [Source type: General]

^ One team member is named the “scrum master”, who “ leads the Scrum meetings, identifies the initial backlog to be completed in the sprint, and empirically measures progress toward the goal of delivering this incremental set of product functionality.
  • Open Kosmaczewski - Scrum Software Development Process 15 September 2009 2:44 UTC kosmaczewski.net [Source type: FILTERED WITH BAYES]

.Which backlog items go into the sprint is determined during the sprint planning meeting.^ Prioritized assets are selected for development into sprint during the sprint planning meeting .
  • ScrumDesk - Scrum overview 25 September 2009 4:28 UTC www.scrumdesk.com [Source type: General]

^ Sprint Backlog :List of items that must be done to turn the Product Backlog into shippable items during the Sprint .
  • Scrum backlog templates and examples | Agile Software Development 25 September 2009 4:28 UTC agilesoftwaredevelopment.com [Source type: General]

^ The last day of the sprint is a day when team meet and answer three questions: What went bad during the sprint?
  • ScrumDesk - Scrum overview 25 September 2009 4:28 UTC www.scrumdesk.com [Source type: General]

.During this meeting, the Product Owner informs the team of the items in the product backlog that he or she wants completed.^ The Product Owner need not sit in for this part of the meeting, as it's more for the team.

^ Product owner will choose assets that he wants to complete.
  • ScrumDesk - Scrum overview 25 September 2009 4:28 UTC www.scrumdesk.com [Source type: General]

^ Each Sprint starts with a two to three-hour planning session that includes the customer (product owner), the facilitator (Scrummaster) and the cross-functional team.
  • Scrum: Definition and additional resources from ZDNet 25 September 2009 4:28 UTC dictionary.zdnet.com [Source type: General]

.The team then determines how much of this they can commit to complete during the next sprint.^ No commitments until next Sprint planning.
  • Scrum Development Process 25 September 2009 4:28 UTC www.fredosaurus.com [Source type: General]

^ At the beginning of each "sprint", a timebox which is suggested to be 30 calendar days but can be any length in practice, the team identifies the requirements that they will implement during that sprint and plans out how they'll do it.
  • Dr. Dobb's | Scaling Scrum | April 8, 2008 25 September 2009 4:28 UTC www.ddj.com [Source type: General]
  • Dr. Dobb's | Scaling Scrum | April 8, 2008 25 September 2009 4:28 UTC www.ddj.com [Source type: General]

^ I also like how adaptable it is - you can have a 2 man team or an 8 man team, and you can have a 2 day sprint or a 2 month sprint.
  • Abakas: Test in Process: SCRUM 25 September 2009 4:28 UTC blog.abakas.com [Source type: General]

[1] .During a sprint, no one is allowed to change the sprint backlog, which means that the requirements are frozen for that sprint.^ I understand that the Product Backlog is used to prioritize functionality, but I would think that the actual requirements of a backlog item would be completed before the Sprint Planning Meeting.

^ There is no explicit pull system within a Sprint and it's a stretch to suggest that the batch transfer at the beginning of a Sprint - the selection of the backlog - is a truly "pull" process.

^ That allows you to make changes for the next sprint.
  • From JavaOne 2009: Scrum and Team Productivity 25 September 2009 4:28 UTC www.artima.com [Source type: General]

.After a sprint is completed, the team demonstrates the use of the software.^ The team then determines how much of this they can commit to complete during the next sprint.During the sprint, no one is able to change the sprint backlog, which means that the requirements are frozen for a sprint.
  • Development Process | Waterfall | Agile | RUP Process | XP Process | Scrum Process 25 September 2009 4:28 UTC www.osait.com [Source type: Reference]

^ During each sprint, a 15-30 day period (length decided by the team), the team creates an increment of potentially shippable (usable) software.
  • Development Process | Waterfall | Agile | RUP Process | XP Process | Scrum Process 25 September 2009 4:28 UTC www.osait.com [Source type: Reference]

^ To complete this exercise, and completely get rid of MS Project, we needed to calculate the amount of hours that the team would be able to invest on each two-week sprint.
  • Let's implement SCRUM 25 September 2009 4:28 UTC www.nearsoft.com [Source type: General]

.Scrum enables the creation of self-organizing teams by encouraging co-location of all team members, and verbal communication across all team members and disciplines that are involved in the project.^ As originally developed, Scrum assumes that the project team is all working at the same location.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

^ Scrum teams work from a product backlog, a prioritized stack of requirements maintained by the "product owner" who is responsible for working closely with the team to represent the overall stakeholder community.
  • Dr. Dobb's | Scaling Scrum | April 8, 2008 25 September 2009 4:28 UTC www.ddj.com [Source type: General]
  • Dr. Dobb's | Scaling Scrum | April 8, 2008 25 September 2009 4:28 UTC www.ddj.com [Source type: General]

^ If a team member is having trouble or needs help, he can go to the scrum master who will take the time to track down the necessary resources.
  • How Two Hours Can Waste Two Weeks : programming 15 September 2009 2:44 UTC www.reddit.com [Source type: General]
  • How Two Hours Can Waste Two Weeks : programming 15 September 2009 2:44 UTC www.reddit.com [Source type: General]

.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.^ Planning new project with Scrum .
  • ScrumDesk - Scrum overview 25 September 2009 4:28 UTC www.scrumdesk.com [Source type: General]

^ At the start of each Sprint, teams pick features from a prioritized list of customer requirements, called user stories, so that the features that are developed first are the most important according to the customer.
  • Do you know what Scrum is? Wondering if you should try Scrum on your next project? The Agile Story: Scrum meets the PMP « cPrime Blog 25 September 2009 4:28 UTC www.cprime.com [Source type: General]

^ Readers I am running a project using Scrum, and I have been discovering that even though the information is to hand many readers of traditional PM and BA sites aren't familiar with the process.
  • Better Projects: The Better Projects Scrum Reading List 25 September 2009 4:28 UTC www.betterprojects.net [Source type: General]

.As such, Scrum adopts an empirical approach—accepting that the problem cannot be fully understood or defined, focusing instead on maximizing the team’s ability to deliver quickly and respond to emerging requirements.^ One team member is named the “scrum master”, who “ leads the Scrum meetings, identifies the initial backlog to be completed in the sprint, and empirically measures progress toward the goal of delivering this incremental set of product functionality.
  • Open Kosmaczewski - Scrum Software Development Process 15 September 2009 2:44 UTC kosmaczewski.net [Source type: FILTERED WITH BAYES]

^ Daily Scrum "I am looking for some approaches to shift our scrums' dynamics so the teams are owning the scrum more than me."
  • scrumdevelopment : Message: Re: Daily Scrum 25 September 2009 4:28 UTC groups.yahoo.com [Source type: General]

^ Taking the analogy to software development, Scrum is based on multiple small teams working in an intensive and interdependent manner to deliver a piece of software.
  • Do you know what Scrum is? Wondering if you should try Scrum on your next project? The Agile Story: Scrum meets the PMP « cPrime Blog 25 September 2009 4:28 UTC www.cprime.com [Source type: General]

.There are several implementations of systems for managing the Scrum process, which range from yellow stickers and whiteboards, to software packages.^ For oversight roles, we recommend Program Managers, PMO Directors and staff, and executives who are interested in improving product development by integrating the Scrum process with the business.
  • Scrum in Practice Training Course - cPrime 25 September 2009 4:28 UTC www.cprime.com [Source type: FILTERED WITH BAYES]

^ The answer is yes, because Scrum is a process framework and is not really comparable to the PMBOK®, which seeks to standardize project management best practices.
  • Do you know what Scrum is? Wondering if you should try Scrum on your next project? The Agile Story: Scrum meets the PMP « cPrime Blog 25 September 2009 4:28 UTC www.cprime.com [Source type: General]

^ The Scrum for Team System process template already provides a "Task Board" report.
  • Suggestion: Export to html/web. - Scrum for Team System 25 September 2009 4:28 UTC scrumforteamsystem.com [Source type: General]

.One of Scrum’s biggest advantages is that it is very easy to learn and requires little effort to start using.^ The link that you directed me to has information that will be very helpful to me as I begin to learn Scrum.

^ Implementing Scrum has transformed our department, from one with little credibility, to one that others all around the organisation are looking up to and seeking to follow.

^ [Liam] XQuery was slow to start using IRC, but later found it useful 19:10:52 [tantek] ooh good one Yves.
  • IRC log of tp on 2007-11-07 15 September 2009 2:44 UTC tibor.w3.org [Source type: Original source]

Roles

A number of roles are defined in Scrum. .All roles fall into two distinct groups—pigs and chickens—based on the nature of their involvement in the development process.^ All good methods are based on relevant previous experience and data plus breaking down the project into the parts.
  • CS372:Input of Project Management and Planning 15 September 2009 2:44 UTC www.csci.csusb.edu [Source type: FILTERED WITH BAYES]

^ Developers estimates stories effort size using technique called Planning Poker ® .  Development process is divided into iterations with constant duration.
  • ScrumDesk - Scrum overview 25 September 2009 4:28 UTC www.scrumdesk.com [Source type: General]

^ Today we'll look at SCRUM. How I got here: First of all, SCRUM is not a software development process.
  • Abakas: Test in Process: SCRUM 25 September 2009 4:28 UTC blog.abakas.com [Source type: General]

These groups get their names from a joke [5] about a pig and a chicken opening a restaurant:[6]
A pig and a chicken are walking down a road. The chicken looks at the pig and says, “Hey, why don’t we open a restaurant?” The pig looks back at the chicken and says, “Good idea, what do you want to call it?” The chicken thinks about it and says, “Why don’t we call it ‘Ham and Eggs’?” “I don’t think so,” says the pig, “I’d be committed, but you’d only be involved.”
.So the “pigs” are committed to building software regularly and frequently, while everyone else is a “chicken”—interested in the project but really indifferent because if it fails they’re not the pigs—that is, they weren’t the ones that committed to doing it.^ The answer is yes, because Scrum is a process framework and is not really comparable to the PMBOK®, which seeks to standardize project management best practices.
  • Do you know what Scrum is? Wondering if you should try Scrum on your next project? The Agile Story: Scrum meets the PMP « cPrime Blog 25 September 2009 4:28 UTC www.cprime.com [Source type: General]

^ That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

^ And because maintaining a comprehensive inventory of everything that needs to get done in one place, accessible by all the relevant people, we can very quickly re-calibrate to focus on what’s critical.
  • DavidCo's Robert Peake on "Getting Software Done" (part 2) | 43 Folders 15 September 2009 2:44 UTC www.43folders.com [Source type: General]

.The needs, desires, ideas and influences of the chicken roles are taken into account, but are not in any way allowed to affect, distort or get in the way of the actual Scrum project.^ Imagine gaining deep insights into the fundamentals of Scrum and Agile that could make all the difference in the world on your current project...
  • Camp Scrum 25 September 2009 4:28 UTC campscrum.com [Source type: General]

^ Blog about Scrum: Getting started, Crisis Project Management, and Transforming IT into a Lean Organization.

^ The course focuses on the practices you need to work in a Scrum project.

“Pig” roles

.The Pigs are the ones committed to the project in the Scrum process—they are the ones with “their bacon on the line” and performing the actual work of the project.^ PMOs might have to examine their charter and make modifications to work with less rigid Scrum processes.
  • Do you know what Scrum is? Wondering if you should try Scrum on your next project? The Agile Story: Scrum meets the PMP « cPrime Blog 25 September 2009 4:28 UTC www.cprime.com [Source type: General]

^ The answer is yes, because Scrum is a process framework and is not really comparable to the PMBOK®, which seeks to standardize project management best practices.
  • Do you know what Scrum is? Wondering if you should try Scrum on your next project? The Agile Story: Scrum meets the PMP « cPrime Blog 25 September 2009 4:28 UTC www.cprime.com [Source type: General]

^ The Scrum process flow is structured in cycles of work called Sprints.
  • Do you know what Scrum is? Wondering if you should try Scrum on your next project? The Agile Story: Scrum meets the PMP « cPrime Blog 25 September 2009 4:28 UTC www.cprime.com [Source type: General]

ScrumMaster (or Facilitator)
Scrum is facilitated by a ScrumMaster, whose primary job is to remove impediments to the ability of the team to deliver the sprint goal. The ScrumMaster is not the leader of the team (as the team is self-organizing) but acts as a buffer between the team and any distracting influences. The ScrumMaster ensures that the Scrum process is used as intended. The ScrumMaster is the enforcer of rules. A key part of the ScrumMaster’s role is to protect the team and keep them focused on the tasks in hand.
Team
The team has the responsibility to deliver the product. A team is typically made up of 5–9 people with cross-functional skills who do the actual work (design, develop, test, technical communication, etc.).
Product Owner
The Product Owner represents the voice of the customer. He/she ensures that the Scrum Team works with the “right things” from a business perspective. The Product Owner writes customer-centric items (typically user stories), prioritizes them and then places them in the product backlog. .A Product Owner can be a member of the Scrum Team but cannot be a ScrumMaster[7].^ Scrum Course Review Quick Poll: Does the Product Owner Participate in ...

^ We are having several issues with our scrum and > some team members are wanting to do away with it or change it to a twice > a week thing.
  • scrumdevelopment : Message: Re: Daily Scrum 25 September 2009 4:28 UTC groups.yahoo.com [Source type: General]

^ The product owner would have a prioritized backlog and the team would simply pull the top (however many) stories from it and start work.

According to original Scrum, Product Owner is in a "pig" role. However, if the Product Owner does not have involvement regularly, he/she may be considered as a "chicken" .

“Chicken” roles

.Chicken roles are not part of the actual Scrum process, but must be taken into account.^ You will learn about the history of Agile and Scrum, but will quickly move into the details of the Scrum flow and the roles of Scrum.
  • Camp Scrum 25 September 2009 4:28 UTC campscrum.com [Source type: General]

^ Not taking into account the time taken to Tweet, I believe these were the work intervals described: .
  • A Day in the Life of a Senior Designer « BioWare Blog 15 September 2009 2:44 UTC blog.bioware.com [Source type: FILTERED WITH BAYES]

^ Introduction Scrum roles Scrum meetings Scrum artifacts Scrum process flow Conclusion Resources About the author Comments Local resources .
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

They are people for whom the software is being built.
Stakeholders (customers, vendors)
These are the people who enable the project and for whom the project will produce the agreed-upon benefit[s], which justify its production. They are only directly involved in the process during the sprint reviews.
Managers
People who will set up the environment for the product development organizations.

Meetings

Daily Scrum
Each day during the sprint, a project status meeting occurs. This is called a “daily scrum”, or “the daily standup”. This meeting has specific guidelines:
  • The meeting starts precisely on time.
  • All are welcome, but only “pigs” may speak
  • The meeting is timeboxed to 15 minutes
  • The meeting should happen at the same location and same time every day
During the meeting, each team member answers three questions:.[8]
  • What have you done since yesterday?
  • What are you planning to do today?
  • Do you have any problems preventing you from accomplishing your goal?^ From planning how you get to work on time, to planning the next step in your team project, thru to sorting out a plan for a big project....
    • CS372:Project Planning and Management 15 September 2009 2:44 UTC ftp.cse.csusb.edu [Source type: FILTERED WITH BAYES]

    ^ Re: Daily Scrum Jeff, Our daily scrum script is: Scrum Master: Scot, what did you accomplish yesterday?
    • scrumdevelopment : Message: Re: Daily Scrum 25 September 2009 4:28 UTC groups.yahoo.com [Source type: General]

    ^ Tips for becoming a better programmer… What programming practice that you once liked have you since changed your mind about?
    • How not to rush yourself? - Stack Overflow 15 September 2009 2:44 UTC stackoverflow.com [Source type: General]

    (It is the role of the ScrumMaster to facilitate resolution of these impediments. .Typically this should occur outside the context of the Daily Scrum so that it may stay under 15 minutes.^ Re: Daily Scrum Scot, your script sounds like a command-and- contro scenario in which the ScrumMaster functions like a traditional PM. The problem that *may* occur with this...
    • scrumdevelopment : Message: Re: Daily Scrum 25 September 2009 4:28 UTC groups.yahoo.com [Source type: General]

    ^ Re: Daily Scrum I agree with the other comment about this sounding too C&C. The Scrummaster should kick off the daily scrum by just saying something like, "Good morning!
    • scrumdevelopment : Message: Re: Daily Scrum 25 September 2009 4:28 UTC groups.yahoo.com [Source type: General]

    )
Scrum of scrums
Each day normally after the daily scrum.
  • These meetings allow clusters of teams to discuss their work, focusing especially on areas of overlap and integration.
  • A designated person from each team attends.
The agenda will be the same as the Daily Scrum, plus the following four questions:[9]
  • What has your team done since we last met?
  • What will your team do before we meet again?
  • Is anything slowing your team down or getting in their way?
  • Are you about to put something in another team’s way?
Sprint Planning Meeting[10][11]
At the beginning of the sprint cycle (every 7–30 days), a “Sprint Planning Meeting” is held.
  • Select what work is to be done
  • Prepare the Sprint Backlog that details the time it will take to do that work, with the entire team
  • Identify and communicate how much of the work is likely to be done during the current sprint
  • Eight hour limit
At the end of a sprint cycle, two meetings are held: the “Sprint Review Meeting” and the “Sprint Retrospective
Sprint Review Meeting[12]
    .
  • Review the work that was completed and not completed
  • Present the completed work to the stakeholders (a.k.a.^ In original Scrum, the review meeting is to demonstrate the working software to the PO and stakeholders, who are then asked for their feedback.
    • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

    “the demo”)
  • Incomplete work cannot be demonstrated
  • Four hour time limit
Sprint Retrospective[13]
    .
  • All team members reflect on the past sprint
  • Make continuous process improvements
  • Two main questions are asked in the sprint retrospective: What went well during the sprint?^ In original Scrum, the PO, the team, and the Scrum master use the retrospective, or reflection, to define improvements to the process.
    • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

    ^ Allow everyone to ask questions and clarify the requirements, making notes on the Story Card.

    ^ [Nick] Nick has joined #tp 14:19:20 [raman] and people are still doing browser-specific code -- he's making it sound like that was all in the past...
    • IRC log of tp on 2007-11-07 15 September 2009 2:44 UTC tibor.w3.org [Source type: Original source]

    What could be improved in the next sprint?
  • Three hour time limit

Artifacts

Product backlog

.The product backlog is a high-level document for the entire project.^ Project Management/Scrum Project Management/Scrum/Projects Project Management/Scrum/Projects/Edit Projects Project Management/Scrum/Backlogs Project Management/Scrum/Backlogs/Draft Backlogs Project Management/Scrum/Backlogs/Opened Backlogs Project Management/Scrum/Sprint Project Management/Scrum/Sprint/Opened Sprints Project Management/Scrum/Sprint/Draft Sprints Project Management/Scrum/Sprint/Sprints Done Project Management/Scrum/Sprint/My Sprints (Product Owner) Project Management/Scrum/Sprint/My Sprints (Scrum Master) Project Management/Scrum/Sprint/My Sprints (Product Owner)/My opened sprints (Product Owner) Project Management/Scrum/Sprint/My Sprints (Scrum Master)/My opened sprints (Scrum Master) Project Management/Scrum/Scrum Meeting Project Management/Scrum/All Tasks Project Management/Scrum/All Tasks/My tasks Project Management/Scrum/All Tasks/My tasks/My opened tasks Project Management/Tasks/All Tasks/Opened tasks Views ¶ .
  • Scrum, Agile Development Method (scrum) — Documentation 25 September 2009 4:28 UTC doc.openerp.com [Source type: FILTERED WITH BAYES]

^ INHERIT scrum.project.form (form) scrum.project.tree (tree) scrum.product.backlog.tree (tree) scrum.product.backlog.form (form) scrum.sprint.tree (tree) scrum.sprint.form (form) scrum.meeting.tree (tree) Scrum Meeting (form) * INHERIT scrum.task.form (form) Objects ¶ .
  • Scrum, Agile Development Method (scrum) — Documentation 25 September 2009 4:28 UTC doc.openerp.com [Source type: FILTERED WITH BAYES]

.It contains backlog items: broad descriptions of all required features, wish-list items, etc.^ At the start of each Sprint, teams pick features from a prioritized list of customer requirements, called user stories, so that the features that are developed first are the most important according to the customer.
  • Do you know what Scrum is? Wondering if you should try Scrum on your next project? The Agile Story: Scrum meets the PMP « cPrime Blog 25 September 2009 4:28 UTC www.cprime.com [Source type: General]

^ I understand that the Product Backlog is used to prioritize functionality, but I would think that the actual requirements of a backlog item would be completed before the Sprint Planning Meeting.

^ List all the steps that will be required to finish the project, then list all the steps those steps will require to be concluded, and so on until you reach atomic items you are absolutely sure you can finish in a day or less.
  • How not to rush yourself? - Stack Overflow 15 September 2009 2:44 UTC stackoverflow.com [Source type: General]

prioritized by business value. It is the “What” that will be built. It is open and editable by anyone and contains rough estimates of both business value and development effort. Those estimates help the Product Owner to gauge the timeline and, to a limited extent, priority. .For example, if the “add spellcheck” and “add table support” features have the same business value, the one with the smallest development effort will probably have higher priority, because the ROI (Return On Investment) is higher.^ For example, for most of my career (mostly as a developer then project lead), I was at one company, on one team.

.The product backlog is the property of the Product Owner.^ Project Management/Scrum Project Management/Scrum/Projects Project Management/Scrum/Projects/Edit Projects Project Management/Scrum/Backlogs Project Management/Scrum/Backlogs/Draft Backlogs Project Management/Scrum/Backlogs/Opened Backlogs Project Management/Scrum/Sprint Project Management/Scrum/Sprint/Opened Sprints Project Management/Scrum/Sprint/Draft Sprints Project Management/Scrum/Sprint/Sprints Done Project Management/Scrum/Sprint/My Sprints (Product Owner) Project Management/Scrum/Sprint/My Sprints (Scrum Master) Project Management/Scrum/Sprint/My Sprints (Product Owner)/My opened sprints (Product Owner) Project Management/Scrum/Sprint/My Sprints (Scrum Master)/My opened sprints (Scrum Master) Project Management/Scrum/Scrum Meeting Project Management/Scrum/All Tasks Project Management/Scrum/All Tasks/My tasks Project Management/Scrum/All Tasks/My tasks/My opened tasks Project Management/Tasks/All Tasks/Opened tasks Views ¶ .
  • Scrum, Agile Development Method (scrum) — Documentation 25 September 2009 4:28 UTC doc.openerp.com [Source type: FILTERED WITH BAYES]

.Business value is set by the Product Owner.^ Have the Product Owner, product manager, business analyst or whoever is appropriate in your organisation, prepare the target User Stories for the next Sprint prior to Sprint Planning.

Development effort is set by the Team.

Sprint backlog

.The sprint backlog is a document containing information about how the team is going to implement the features for the upcoming sprint.^ Your team will go hyperproductive in three sprints and stay that way until or unless the men in black take you down.
  • Scrum Log Jeff Sutherland 25 September 2009 4:28 UTC jeffsutherland.com [Source type: General]

^ Contains subtasks for the user stories, use cases, and tasks to implement in the next sprint.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

^ See other entries about: How To Implement Scrum in 10 Easy Steps , Most Read , Scrum Newer Post Older Post Home 19 comments: .

.Features are broken down into tasks; as a best practice, tasks are normally estimated between four and sixteen hours of work.^ Always break down a complex piece of work into simpler steps.
  • CS372:Project Planning and Management 15 September 2009 2:44 UTC ftp.cse.csusb.edu [Source type: FILTERED WITH BAYES]

^ I've found that I get overwhelmed with project/feature ideas at times and it really helps to write everything down and file it for a later time when I have the resources available to work effectively.
  • How not to rush yourself? - Stack Overflow 15 September 2009 2:44 UTC stackoverflow.com [Source type: General]

^ [KevinLawver] There is also a HUGE difference between: the standard, the implementations, and then the best practices.
  • IRC log of tp on 2007-11-07 15 September 2009 2:44 UTC tibor.w3.org [Source type: Original source]

.With this level of detail the whole team understands exactly what to do, and anyone can potentially pick a task from the list.^ At the start of each Sprint, teams pick features from a prioritized list of customer requirements, called user stories, so that the features that are developed first are the most important according to the customer.
  • Do you know what Scrum is? Wondering if you should try Scrum on your next project? The Agile Story: Scrum meets the PMP « cPrime Blog 25 September 2009 4:28 UTC www.cprime.com [Source type: General]

^ Have someone who understands the requirements for the User Story present it to the team (whole team).

.Tasks on the sprint backlog are never assigned; rather, tasks are signed up for by the team members as needed, according to the set priority and the team member skills.^ I have set up and managed Test teams.

^ Step #2: How to estimate your product backlog - Step #3: Sprint Planning/clarify requirements - Step #4: Sprint Planning/estimate tasks - Step #5: Create a collaborative workspace - Step #6: Sprint!

^ The goal of the call is to end up with a sprint backlog with work items that both the collocated and the remote group have committed to.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

The sprint backlog is the property of the Team. Estimations are set by the Team. Often an according Task Board is used to see and change the state of the tasks of the current sprint, like “to do”, “in progress” and “done”.

Burn down

.The sprint burn down chart is a publicly displayed chart showing remaining work in the sprint backlog.^ Update the sprint backlog to show only these work items.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

^ The goal of the call is to end up with a sprint backlog with work items that both the collocated and the remote group have committed to.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

^ After the planning meeting, the collocated group and the remote test group start working on the same user story (or use case, or another task) of the sprint backlog.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

Updated every day, it gives a simple view of the sprint progress. It also provides quick visualizations for reference. .There are also other types of burndown, for example the Release Burndown Chart that shows the amount of work left to complete the target commitment for a Product Release (normally spanning through multiple iterations) and the Alternative Release Burndown Chart[14], which basically does the same, but clearly shows scope changes to Release Content, by resetting the baseline.^ The Burndown Chart is here and it is a nice one that shows the flow of stories from state to state.
  • Scrum Log Jeff Sutherland 25 September 2009 4:28 UTC jeffsutherland.com [Source type: General]

^ He served as the Technical Lead for the Ames Educational Technology Team (AETT) producing engaging interactive NASA educational products spanning grades K through college.
  • Unlocking Collaboration 15 September 2009 2:44 UTC www.slideshare.net [Source type: FILTERED WITH BAYES]

^ Work out what steps must be complete before other steps can start.
  • CS372:Project Planning and Management 15 September 2009 2:44 UTC ftp.cse.csusb.edu [Source type: FILTERED WITH BAYES]
  • CS372:Input of Project Management and Planning 15 September 2009 2:44 UTC www.csci.csusb.edu [Source type: FILTERED WITH BAYES]

It should not be confused with an earned value chart.

Adaptive project management

The following are some general practices of Scrum:
  • —“Working more hours” does not necessarily mean “producing more output.”

Terminology

The following terminology is used in Scrum:[15]

Roles

Product Owner
The person responsible for maintaining the Product Backlog by representing the interests of the stakeholders.
ScrumMaster
The person responsible for the Scrum process, making sure it is used correctly and maximizes its benefits.
Team
A cross-functional group of people responsible for managing itself to develop the product.
Scrum Team
Product Owner, ScrumMaster and Team

Artifacts

Sprint burn down chart
Daily progress for a Sprint over the sprint’s length.
Product backlog
A prioritized list of high level requirements.
Sprint backlog
A prioritized list of tasks to be completed during the sprint.

Others

Impediment
Anything that prevents a team member from performing work as efficiently as possible.
Sprint
A time period (typically 2–4 weeks) in which development occurs on a set of backlog items that the Team has committed to.
Sashimi
A slice of the whole equivalent in context to all other slices of the whole. For the Daily Scrum constant. It can also be established on a sprint-by-sprint basis, using commitment-based planning.
Abnormal Termination
The team can cancel a Sprint if they feel they are unable to meet the Sprint Goal. Management can cancel a Sprint if external circumstances negate the value of the Sprint Goal. If a Sprint is abnormally terminated, the next step is to conduct a new Sprint planning meeting, where the reason for the termination is reviewed.

Scrum modifications

Scrum-ban

Scrum-ban is a software production model based on Scrum and Kanban. .Scrum-ban is especially suited for maintenance projects or (system) projects with frequent and unexpected user stories or programming errors.^ As well as reading the posts I've written about User Stories, read this Implementing Scrum series.

^ May 2008 07:42 Hi Shawn Combining User Stories from eXtreme Programming with Scrum works really well.

^ Larry Dignan Blog posts 2009-08-18 Sprintometer 3.0 (Windows) Sprintometer is a simple tool with modern GUI for SCRUM and Extreme Programming projects' tracking.
  • Scrum Resources | ZDNet 25 September 2009 4:28 UTC updates.zdnet.com [Source type: General]
  • Scrum: Definition and additional resources from ZDNet 25 September 2009 4:28 UTC dictionary.zdnet.com [Source type: General]

.In such cases the time-limited sprints of the Scrum model are of no appreciable use, but Scrum’s daily meetings and other practices can be applied, depending on the team and the situation at hand.^ It combines an iterative approach to development with other useful practices, including special meetings, a definition of roles, and specification of the artifacts.
  • Scrum Resources | ZDNet 25 September 2009 4:28 UTC updates.zdnet.com [Source type: General]

^ On one of my recent projects the non-scrum team tried using daily meetings (idea borrowed from the scrumish team around, where daily meetings worked perfectly).
  • scrumdevelopment : Message: Re: Daily Scrum 25 September 2009 4:28 UTC groups.yahoo.com [Source type: General]

^ I understand that the Product Backlog is used to prioritize functionality, but I would think that the actual requirements of a backlog item would be completed before the Sprint Planning Meeting.

.Visualization of the work stages and limitations for simultaneous unfinished user stories and defects are familiar from the Kanban model.^ Parallel work of both groups on User Story n (US n) .
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

^ If the acceptance tests for the user story are running well, the test group can execute the test cases and report the defects.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

^ After the planning meeting, the collocated group and the remote test group start working on the same user story (or use case, or another task) of the sprint backlog.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

.Using these methods, the team’s workflow is directed in a way which allows for minimum completion time for each user story or programming error, and which on the other hand ensures that each team member is constantly employed.^ Contains subtasks for the user stories, use cases, and tasks to implement in the next sprint.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

^ If you check this field, the project manager will receive a request each time a task is completed by his team.
  • Scrum, Agile Development Method (scrum) — Documentation 25 September 2009 4:28 UTC doc.openerp.com [Source type: FILTERED WITH BAYES]

^ Explain to the test group the goal of the sprint and the user stories, use cases, and tasks with their subtasks that the collocated group committed to.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

[16]
.To illustrate each stage of work, teams working in the same space often use post-it notes or a large whiteboard.^ As originally developed, Scrum assumes that the project team is all working at the same location.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

^ On one of my recent projects the non-scrum team tried using daily meetings (idea borrowed from the scrumish team around, where daily meetings worked perfectly).
  • scrumdevelopment : Message: Re: Daily Scrum 25 September 2009 4:28 UTC groups.yahoo.com [Source type: General]

^ After the planning meeting, the collocated group and the remote test group start working on the same user story (or use case, or another task) of the sprint backlog.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

.[17] In the case of decentralized teams stage illustration softwares, such as ScrumWorks and (the combination of) JIRA and GreenHopper can be used to visualize each team’s use stories, defects and tasks divided into separate phases.^ Define the sprint goal and user stories, use cases, and tasks that the team commits to.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

^ Contains subtasks for the user stories, use cases, and tasks to implement in the next sprint.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

^ Explain to the test group the goal of the sprint and the user stories, use cases, and tasks with their subtasks that the collocated group committed to.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

In their simplest, the work stages are
  • Unstarted
  • Ongoing
  • Completed
tasks or usage stories. .If desired, though, the teams can add more stages of work (such as “defined”, “designed”, “tested” or “delivered”).^ Consequence: less work done but more working software delivered.
  • CS372:Project Planning and Management 15 September 2009 2:44 UTC ftp.cse.csusb.edu [Source type: FILTERED WITH BAYES]

^ With more than 4 or 5 people in a team working on the same artifacts -- especially code -- you need a system that stops two people modifying the same file in parallel.
  • CS372:Project Planning and Management 15 September 2009 2:44 UTC ftp.cse.csusb.edu [Source type: FILTERED WITH BAYES]

^ Do it as a test to see if you can improve your performance on the the other phases and thus deliver a faster product if you spend 20% more time or 50% more time or 100% more time on design.
  • How not to rush yourself? - Stack Overflow 15 September 2009 2:44 UTC stackoverflow.com [Source type: General]

.These additional phases can be of assistance if a certain part of the work becomes a bottleneck and the limiting values of the unfinished work can not be raised.^ These are umbrella agreements, meaning that additional partnerships can be defined as a simple “Annex”, with limited delay and legal overhead.
  • Unlocking Collaboration 15 September 2009 2:44 UTC www.slideshare.net [Source type: FILTERED WITH BAYES]

^ Not only do they work well, but they will provide a consolidated archive of our work process – perhaps that will have additional value in the “lessons learned” phase.
  • Unlocking Collaboration 15 September 2009 2:44 UTC www.slideshare.net [Source type: FILTERED WITH BAYES]

.A more specific task division also makes it possible for employees to specialize in a certain phase of work.^ We will make no direct contributions to the division- specific analysis – although these enabling mechanisms will bring a much larger pool of expertise to bear in every division.
  • Unlocking Collaboration 15 September 2009 2:44 UTC www.slideshare.net [Source type: FILTERED WITH BAYES]

^ Complexity: O(number_of_parts^2) Handling more than half-a-dozen people directly reporting to you is a crazy making task.
  • CS372:Project Planning and Management 15 September 2009 2:44 UTC ftp.cse.csusb.edu [Source type: FILTERED WITH BAYES]
  • CS372:Input of Project Management and Planning 15 September 2009 2:44 UTC www.csci.csusb.edu [Source type: FILTERED WITH BAYES]

[18]
.There are no set limiting values for unfinished work.^ If no, find a part of the work items set that is testable in the next sprint.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

.Instead, each team has to define them individually by trial and error; a value too small results in workers standing idle for lack of work, whereas values too high tend to accumulate large amounts of unfinished work, which in turn hinders completion times.^ If you check this field, the project manager will receive a request each time a task is completed by his team.
  • Scrum, Agile Development Method (scrum) — Documentation 25 September 2009 4:28 UTC doc.openerp.com [Source type: FILTERED WITH BAYES]

^ Look for error conditions you'll have to handle, and whatever amount of time you think it will take to complete each feature/function, pad that amount by a lot.
  • How not to rush yourself? - Stack Overflow 15 September 2009 2:44 UTC stackoverflow.com [Source type: General]

.[19] A rule of thumb worth bearing in mind is that no team member should have more than two simultaneous selected tasks, and that on the other hand not all team members should have two tasks simultaneously.^ In the paralel case we have two or more scenarios depending on which task we start first.
  • CS372:Project Planning and Management 15 September 2009 2:44 UTC ftp.cse.csusb.edu [Source type: FILTERED WITH BAYES]

^ So when there are more than one predecessor activity you need to add extra dummy arrows/activities/task to show the dependency.
  • CS372:Input of Project Management and Planning 15 September 2009 2:44 UTC www.csci.csusb.edu [Source type: FILTERED WITH BAYES]

^ A coherent community of support for E/PO leads and team members would effectively raise the bar, and bring this level of excellence to all E/PO efforts.
  • Unlocking Collaboration 15 September 2009 2:44 UTC www.slideshare.net [Source type: FILTERED WITH BAYES]

[18]
.The major differences between Scrum and Kanban are derived from the fact that in Scrum work is divided into sprints that last a certain amount of time, whereas in Kanban the workflow is continuous.^ Sprint time line Parallel work .
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

^ You can write acceptance tests for a group of testable work items into the sprint backlog.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

^ You also learned how to improve communication and cooperation between the collocated group and the remote test group, and how to counteract some of the disadvantages of working in different geographic locations.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

This is visible in work stage tables which in Scrum are emptied after each sprint. In Kanban all tasks are marked on the same table. .Scrum focuses on teams with multifaceted know-how, whereas Kanban makes specialized, functional teams possible.^ The Scrum master, a facilitator for Scrum, knows how Scrum works and coaches the team to get the best possible results in software development in future releases.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

^ But that would require specialized groups that know how to build curriculae...
  • IRC log of tp on 2007-11-07 15 September 2009 2:44 UTC tibor.w3.org [Source type: Original source]

^ Preferably, the extended team (or as many members as possible) should participate in the same Scrum or agile workshop.
  • Architecture tip: Adapting the Scrum project management method for geographically separated teams 25 September 2009 4:28 UTC www.ibm.com [Source type: General]

[20]
Since Scrum-ban is such a new development model, there is not much reference material. .Kanban, on the other hand, has been applied in software development at least by Microsoft and Corbis.^ Mercurial Communications, Corp: Joint CTO and interim COO. Led company growth from 12 to 115 staff, delivering turnkey software development for AOL, Microsoft, HP, Boeing, the Government of Canada and many others.
  • Unlocking Collaboration 15 September 2009 2:44 UTC www.slideshare.net [Source type: FILTERED WITH BAYES]

^ The questionnaire will then ask you other questions about the software development project.

[21]

Product development

.Scrum as applied to product development was first referred to in “The New Product Development Game” (Harvard Business Review 86116:137–146, 1986) and later elaborated in “The Knowledge Creating Company” both by Ikujiro Nonaka and Hirotaka Takeuchi (Oxford University Press, 1995).^ Wether you are a Product Owner managing your Product Backlog and Release Plan, a Scrum Master coaching and supporting a team or a developer tracking issues and sharing knowledge, Agilo is highly configurable to adapt to your specific workflow and...
  • Scrum Resources | ZDNet 25 September 2009 4:28 UTC updates.zdnet.com [Source type: General]

^ Additionally, he will lead the development efforts to create the Social Media Dashboard, Media Library, and Knowledge Base systems that comprise the Project B products.
  • Unlocking Collaboration 15 September 2009 2:44 UTC www.slideshare.net [Source type: FILTERED WITH BAYES]

^ Co-founder and CTO of Minnesota’s first corporate DVD production company.
  • Unlocking Collaboration 15 September 2009 2:44 UTC www.slideshare.net [Source type: FILTERED WITH BAYES]

Today there are records of Scrum used to produce financial products, Internet products, and medical products by ADM.

See also

Other Agile methods

References

  1. ^ a b Schwaber, Ken (1 February 2004). Agile Project Management with Scrum. Microsoft Press. ISBN 978-0-735-61993-7. 
  2. ^ Takeuchi, Hirotaka; Nonaka, Ikujiro (January-February 1986). "The New New Product Development Game" (PDF). Harvard Business Review. http://apln-richmond.pbwiki.com/f/New%20New%20Prod%20Devel%20Game.pdf. Retrieved 2008-09-26. 
  3. ^ DeGrace, Peter; Stahl, Leslie Hulet (1 October 1990). Wicked problems, righteous solutions. Prentice Hall. ISBN 978-0-135-90126-7. 
  4. ^ Sutherland, Jeff (October 2004). "Agile Development: Lessons learned from the first Scrum" (PDF). http://www.scrumalliance.org/resources/35. Retrieved 2008-09-26. 
  5. ^ http://www.implementingscrum.com/2006/09/11/the-classic-story-of-the-pig-and-chicken/
  6. ^ Schwaber, p. 7
  7. ^ http://www.scrum.org/scrumguides/
  8. ^ Schwaber, p. 135
  9. ^ Cohn, Mike (May 2007). "Advice on Conducting the Scrum of Scrums Meeting". http://www.scrumalliance.org/articles/46-advice-on-conducting-the-scrum-of-scrums-meeting. Retrieved 2009-07-23. 
  10. ^ Schwaber, p. 133
  11. ^ Sprint, Planning (January-February 2009). Sprint Planning Rules. http://www.sprintplanning.com/SprintPlanningRules.aspx. Retrieved 2009-03-30. 
  12. ^ Schwaber, p. 137
  13. ^ Schwaber, p. 138
  14. ^ Invented by Mike Cohn, more info can be found here
  15. ^ Schwaber, pp. 141–143
  16. ^ p.5 Crisp.se
  17. ^ Leansoftwareengineering.com
  18. ^ a b Leansoftwareengineering.com
  19. ^ p.18 - 19 Crisp.se
  20. ^ p.22 - 23 Crisp.se
  21. ^ Infoq.com (The video and the summary)

Further reading

.

External links

Videos


Citable sentences

Up to date as of December 16, 2010

Here are sentences from other pages on Scrum (development), which are similar to those in the above article.








Got something to say? Make a comment.
Your name
Your email address
Message