Agile development for a multi-disciplinary bicycle stability test bench

Agile software development methods are used extensively in the software industry. This paper describes an argument to explain why these methods can be used within a multi-disciplinary project and provides a concrete description on how to implement such a method, using a case-study to support the rationale. The SOFIE (Intelligent Assisted Bicycle) project was created to develop mechatronic appliances to make bicycles more stable, i.e. safer. A bicycle stability test bench is created within this project and is used as the case study for this research. The relative complexity of the test bench development and partner structure within the SOFIE project has many similarities with large-scale complex projects found in industry. Thus it provides a good environment to research the application of Agile software methods to a multi-disciplinary project

Scrum Game: An Agile Software Management Game

For the past few years, in their attempt to avoid the heavyweight bureaucracy of traditional project management methods such as the Waterfall model, companies have started incorporating agile methods (e.g. Extreme Programming, Scrum, Crystal) for their project development. These methods are characterised by their incremental and iterative delivery, their ability to incorporate change at any stage of the project lifecycle, as well as their small and co-located teams. Even though these methods are included in the syllabus of many software engineering modules at university level, many students currently feel more confident with traditional, rather than agile methods. Many employers find that recent graduates are not equipped with the desired skills of a software engineer because, even though they are knowledgeable in the different software engineering practices, they lack practical experience of these methods. The combination of these two factors show that the university’s approach to teaching software management methods is only theoretical and it does not give students the opportunity to apply them to their projects so they can get a better understanding of their use. The project developed the prototype of a computer game that simulates the use of the Scrum method within different projects, named Scrum Game. The game is supplementary material for a lecture course, and its purpose is to guide students through the Scrum lifecycle. Students can thereby get a small glimpse of the different phases of Scrum, the way that the different Scrum roles interact with each other, and the way that Scrum is used to implement real projects. In addition, the Scrum Game has an administrator mode enabling lecturers to view a log of the progress of all their students in the game. They can use this mode to create new projects or to alter existing ones by adding new tasks or problems, thereby adjusting the level of difficulty to the level of their students, or so that it fits their teaching. The web-based system was developed using PHP, MySQL, HTML, CSS, JavaScript, AJAX (jQuery) and Google Charts API. The system was thoroughly tested against the initial requirements and other system tests. The Scrum Game was evaluated by 22 peer colleagues reading for an MSc in Software Engineering at the University of Southampton, to identify whether the system achieved its goal of introducing students to the Scrum methodology and reaching a deeper understanding of its practical use during project implementation. The results of a questionnaire showed that little prior knowledge was assumed during the game, and that 86% of the participants felt that the game helped them learn more about Scrum. When asked, “Do you think that if this game was part of your Project Management module, would you get a better understanding about Scrum?” an impressive 95% (21 out of 22 participants) agreed that the game would be helpful, and rated the system 8 out of 10 on average

To Overcome Communication Challenges in Distributed/Virtual Scrum Teams

The purpose of this research is to give an overview of a scrum in distributed teams and to suggest ways overcome communication challenges in such projects. In this research proposal, the latest available research on a scrum in distributed teams will be thoroughly analyzed and evaluated to know the possible solutions for communication problems in distributed teams. A review of the literature suggested scrum is widely accepted agile methodology in software projects and also it works best within collocated teams. However, the literature review also proposes that lack of proper communication is one of the main challenge faced by distributed scrum teams which needs more research. Effective communication among teams is fundamental to the agile approach in which proper and continuous feedback are absolutely necessary to improve team productivity and software quality. It is important to have right communication tool, trust among team members, organized daily scrum meetings, proper coordination, less time zone difference between locations and no language barrier to have effective communication within virtual scrum teams. Due to progression in technology scrum projects are going distributed as there are many benefits to the organizations. A brief literature review will be conducted to study the research problem which will provide valuable solutions to the communication issues in distributed teams. This research paper will be very useful to other researchers to solve the other challenges of a scrum in distributed projects

AGILE & DISTRIBUTED PROJECT MANAGEMENT: A CASE STUDY REVEALING WHY SCRUM IS USEFUL

Scrum has gained surprising momentum as an agile IS project management approach. An obvious question is why Scrum is so useful? To answer that question we carried out a longitudinal study of a distributed project using Scrum. We analyzed the data using coding and categorisation and three carefully selected theoretical frameworks. Our conclusion in this paper is that Scrum is so useful because it provides effective communication in the form of boundary objects and boundary spanners, it provides effective social integration by building up social team capital, and it provides much needed control and coordination mechanisms by allowing both local and global articulation of work in the project. That is why Scrum is especially useful for distributed IS project management and teamwork

Using Scrum in a side project with distributed teams

