search query: @keyword sopimus / total: 10
reference: 2 / 10
« previous | next »
Author:Suomela, Ulla
Title:Contracts in Agile Projects
Sopimukset ketterissä projekteissa
Publication type:Master's thesis
Publication year:2010
Pages:(10) + 85 s. + liitt. 12      Language:   eng
Department/School:Informaatio- ja luonnontieteiden tiedekunta
Main subject:Tietojenkäsittelyoppi   (T-76)
Supervisor:Laine, Juha
Instructor:Aalto, Timo
OEVS:
Electronic archive copy is available via Aalto Thesis Database.
Instructions

Reading digital theses in the closed network of the Aalto University Harald Herlin Learning Centre

In the closed network of Learning Centre you can read digital and digitized theses not available in the open network.

The Learning Centre contact details and opening hours: https://learningcentre.aalto.fi/en/harald-herlin-learning-centre/

You can read theses on the Learning Centre customer computers, which are available on all floors.

Logging on to the customer computers

  • Aalto University staff members log on to the customer computer using the Aalto username and password.
  • Other customers log on using a shared username and password.

Opening a thesis

  • On the desktop of the customer computers, you will find an icon titled:

    Aalto Thesis Database

  • Click on the icon to search for and open the thesis you are looking for from Aaltodoc database. You can find the thesis file by clicking the link on the OEV or OEVS field.

Reading the thesis

  • You can either print the thesis or read it on the customer computer screen.
  • You cannot save the thesis file on a flash drive or email it.
  • You cannot copy text or images from the file.
  • You cannot edit the file.

Printing the thesis

  • You can print the thesis for your personal study or research use.
  • Aalto University students and staff members may print black-and-white prints on the PrintingPoint devices when using the computer with personal Aalto username and password. Color printing is possible using the printer u90203-psc3, which is located near the customer service. Color printing is subject to a charge to Aalto University students and staff members.
  • Other customers can use the printer u90203-psc3. All printing is subject to a charge to non-University members.
Location:P1 Ark Aalto     | Archive
Keywords:agile
project
contract
Scrum
XP
requirement
product owner
ketterä
projekti
sopimus
Scrum
XP
vaatimus
tuotteen omistaja
Abstract (eng): Agile software development has become a very attractive alternative in software development projects.
Despite gaining success in software development projects, Agile projects cause difficulties in contract negotiations and contract creation.
Contract conditions of traditional methodologies are not necessarily valid in agile methodologies; with respect to certain issues, traditional and agile processes are radically different.
Agile software development supports continuous change and responding to alterations of requirements that stem from business value changes.
Creating contract conditions with a changing scope is very challenging, and it is difficult to create a contract with changing contract conditions.
In Agile projects, one never knows in the beginning how much the development project is going to change as it progresses.

This research investigated how well contracts of traditional projects adapt to agile projects.
The research consisted of a survey and a literature review of the traditional and agile project model.
The need for contract amendments was based on the differences between the models and on their influence on contract conditions.

The research questions revealed the crucial properties of the agile project model, which require contract amendments.
An active product owner is one of the most important success factors of an agile project.
Both parties have to be aware of their respective duties and responsibilities.
Role descriptions, change management and clear description of acceptance criteria in the contract and the project guarantee a successful project.
In addition, the contract termination conditions of an agile project should be clarified.
Abstract (fin): Ketterästä ohjelmistokehityksestä on tullut hyvin vetovoimainen vaihtoehto ohjelmistokehitysprojekteissa.
Menetelmää on alettu soveltamaan projekteihin, mutta ketterien projektien sopimusvaihe on haastava.
Ketterä ohjelmistokehitys tukee jatkuvaa muutosta ja vaatimustenhallinnan reagointia muuttuviin liiketoiminnan olosuhteisiin.
Muuttuvia ehtoja on kuitenkin vaikea kirjata sopimukseen, sillä alussa ei tiedetä, kuinka paljon kehitysprojekti tulee edetessään muuttumaan.

Tässä työssä tutkittiin perinteisten sopimusten soveltuvuutta ketteriin projekteihin.
Tutkimus koostui kyselytutkimuksesta sekä ketterää ja perinteistä projektimallia käsittelevästä kirjallisuuskatsauksesta.
Sopimuksen muutostarpeet perusteltiin mallien erilaisuudella ja sen vaikutuksella sopimusehtoihin.

Tutkimuskysymysten avulla löydettiin ketterän projektimallin keskeiset ominaisuudet, jotka edellyttävät sopimusmuutoksia.
Huomattiin, että aktiivinen tuotteenomistaja on elintärkeä ketterän projektin onnistumisen kannalta ja vastuiden ja roolien kuvauksien tulee olla sopimusosapuolten tiedossa.
Roolikuvaukset, muutostenhallinta ja hyväksyntäprosessien selkeä määrittely sopimuksessa ja projektissa takaavat ketterän projektin onnistumisen.
Myös sopimuksen irtisanomista tulee selkeyttää ketterän projektin ehdoissa.
ED:2010-05-10
INSSI record number: 39602
+ add basket
« previous | next »
INSSI