Generella riktlinjer vid distribuerad Scrum
Today many companies are global and can exist all over the world. It is more common that projects are conducted in different locations, from various cities in a country to nations in different parts of the world. To manage projects both traditional practices such as the Waterfall method and new flexible methods known as agile methods are used. How is the process affected when a project is distributed, when the team is scattered in different places? This makes it difficult to create a good project, something we will discuss and try to find solutions for. Aspects that can affect the project are difficulties with communication, interaction, timing, language and cultural problems.The company Riksnet which deals with communication is in need of a new website. They are interested in the agile approach as they are not working with any particular method within the project. They want to implement the agile method Scrum for the creation of their website. Scrum emphasizes individuals and interactions over processes and tools, which is facilitated by physical interactions. Riksnet who are located in Umeå while we are located in Gothenburg means that the project will be distributed. This gives us the following question: What problems arise in distributed Scrum and how do they affect the guidelines of the Agile Manifesto?To answer the question we conducted literature reviews, interviews and a case study in which action research was conducted. Based on the finds made in the case study we look at problems that can arise in distributed Scrum and if the Agile Manifesto were broken. The discoveries that were made were put against existing literature and interviews and are the result of this report. The discoveries are leading to general guidelines that are supposed to work for companies like Riksnet.