Scrum is the most popular agile software development methodology in use today (VersionOne, 2013), (West & Grant, 2010), (Begel & Nagappan, 2007). Many of the Scrum teams work in virtual distributed formations (VersionOne, 2013). The distributed work model introduces multiple burdens, like communication issues, matter of trust, time zones and cultural differences to the teams, which can severely affect performance (Deemer, s.a.). As a result, dislocated Scrum teams have a considerably lower success rate than collocated ones according to various surveys (Ambler S. W., 2008), (Ambler S. W., Agility at Scale Survey 2012, 2012), (Cohn, 2010). This paper researches the topic of “Using Scrum in a side project with distributed teams” and consist of three main parts: theoretical background, methods and results. In the theoretical background we cover the different software development methodologies, agile methodology in particular. We take a deeper look into Scrum; it's history, roles in Scrum, Scrum artifacts and ceremonies. We also briefly discuss virtual teams theory. In the methods we cover the online contract bridge card game development, Lean Startup and Business Model Generation as part of business development, background info on contract bridge, validating the idea, the design and development tools used to build the minimum viable product and the methods of data collection for Scrum. In the results we describe our implementation of Scrum, the building of the minimum viable product, and research made into other early stage startup teams to support our own findings.http://tartu.ester.ee/record=b2656166~S1*es

Managing risks in virtual-agile it projects: The paradigm of responsiveness

Managing risks in IT projects has always been a critical area of study for many researchers and practitioners. Due to the rapid advances in information and communication technologies (ICTs), there is an increasing number of challenges and issues for the IT organisations. Virtual-Agile IT projects being virtually operated and based on Agile methodology principles are facilitating IT industry having their main application in the software development industry, where entities from diverse backgrounds have varied working practices, languages and culture, and works together for achieving common aims. There have been several benefits integrated with the application of Virtual-Agile IT projects but the intersection of these two unique working concepts (Virtual-Agile) gives rise to several risks and uncertainties which have now become a point of concern for these organisations. The need for minimising the possibility of such evolving risks and uncertainties became the foundation of conducting this study from a theoretical viewpoint, where the researcher aimed to propose a conceptual framework helping organisations meet their business objectives constructively. The study is exploratory in nature which discovers all those appropriate practices, strategies and guidelines which support reducing risk and uncertainties between the distributed stakeholders during the product development phase. The research methodology used is primarily dependent on qualitative methods combined with the grounded theory methodology to gather rich and rigorous information from experienced and professional personnel from different geographical regions. Depending upon the procedures of grounded theory methodology, the data were collected and analysed simultaneously under the principles of constant comparison and theoretical sampling. The procedures helped to determine thought-provoking results and highlighted various dimensions of the phenomenon under investigation. Responsiveness which emerged as the central phenomenon to overcome risks and uncertainties in Virtual-Agile IT project environments proposes for a proactive system which could be able to deal with project uncertainties, thus reducing the likelihood of potential risks, and enhancing opportunities for the organisations. Responsiveness, which is an ability of the system to perceive, reflect and adapt changes in the project environments is dependent upon efficiently management of three major components, i.e. technology, timeliness and communication. Technology which is the most critical element when operating in virtual environments requires standardization and should be extensively used to develop strong networks and integration between various locations around the world. Timeliness is elementary and a pre-requisite for completion of on-going multiple projects in IT organisations Communication which is the utmost component, is required at various levels for evolving synchronisation in the overall system, such as when developing correlation and satisfaction among distributed stakeholders, estimating the level of required competency and ensuring an efficient knowledge transfer process. Responsiveness, which is required throughout the development cycle, also further influences formal risk management practices undertaken at various levels of the project. Risk management planning and implementation of the response strategies are dependent upon Responsiveness i.e. how well, timely and using technical resources the entities communicate for determining a solution to a problem. The paradigm developed, thus reflects industrial practices undertaken in the software development industry to meet project objectives and would support organisations and their prominent stakeholders to overcome risks and uncertainties in the future Virtual-Agile IT projects

Beyond the border: A comparative literature review on communication practices for agile global outsourced software development projects

Software development is increasingly heading in the direction of combining agile software development practices and outsourcingsoftware development to external vendors worldwide. The resultingagile global outsourced software development (AGOSD) projects are characterized by applying agile methods to distributed environments, whichresults in several problems for collaboration and coordination. Specifically, communication between the project participantshas been found to be a major challenge in distributed environment. Therefore, our study investigates the problem of improving communication in distributed settings by identifying suitable communication practicesfor usage within AGOSD projects.Based on an extensive literature review,our study (1) provides an overview of adequate practices for usage in AGOSD and (2) points out differences to traditional communication practices ofagile software development(ASD)projects used in collocated, non-distributed environments