du.sePublications
Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Varför arbetar vissa utvecklingsteam agilt med kravhantering och vissa inte?: En fallstudie på Lantmäteriet
Dalarna University, School of Technology and Business Studies, Information Systems.
2017 (Swedish)Independent thesis Basic level (degree of Bachelor), 10 credits / 15 HE creditsStudent thesisAlternative title
Why do some software developing teams work with agile methods in requirement engineering and some do not? – A case study in Lantmäteriet (English)
Abstract [sv]

Kravhantering inom systemutveckling utgör basen för vad som ska utvecklas. Agila systemutvecklingsmetoder blir vanligare för varje dag som går. Det har dock ofta visat sig finnas utmaningar med hur man anpassar just kravhanteringen till de agila metoderna.

Verksamheter har olika förutsättningar för att arbeta agilt. Lantmäteriet i Gävle uttryckte ett behov att undersöka varför den agila praxis man hade inte följdes av alla utvecklingsteam i samband med kravhanteringen.

Syftet med denna uppsats var därför att undersöka varför vissa utvecklingteam i en verksamhet arbetade agilt med sin kravhantering medan vissa inte gjorde det. För att undersöka detta utförde jag en fallstudie där jag med hjälp av enkäter och intervjuer samlade in data från både utvecklare och personer på verksamhetssidan som var inblandade i kravhanteringen. Resultaten visade att orsakerna till att en agil kravhantering fungerade så olika var flera. Genom att använda en tematisk analys kunde jag urskilja några framträdande orsaker. Kommunikation och flexibilitet samt kunskap och förståelse för olika perspektiv var teman som utgjorde positiva faktorer. De teman som istället utgjorde negativa faktorer var bland andra otydliga roller, brist på direktiv, en övertro till metoder och processer, osynk mellan verksamhet och IT, prioriteringsproblem, förvaltningsplaner, attityder och IT-arkitektur.

Abstract [en]

Requirements engineering within software development is the foundation of what needs to be developed. Agile methods in software development become more common every day. It has however often been shown that there are certain challenges with how to adopt the requirements engineering to the agile methodology.

Businesses have different preconditions for agile methods. Lantmäteriet in Gävle had a need to examine why not all the developing teams followed agile methods within the requirements engineering process.

The purpose with this thesis was thus to examine why some developing teams in an organization worked in an agile manner with the requirements engineering, and some did not. To do this I performed a case study where I collected data through questionnaires and interviews from both developers and people from the business side. The results showed that the reasons for these differences were multiple. Communication and flexibility, and knowledge and understanding for different perspectives were the positive factors. The themes that hindered an agile way of working were, among others, unclear roles, lack of direction, too much reliance on methods and processes, discrepancy between business and IT, prioritizing issues, management plans, attitudes and IT architecture.

Place, publisher, year, edition, pages
2017.
Keyword [en]
Requirements engineering, agile requirements engineering, agile software development, agile methods.
Keyword [sv]
Kravhantering, agil kravhantering, agil systemutveckling, agila metoder.
National Category
Information Systems
Identifiers
URN: urn:nbn:se:du-25514OAI: oai:DiVA.org:du-25514DiVA: diva2:1120759
Available from: 2017-07-07 Created: 2017-07-07

Open Access in DiVA

fulltext(1002 kB)39 downloads
File information
File name FULLTEXT01.pdfFile size 1002 kBChecksum SHA-512
0ec478da79892e329834cf60f2f210e039686fff8fa846088073b4a258c7eab8f205421678b7736774fb401d1f2f1e30dc866c6b6f7bde10bc143ffc1f99e0c9
Type fulltextMimetype application/pdf

By organisation
Information Systems
Information Systems

Search outside of DiVA

GoogleGoogle Scholar
Total: 39 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

Total: 395 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf