DOCSLIB.ORG

Agile Methodologies & Scrum: When Is a Team Ready to Start Using

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Agile Methodologies & Scrum: When Is a Team Ready to Start Using University of Patras Department of Business Administration Graduate Programme (Master) in Business Administration (MBA) Agile methodologies & Scrum: When is a team ready to start using it? Author: Chrysomalli Eleni Supervisor: Stamatiou Ioannis Three-member Examining Board: Karayani Despoina Peppas Pavlos Stamatiou Ioannis February 22, 2018 Acknowledgments This is the point where i must acknowledge that this thesis is not an individual piece of work. On the contrary,it is the result of the interaction and help of many people. I would like to begin by thanking all Albelli employees for their time, support and valuable help. This research could not have been done without them. Thank you wholeheartedly! Afterwards,I want to thank my supervisor, Mr. Yianni Stamatiou, for the support and the trust he has shown me throughout this period. His encouraging words have always made me want to become better. A big thank you to Albelli's front-end(e commerce team), and more specifically to Eveline Sparreboom, Mascha Welling, Emanuele Pane, Constant Zomer & Robbert-Jan Klein for the trust they showed me when I even did not believe in myself. I feel very lucky that I had the chance to work with each of you individually and to learn so many things from all of you. You are all special to me. Continuing, I would like to thank my family for their unlimited love, support and continuous encouragment. A special thank you to my close friends. I recognize and I am grateful for everything you have done for me and a further great thank you to my sisterly friend Georgia Tsekoura. Finally, this diploma’thesis is devoted to two people: I. My grandmother, who died two years ago but has always been always a model for me and a source of inspiration. She taught me how not to quit and that there is nothing more precious than being alive one more day. II. Miguel Pereira, who has been for the last 1.5 year, a true mentor for me. His support, his immediate help, his patience and his guidance have helped me mature professionally and personally. Thank you all! Page 2 of 121 Table of contents Abstract .................................................................................................................................. 8 Introduction ........................................................................................................................... 9 Purposes and goals of research ......................................................................................... 9 Structure of thesis ............................................................................................................ 10 Chapter 1: Waterfall versus Agile ........................................................................................... 12 1.1 Waterfall Model design ............................................................................................. 12 1.2 Agile Methodologies .................................................................................................. 15 Chapter 2: Most commonly used Agile Methods &Practices ................................................ 24 2.1 Introduction ............................................................................................................... 24 2.2 Agile Methodologies .................................................................................................. 24 2.2.1 Adaptive software development (ASD) .................................................................. 24 2.2.2 Agile modelling ....................................................................................................... 26 2.2.3 Crystal Clear methods: ............................................................................................ 26 2.2.4 Dynamic systems development method (DSDM): .................................................. 27 2.2.5 Extreme programming (XP): ................................................................................... 28 2.2.6 Feature-driven development (FDD): ....................................................................... 29 2.2.7 Lean software development: .................................................................................. 29 2.2.8 Kanban .................................................................................................................... 30 2.2.9 Scrum ...................................................................................................................... 31 2.2.10 Scrumban .............................................................................................................. 32 2.2.11 Rapid application development (RAD).................................................................. 32 2.3 Agile practices ............................................................................................................ 33 2.3.1 Acceptance test-driven development (ATDD) ........................................................ 33 2.3.2 Behaviour-driven development (BDD) ................................................................... 33 2.3.3 Business analyst designer method (BADM) ............................................................ 34 2.3.4 Cross-functional team ............................................................................................. 35 2.3.5 Continuous integration (CI): ................................................................................... 36 2.3.6 Domain-driven design (DDD) .................................................................................. 36 2.3.7 Pair programming ................................................................................................... 36 2.3.8 Planning poker ........................................................................................................ 37 2.3.9 Refactoring .............................................................................................................. 37 2.3.10 Test-driven development (TDD) ........................................................................... 38 2.3.11 User story .............................................................................................................. 38 2.3.12 Story-driven modelling ......................................................................................... 38 Page 3 of 121 2.3.13 Retrospective ........................................................................................................ 39 2.3.14 Velocity tracking ................................................................................................... 39 2.3.15 User Story Mapping .............................................................................................. 39 2.3.16 More Practices: ..................................................................................................... 39 Chapter 3 –Scrum .................................................................................................................... 41 3.1 Roles ........................................................................................................................... 42 3.1.1 Product Owner ........................................................................................................ 42 3.1.2 Scrum Master .......................................................................................................... 43 3.1.3 Scrum Team ............................................................................................................ 44 3.1.4Stakeholders ............................................................................................................ 45 3.2 Artifacts ...................................................................................................................... 45 3.2.1 Product Backlog ...................................................................................................... 45 3.2.2 Sprint Backlog ......................................................................................................... 48 3.2.3 Product increment .................................................................................................. 49 3.3 Workflow .................................................................................................................... 49 3.3.1 The Scrum process .................................................................................................. 49 3.3.2 Sprint Planning ........................................................................................................ 49 3.3.3 The Daily Scrum ...................................................................................................... 50 3.3.4 Sprint Review .......................................................................................................... 50 3.3.5 Sprint Retrospective ............................................................................................... 51 3.4 Work & Delivery Flow-Example ................................................................................. 52 Chapter 4:Methodology of research .................................................................................. 54 4.1 Purpose of research- Definition of the research question ....................................... 54 4.2 Research plan ............................................................................................................. 54 4.2.1 Selection of research plan....................................................................................... 54 4.2.2Method of collecting data ......................................................................................
Load more

Recommended publications
  • RISK MANAGEMENT - DSDM Organization Design for Enterprise Agility Paper ID: PMIBC-16-1-002 Author: Ms
    ARCHITECTING PROJECT MANAGEMENT for Enterprise Agility… July 14 to 16, 2016, NIMHANS Convention Centre, Bengaluru RISK MANAGEMENT - DSDM Organization Design For Enterprise Agility Paper ID: PMIBC-16-1-002 Author: Ms. PONSASIKALA PONNIAH Project Management Practitioners’ Conference 2016 CONTENTS Abstract ........................................................................................................................................................................ 3 Introduction .................................................................................................................................................................. 3 Details of the paper...................................................................................................................................................... 4 Conclusion ................................................................................................................................................................. 14 References ................................................................................................................................................................ 15 w ww.pmibangalorechapter.org Pa g e 2 Project Management Practitioners’ Conference 2016 ABSTRACT The purpose of this paper was to ascertain the extent to which risk management practices are incorporated into agile development projects. Businesses are increasingly operating in extremely turbulent environments necessitating the need to respond and adapt to change more quickly and improve
    [Show full text]
  • Software Development Methodologies on Android Application Using Example
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by VUS Repository POLYTECHNIC OF ŠIBENIK DEPARTMENT OF MANAGEMENT SPECIALIST STUDY OF MANAGEMENT Ivan Bumbak SOFTWARE DEVELOPMENT METHODOLOGIES ON ANDROID APPLICATION USING EXAMPLE Graduate thesis Šibenik, 2018. POLYTECHNIC OF ŠIBENIK DEPARTMENT OF MANAGEMENT SPECIALIST STUDY OF MANAGEMENT SOFTWARE DEVELOPMENT METHODOLOGIES ON ANDROID APPLICATION USING EXAMPLE Graduate thesis Course: Software engineering Mentor: PhD Frane Urem, college professor Student: Ivan Bumbak Student ID number: 0023096262 Šibenik, September 2018. TEMELJNA DOKUMENTACIJSKA KARTICA Veleučilište u Šibeniku Diplomski rad Odjel Menadžmenta Diplomski specijalistički stručni studij Menadžment Razvojne metode programa na Android platformi koristeći primjer Ivan Bumbak [email protected] Postoji mnogo razvojnih metoda programskih rješenja koje se mogu koristiti za razvoj istih na bilo kojoj platformi. Koja metoda će se koristiti ovisi o zahtjevnosti samog projekta, koliko ljudi radi na projektu, te u kojem vremenskom roku projekt mora biti isporučen. U svrhu ovog diplomskog rada razvijena je Android aplikacija putem tradicionalne metode, iako su danas sve više i više popularne takozvane agile metode. Agile, ili agilan, znači biti brz i sposoban reagirati na vrijeme te prilagoditi se svim promjenama u bilo kojem trenutku razvoja projekta. U radu su objašnjenje najpopularnije agile metode te su prikazane prednosti korištenja agile metoda u odnosu na tradicionalnu metodu. (37 stranica
    [Show full text]
  • Personal Extreme Programming with Moscow Prioritization for Developing Library Information System
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Proceeding of the Electrical Engineering Computer Science and Informatics Proceeding of EECSI 2018, Malang - Indonesia, 16-18 Oct 2018 Personal Extreme Programming with MoSCoW Prioritization for Developing Library Information System 1st Gita Indah Marthasari 2nd Wildan Suharso 3rd Frendy Ardiansyah Informatika Informatika Informatika Universitas Muhammadiyah Malang Universitas Muhammadiyah Malang Universitas Muhammadiyah Malang Malang, Indonesia Malang, Indonesia Malang, Indonesia [email protected] [email protected] [email protected] Abstract— Software development projects require determined so that the application is completed on time as experience and knowledge of the developer or clients related to user’s request. The priority setting in PXP is based on the system which will be developed. Unclear clients’ needs technical risk, and business value [7]. potentially emerge many changes of needs during the process State Attorney is one of the institutions that play an of development which can not be resolved by using essential role in the control of the law and the welfare of the conventional software development methodology. The implementation of the less significant requirements either from people, especially in the territory of its power in Indonesia the clients or the other stakeholders causes the project [8]. Based on the preliminary survey, we have found a few development becomes longer. Therefore, a technique is needed weaknesses in the service process in Batu State Attorney. to arrange the priority of software requirements. In this paper, One of the weaknesses is found in library services.
    [Show full text]
  • Using Eight Agile Practices in an Online Course to Improve Student Learning and Team Project Quality
    Using Eight Agile Practices in an Online Course to Improve Student Learning and Team Project Quality Andrea R. Hulshult Miami University Timothy C. Krehbiel Miami University As online learning continues to increase, instructors need different teaching methods and technologies for teaching online. This study explores how Agile practices are integrated into an online IT course. We focus on incorporating eight Agile practices (team charters, daily stand-ups, Kanban boards, story cards, MoSCoW, timeboxing, showcases, and retrospectives). Students were surveyed at the end of the course and the results indicate Agile enhanced students’ learning and increased the quality of their final project. INTRODUCTION One promising approach to enhance collaboration and group projects in online courses is Agile methodology. According to Krehbiel et al., (2017), Agile is a collection of practices aimed at enhancing group collaboration. Agile began in the computer software industry in the early 2000s to manage software development projects. When working in an Agile environment, teams focus on collectively articulating their goals, reflecting on their work and making necessary adjustments, having authentic group interactions, improving team dynamics, and encouraging innovation (Smith & Sidky, 2009). Agile teams work in iterative, usually two-week, work cycles that have a regular cadence of feedback and reflection practices. Teams get real-time feedback on their work, reflect on their functioning as a team by discussing what is going well and what needs improved, make adjustments to their work, and repeat. Agile teams have higher quality outcomes and better meet their customers’ needs compared to traditional project management models (Krehbiel et al., 2017). As Agile continues to integrate into other industry sectors, including education, researchers are adapting the traditional Agile values for their industry’s specific value system.
    [Show full text]
  • An Essay on Agile Project Management Practices [Habilitações Académicas]
    Daniel Rabasquinho Gouveia Undergraduate in Engineering and Industrial Management Sciences [Nome completo do autor] [Habilitações Académicas] [Nome completo do autor] [Habilitações Académicas] [Nome completo do autor] An Essay on Agile Project Management Practices [Habilitações Académicas] [Título da Tese] [Nome completo do autor] [Habilitações Académicas]Dissertation for the achievement of an Integrated Master’s degree in Industrial Engineering and Management [Nome completo do autor] [Habilitações Académicas] Dissertação para obtenção do Grau de Mestre em [Nome completo do autor] [EngenhariaAdviser: Informática]Prof. Dr. Alexandra Maria Baptista Ramos Tenera, Assistant Professor, [Habilitações Académicas] FCT-UNL [Nome completo do autor] Jury: [Habilitações Académicas] President: Prof. Dr. Isabel Maria do Nascimento Lopes, Assistant Professor, FCT-UNL Members: Prof. Dr. Mário José Batista Romão, Associate Professor, ISEG Prof. Dr. Alexandra Maria Baptista Ramos Tenera, Assistant Professor, FCT-UNL September, 2015 Daniel Rabasquinho Gouveia Undergraduate in Engineering and Industrial Management Sciences [Nome completo do autor] [Habilitações Académicas] [Nome completo do autor] [Habilitações Académicas] [Nome completo do autor] An Essay on Agile Project Management Practices [Habilitações Académicas] [Título da Tese] [Nome completo do autor] [Habilitações Académicas]Dissertation for the achievement of an Integrated Master’s degree in Industrial Engineering and Management [Nome completo do autor] [Habilitações Académicas] Dissertação para
    [Show full text]
  • Understanding the Characteristics, Benefits and Challenges of Agile It
    International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.5, September 2019 UNDERSTANDING THE CHARACTERISTICS , BENEFITS AND CHALLENGES OF AGILE IT PROJECT MANAGEMENT : A LITERATURE BASED PERSPECTIVE Godfred Yaw Koi-Akrofi 1, Joyce Koi-Akrofi 2 and Henry Akwetey Matey 3 1,3 Department of IT Studies, University of Professional Studies, Accra 2PMO Department, Vodafone Ghana ABSTRACT The objectives of this study was to bring out the understanding of the concept of agile IT project management; what it is and what it is not. It was also aimed at comparing the pros and cons of both agile and traditional methods of IT project management in a typical industry setting; the challenges of going purely agile, and so on. It is purely a review of literature of peer reviewed papers sourced mainly from Google Scholar. It was revealed that agile outweigh the traditional methods in terms of benefits, but its implementation poses a lot of challenges due to a number of issues, paramount among them being organizational culture and empowerment of the project team. This has resulted in a number of industries sticking to the traditional methods despite the overwhelming benefits of agile. In another school of thought, the combination of the two paradigms is the way forward. KEYWORDS Project Management, Scrum, Agile, Software, Traditional 1. INTRODUCTION Seventeen individuals gathered at The Lodge at Snowbird Ski Resort in Wasatch Mountains in Utah on February 11-13, 2001 to speak, ski, relax and attempt to discover common ground — and, of course, eat.. What emerged was the Manifesto of Agile Software Development (Retrieved on 16/06/2019 at https://agilemanifesto.org/history.html ).
    [Show full text]
  • Software Requirements Prioritisation: a Systematic Literature Review on Significance, Stakeholders, Techniques and Challenges
    Received October 3, 2018, accepted November 7, 2018, date of publication November 19, 2018, date of current version December 18, 2018. Digital Object Identifier 10.1109/ACCESS.2018.2881755 Software Requirements Prioritisation: A Systematic Literature Review on Significance, Stakeholders, Techniques and Challenges FADHL HUJAINAH 1, ROHANI BINTI ABU BAKAR 1, MANSOOR ABDULLATEEF ABDULGABBER 2, AND KAMAL Z. ZAMLI 1, (Member, IEEE) 1Faculty of Computer Systems and Software Engineering, Universiti Malaysia Pahang, Kuantan 26300, Malaysia 2Faculty of Computer and Cyber Science, Software Engineering, University Prince Mugrin, Al-Madinah 41499, Saudi Arabia Corresponding author: Fadhl Hujainah ([email protected]) This work was partially supported by the Fundamental Research Grant: A New Model for Automated Stakeholder Quantification and Prioritization Based on User Needs for Software System Development from the Ministry of Higher Education Malaysia under Grant RDU190164 and the PGRS170393 Grant from Universiti Malaysia Pahang. ABSTRACT As one of the gatekeepers of quality software systems, requirements' prioritization (RP) is often used to select the most important requirements as perceived by system stakeholders. To date, many RP techniques that adopt various approaches have been proposed in the literature. To identify the strengths, opportunities, and limitations of these existing approaches, this paper studied and analyzed the RP field in terms of its significance in the software development process based on the standard review guidelines by Kitchenham. By a rigorous study selection strategy, 122 relevant studies were selected to address the defined research questions. Findings indicated that RP plays a vital role in ensuring the development of a quality system with defined constraints. The stakeholders involved in RP were reported, and new categories of the participating stakeholders were proposed.
    [Show full text]
  • We Use Agile. What Does That Mean?
    Project Methodology We use Agile. What does that mean? Traditional Project Management Agile Project Management All features and requirements are Project starts with a backlog of fixed at the start of the project. desired features. Items are selected on a sprint-by-sprint basis from thebacklog. Specifications are planned in detail General functionality is defined for before starting work. each backlog task, but specifics Source: dzone.com are flexible. 1. Start withbroad-stroke requirements (Usually in the form of user stories) Adding or changing features after Adding or changing features can 2. Build a Minimum Viable Product (MVP) the project has started requires a be done any time, by managing 3. Review and collect feedback formal change order. the backlog. 4. Implement changes based on feedback 5. Repeat Timeline is fixed. Timeline is flexible. Discover User-Driven Agile 1 Knowledge transfer and research. Understanding both business goals and user goals. Optimize Plan 5 Continually measuring and 2 Reviewing and analyzing our optimizing to ensure the best findings and planning out possible experience and the overall implementation results. strategy. Build Design 4 Implementing anddeploying 3 Realizing the strategy and the project based on the concept and turning it into a strategy and design. tangible design andprototype. How toAgile ➔ Tickets are executed using MoSCoW method of prioritization. ◆ MUST have this requirement to meet the business needs. ◆ SHOULD have this requirement if at all possible, but project success does not rely on this. ◆ COULD have this requirement if it does not affect the fitness of business needs of the project. ◆ WON'T include this requirement in a given release, but it may be considered for the future.
    [Show full text]
  • Problem Solver's Toolkit
    THE PROBLEM SOLVER’S TOOLKIT CONTEXT EXPLORE VALIDATE DELIVER This toolkit is a suite of best practice tools and methods that can be adopted by any team, at any time, in the design of products, services and experiences. Take it to workshops and meetings, or use it on your own to help you understand the people you’re designing for and the problems you’re solving for them. Concept, design and layout Adam Corcoran Content Adam Corcoran, Alex Krstev, David Kaldor and Amy Woodlock Collaborators and reviewers This work is licensed under the Creative Nicole McDougall, Caroline Sheehan, Commons Attribution-NonCommercial- Kathleen Watt, Caitlin Calder-Potts, NoDerivatives 4.0 International Rushda Halith, Amber Mackinnon, Keira License. To view a copy of this license, Morris-Akeroyd, Katrina Harrison, visit http://creativecommons.org/ Jennifer Shailer, Alexander Caminer licenses/by-nc-nd/4.0/ or send a letter Printed on 60% post consumer waste to Creative Commons, PO Box 1866, recycled, FSC certified, carbon neutral Mountain View, CA 94042, USA. paper from a 100% carbon neutral printer. INTRODUCTION What this kit is, why we designed it, who you should use it with, and how. i WHAT, WHY, WHO, HOW Whether you’re working on your first project at Australian Red Cross, or you’re a seasoned veteran, this toolkit can help you deliver solutions that fit peoples’ needs. What’s this kit about? And why should I use it? We have put together a selection of the best tools and techniques currently in use for designing better products, services and experiences - based on solid evidence.
    [Show full text]
  • Requirements Prioritization in Agile Environments: a Model for Effective Prioritization
    Universiteit Leiden ICT in Business Requirements prioritization in Agile environments: a model for effective prioritization Name: Eleni Stavrou Student-no: s1277030 Date: 25/02/2016 1st supervisor: Christoph Johan Stettina 2nd supervisor: Hans le Fever 1 2 Table of contents 1. Problem definition ............................................................................................................... 6 1.1 Introduction ................................................................................................................. 6 1.2 Research question ........................................................................................................ 7 1.3 Scope of research ......................................................................................................... 7 2. Related work ....................................................................................................................... 8 2.1 Agile Software Development ............................................................................................. 8 2.1.2 Scrum Methodology.................................................................................................. 10 2.2 Requirements Engineering ............................................................................................... 11 2.2.1 Requirements Prioritization ....................................................................................... 12 2.3 Requirement prioritization criteria and methods ..............................................................
    [Show full text]
  • Understanding the Characteristics, Benefits and Challenges of Agile It
    UNDERSTANDING THE CHARACTERISTICS, BENEFITS AND CHALLENGES OF AGILE IT PROJECT MANAGEMENT: A LITERATURE BASED PERSPECTIVE Godfred Yaw Koi-Akrofi, Joyce Koi-Akrofi, Henry Matey To cite this version: Godfred Yaw Koi-Akrofi, Joyce Koi-Akrofi, Henry Matey. UNDERSTANDING THE CHARAC- TERISTICS, BENEFITS AND CHALLENGES OF AGILE IT PROJECT MANAGEMENT: A LIT- ERATURE BASED PERSPECTIVE. International Journal of Software Engineering & Applications (IJSEA), 2019, 10 (5), pp.25-44. 10.5121/ijsea.2019.10502. hal-02869395 HAL Id: hal-02869395 https://hal.archives-ouvertes.fr/hal-02869395 Submitted on 29 Jun 2020 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. International Journal of Software Engineering & Applications (IJSEA), Vol.10, No.5, September 2019 UNDERSTANDING THE CHARACTERISTICS , BENEFITS AND CHALLENGES OF AGILE IT PROJECT MANAGEMENT : A LITERATURE BASED PERSPECTIVE Godfred Yaw Koi-Akrofi 1, Joyce Koi-Akrofi 2 and Henry Akwetey Matey 3 1,3 Department of IT Studies, University of Professional Studies, Accra 2PMO Department, Vodafone Ghana ABSTRACT The objectives of this study was to bring out the understanding of the concept of agile IT project management; what it is and what it is not. It was also aimed at comparing the pros and cons of both agile and traditional methods of IT project management in a typical industry setting; the challenges of going purely agile, and so on.
    [Show full text]
  • Ranking XP Prioritization Methods Based on the ANP
    (IJACSA) International Journal of Advanced Computer Science and Applications, Vol. 8, No. 5, 2017 Ranking XP Prioritization Methods based on the ANP Abdulmajeed Aljuhani Luigi Benedicenti Sultan Alshehri Faculty of Engineering and Faculty of Engineering and Computer Science and Applied Science Applied Science Information Technology College University of Regina, University of Regina, Majmaah University Regina Canada Regina Canada Majmaah, Saudi Arabia Abstract—The analytic network process (ANP) is considered ranking the prioritization techniques that can be used to prior- one of the most powerful tools to facilitate decision-making itize the system requirements. In this study, five prioritization in complex environments. The ANP allows decision makers to techniques are selected as alternatives, which are Kano Model, structure their problems mathematically using a series of simple Relative Weighting, Top-Ten Requirements, 100-Dollar Test, binary comparisons. Research suggests that ANP can be useful in and MoSCoW. software development, where complicated decisions are routinely made. Industrial adoption of ANP, however, is virtually non- existent because of its perceived complexity. We believe that II. RELATED WORK ANP can be very beneficial in industry as it resolves conflicts in a mutually acceptable manner. We propose a protocol for its Requirements may be prioritized based on various features. adoption by means of a case study that aims to explain a ranking These features receive no consensus on their importance in the method to assist an XP team in selecting the best prioritization process. Developers seek to increase the delivered value to the method for ranking the user stories. The protocol was tested in user by making the most suitable decision.
    [Show full text]