Det finnes ingen problemer -bare løsninger


Scrum er en iterativ og inkrementell, fleksibel programvareutviklingsramme for styring av produktutvikling. Det definerer "en fleksibel, helhetlig produktutviklingsstrategi hvor et utviklingslag fungerer som en enhet for å nå et felles mål", utfordrer antakelser om den "tradisjonelle, sekvensielle tilnærmingen" til produktutvikling og gjør det mulig for lag å organisere seg selv ved å oppmuntre til fysisk samarbeid -lokalisering eller nært samarbeid mellom alle lagmedlemmer, samt daglig ansikt-til-ansiktskommunikasjon blant alle gruppemedlemmer og involverte disipliner.


Lær Mer

Siden vår informasjon her er hentet direkte fra unlater vi å ovesette dette til norsk.

The product owner represents the product's stakeholders and the voice of the customer; and is accountable for ensuring that the team delivers value to the business. The product owner writes customer-centric items (typically user stories), prioritizes them based on importance and dependencies, and adds them to the product backlog in order of delivery. Scrum teams should have one product owner. This role should not be combined with that of the scrum master. The product owner should focus on the business side of product development and spend the majority of their time liaising with stakeholders and should not dictate how the team reaches a technical solution.

The development team is responsible for delivering potentially shippable increments (PSIs) of product at the end of each sprint (the sprint goal). A team is made up of 3–9 individuals who do the actual work (analysis, design, develop, test, technical communication, document, etc.). Development teams are cross-functional, with all of the skills as a team necessary to create a product increment. The development team in Scrum is self-organizing, even though there may be some interaction with a project management office (PMOs).

Scrum is facilitated by a scrum master, who is accountable for removing impediments to the ability of the team to deliver the product goals and deliverables. The scrum master is not a traditional team lead or project manager but acts as a buffer between the team and any distracting influences. The scrum master ensures that the Scrum framework is followed. The scrum master helps to ensure the team follows the agreed processes in the Scrum framework, often facilitates key sessions, and encourages the team to improve.

A sprint (or iteration) is the basic unit of development in Scrum. The sprint is a timeboxed effort; that is, it is restricted to a specific duration. The duration is fixed in advance for each sprint and is normally between one week and one month, with two weeks being the most common. Each sprint starts with a sprint planning event that aims to define a sprint backlog, identify the work for the sprint, and make an estimated forecast for the sprint goal. Each sprint ends with a sprint review and sprint retrospective, that reviews progress to show to stakeholders and identify lessons and improvements for the next sprints. Scrum emphasizes working product at the end of the sprint that is really done. In the case of software, this likely includes that the software has been fully integrated, tested and documented, and is potentially shippable.

At the end of a sprint, the team holds two events: the sprint review and the sprint retrospective. At the sprint review, the team reviews the work that was completed and the planned work that was not completed. Presents the completed work to the stakeholders (a.k.a. the demo) and the team and the stakeholders collaborate on what to work on next

The product backlog comprises an ordered list of requirements that a scrum team maintains for a product. It consists of features, bug fixes, non-functional requirements, etc.—whatever must be done to successfully deliver a viable product. The product owner prioritizes those product backlog items (PBIs) based on considerations such as risk, business value, dependencies, size, and date needed. Items added to a backlog are commonly written in story format. The product backlog is what will be delivered, ordered into the sequence in which it should be delivered. It is visible to everyone but may only be changed with the consent of the product owner, who is ultimately responsible for ordering product backlog items for the development team to choose.

The sprint backlog is the list of work the development team must address during the next sprint. The list is derived by the scrum team progressively selecting product backlog items in priority order from the top of the product backlog until they feel they have enough work to fill the sprint. The development team should keep in mind its past performance assessing its capacity for the new sprint, and use this as a guide line of how much 'effort' they can complete. The product backlog items may be broken down into tasks by the development 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 skills of the team. This promotes self-organization of the development team, and developer buy-in.