2 resultados para Computer software -- Development
em Dalarna University College Electronic Archive
Resumo:
In software development organizations there is sometimes a need for change. In order to meet continuously increasing demands from their customers, Sandvik IT Services- SITS, at Sandvik in Sweden, required improving the way they worked with software development. Due to issues like a lot of work in progress and lot of simultaneous tasks for individuals in the teams that caused stress, it was almost impossible to address the question of working with improvements. In order to enable the improvement process Kanban was introduced in the software development teams. Kanban for software development is a change method created by David J. Anderson. The purpose of this thesis is twofold. One part is to assess what effects Kanban has had on the software development teams. The other part is to make a documentation of the Kanban implementation process at SITS. The documentation has been made on the basis of both company internal resources and observations of the Kanban implementation process. The effects of Kanban have been researched with an interview survey to the teams that have gone through the Kick start of the Kanban process. The result of the thesis is also twofold. One part of the result is an extensive documentation of the implementation process of Kanban at SITS. The other part is an assessment of the effects that Kanban has had at SITS. The major effects have been that the teams are experiencing less stress, more focus on quality and better customer collaboration. It is also evident is that it takes time for some effects to evolve when implementing Kanban
Resumo:
Mnga projekt misslyckas och en av anledningarna r dlig styrning av projektet i allmnhet och inom IT branschen i synnerhet. Baserad p kritik av de traditionella metoderna under de senaste ren, s har det uppkommit flera lttrrliga metoder som kallas Agila metoder. Scrum r den mest knda Agila metoden som anvnds idag. Metoden lovar goda resultat, men i en artikel ur tidningen Computer Sweden (feb 2009) str det siffror visar att nio av tio Scrumprojekt misslyckas. Artikeln triggade vrt intresse av att ta reda p vilka problem specifika fr Scrum som mnga har kritiserat och valde drfr att rikta in vr studie mot detta. Uppsatsen syftar till att underska om lokala IT-fretag i Borlnge, Headlight, Sogeti ochstatliga ntkapacitetleverantren Trafikverket ICT lider av det allmnna problem som de andra Scrumanvndarna upplever i samband med anvndningen av metoden. Denna uppsats har fokus p fyra problemomrden: bristfllig dokumentation, smre effektivitet i arbetsprocessen, smre effektivitet i arbetsprocessen i stora projekt samt bristande std fr utvrdering. Fr vr studie har litteraturstudier och intervjuer genomfrts. Intervjuserier gjordes p elva personer hos vra fallfretag. Mlgruppen fr vra intervjuer r Product Owner (PO) ScrumMaster (SM) och utvecklare. Vi kan efter genomfrd studie dra slutsatsen att de allmnna upplevda problem som de andra Scrumanvndaren upplever har vi ven kunnat identifiera hos vra fallfretag. Resultaten har bekrftats med insamlade data och vr teoretiska ram. I diskussionen presenterar vi rekommendationer fr att undvik relaterade problem med Scrum.
