Porovnání frameworků pro rychlý vývoj aplikací na platformě Java / Comparison of rapid web application development frameworks for the Java platformZilvar, Tomáš January 2010 (has links)
The thesis is concerned with a comparison of two rapid web development frameworks for the Java platform - Tapestry 5 and Grails. The goal is to get acquainted with both of the frameworks, explain their basic principles and usage, compare their solution to common challenges and their contribution to faster development. Furthermore, the goal is to de fine a set of criteria for the comparison and match each one of them with their respective weights representing their importance in certain decision making scenarios. The frameworks are new and under dynamic development, therefore the bene ts of this thesis are an extensive research in foreign resources, summary of the acquired knowledge, practical usage examples and furthermore the assessment of the frameworks' strenghts and weaknesses. The conclusions and comparison quanti cation can then be used to strategically choose the appropriate framework if necessarry.
In the rapidly changing market of today, companies need to be responsive and react quickly to changes in both their competitors’ behaviour but also to changes in their own technical environment. In this thesis I have examined the agile characteristics of a number of companies in Stockholm, with focus on three agile concepts; Scrum, eXtreme Programming and Test Driven Development. The work started off by a prestudy, in which I have identified the criteria that a company needs to fulfil in order to be considered agile. This resulted in four main categories of characteristics; Quality, Flexibility, Communication and Competence. After doing the prestudy, these characteristics were investigated through a combination of a quantitative study and a case study. While the results mostly lean towards agile behaviour rather than non agile, it was shown that a lot of work still remains, for instance regarding improvements in the communications area, and also in the way these companies apply the agile methodologies examined. / Inom dagens snabba marknad behöver företag kunna reagera snabbt och effektivt på förändringar i både sina konkurrenters beteende, men också på förändringar i sin egen tekniska miljö. I den här uppsatsen har jag undersökt de agila attributen hos ett antal företag i Stockholm, med fokus på tre agila koncept; Scrum, eXtreme Programming och Test Driven Development. Arbetet inleddes med en förstudie, där jag identifierade de kriterium ett företag behöver uppfylla för att kunna anses vara agilt. Detta resulterade i fyra kategorier av attribut; Kvalitet, Flexibilitet, Kommunikation och Kompetens. Efter förstudien undersöktes dessa attribut genom en kombination av en enkätstudie och en studie av ett enskilt företag. Resultaten lutar mestadels åt ett agilt beteende hos de undersökta företagen, men jag har också kunnat påvisa att mycket arbete återstår, exempelvis inom kommunikationsområdet, och även gällande hur de observerade företagen applicerar de tre undersökta agila koncepten.
06 June 2018
(has links) (PDF)
Erfolg macht attraktiv – das gilt auch für die Prinzipien und Methoden der agilen Softwareentwicklung. Diese finden momentan eine weite Verbreitung, denn sie geben offenbar gute oder zumindest bessere Antworten auf die Probleme, mit denen die herkömmlichen Projektmethoden nicht zurande kommen (Royce 1970). Agile, manchmal auch »leichtgewichtig« genannte Methoden vermeiden übermäßige Planung und Spezifikation, sie ersetzen sie durch eine schnelle Abfolge von Zyklen aus Aktion-Reflexion und Neuausrichtung. Sie bevorzugen die Kollaboration unter gleichberechtigten Experten, die Kommunikation statt Weisung. Und sie beziehen den Kunden und späteren Nutzer bereits in die Entwicklungsarbeit mit ein, denn der Kunde ist die wichtigste Informationsquelle, er bestimmt, inwiefern das Produkt für ihn nützlich ist. Durch solche Prinzipien ist es möglich, Zeit- und Budgetüberschreitungen besser zu vermeiden, einen produktiven Umgang mit Ungewissheit und wechselnden Situationen zu entwickeln und schonender mit der menschlichen Arbeitskraft umzugehen (Abrahamsson et al. 2003). So hat sich das Konzept der »Agilität« auch auf andere Bereiche übertragen, z.B. auf die Gründung von Unternehmen (»Lean Start Up«, Ries 2011) oder die Gestaltung von Organisationsstrukturen (»Agile Organisation«, Richardson 2005). [... aus dem Text]
Erickson, Alyssa Jean
01 April 2018
Agile development is a software development methodology that originated in 2001 (Beck, et al.). It has since gained wide recognition and use in the software industry, and is characterized by iterative development cycles. Organizations outside of the software industry are also finding ways to adapt Agile development to their contexts. BYU Independent Study (BYUIS) is an online education program at Brigham Young University that provides online courses at the high school and university levels. In April 2016, BYUIS implemented the Agile development process to the design and development of online courses. This thesis is a case study that looks specifically at the adoption of Agile at BYUIS, from its implementation in April 2016 to the time of this study in summer of 2017. The question this qualitative study seeks to answer is as follows: how and why did the adoption of the Agile development methodology to instructional design practices at BYUIS reflect or differ from the 12 principles of Agile development? To answer this research question, the researcher used multiple data sources: semi-structured interviews with three administrators, two production team managers, and three instructional designers; surveys for BYUIS student employees (i.e., scrum team members) after each week of observation; and field note observations of three Agile scrum teams for two weeks each. The data from each of these sources was analyzed through a descriptive coding process and then organized into a thematic network analysis. The Results section analyzes evidence from the interviews, surveys, and observations that reflect or differ from each of the 12 principles of Agile. The Discussion addresses three main issues of implementing Agile at BYUIS: how to accommodate for part-time schedules, the complexity of working on different projects, and how to facilitate communication in scrum teams if co-location is not possible. It also looks at how these three issues could be manifest in other organizations and introduces potential solutions. The researcher then presents suggestions for future research on Agile in instructional design or other contexts.
01 January 2022
This is an open source education management system developed on React with Agile management method. Suitable for learning various languages, it is currently developed for the purpose of learning Chinese. Teachers can post assignments and announcements, and students can do lots of practice and quiz on this.
Quality assurance with TL 9000 in agile software development of set-top boxes : The case of Motorola and the use of ScrumGustafsson, Kristofer, Jacobsson, Johan January 2009 (has links)
<p>In today’s fast-paced world, there is a constant demand for better and more efficient ways of doing business. Motorola in Linköping are using the agile development framework, Scrum in their software development. A certain level of quality must also be assured of the delivered goods and services. Is it possible to use Scrum and still meet the quality requirements?</p><p>This Master Thesis is performed to investigate if it is possible to achieve a quality certificate from TL 9000, the telecom industry extension of ISO 9000, when using the agile development framework Scrum. The investigation consists of interviews and observations at Motorola, Linköping, along with literature studies about quality systems and agile development.</p><p>The conclusion is that it is possible to meet the TL 9000 requirements when using Scrum, under the condition that some additional processes are performed and that other parts of the organization also fulfills the remaining requirements. This is needed since there are requirements that are out of scope for the Scrum framework. Examples of the suggested additions are to follow the Scrum framework more strictly and to adopt a more specific definition of done.</p>
We mainly study development velocity in agile teams in this dissertation. The concept of development velocity relates to the classical problem of time estimation in software development and software development planning. Building on previous literature as well as a case study, we explore and theorize the factors that cause ‘velocity flux’, i.e. fluctuations in development velocity through studying the relationship between development velocity and the rate of incoming customer feature requests. The aim of this study is to contribute to a better understanding of what causes velocity flux in agile development, and discusses the implications of the findings for research and practical implications for agile planning. As a result, we propose nine factors that cause velocity flux, and provide some strategies to overcome them in order to make a more effective sprint planning in agile teams.
Globally Distributed Agile Teams: An Exploratory Study of the Dimensions Contributing to Successful Team ConfigurationSharp, Jason H. 12 1900 (has links)
Drawing upon configurational theory, work group design research, virtualness concepts, and the software agility literature, the purpose of this study was to provide a starting point for theorizing about the successful configuration of globally distributed agile teams by exploring the dimensions of team structure, virtualness, and agility. Due to the complex nature of this topic, the need to examine the phenomenon within its natural setting, and the limited amount of research that has been conducted in this particular area, this study adopted an embedded multiple-case research design. The primary data collection method consisted of semi-structured interviews involving members of globally distributed agile teams within three U.S. based organizations with members located in distributed sights in multiple countries. Additional data were collected from archival records. Within-case and cross-analysis was conducted using qualitative data analysis software. This study provides a starting point for answering the question of how the configuration of globally distributed agile teams differs from the configuration of other types of globally distributed teams; it synthesizes past research and findings into a comprehensive theoretical framework; it provides a starting point for theorizing about the successful configuration of globally distributed agile teams; it helps practitioners to identify and address the challenges related to the configuration of globally distributed agile teams; and it presents a set of best practices which will inform organizations on how to configure their globally distributed agile teams.
Moderní metodiky vedení projektů (pro implementace zakázkového SW) / Modern project management methodology (for custom implementations SW)Zatloukal, Filip January 2013 (has links)
This thesis deals with the issue of project management in the development of custom software, particularly PRINCE2 methodology and agile approaches to software development. The work is divided into two parts. The first part is theoretical. It describes the basic concepts of project management, project history and characterizes the selected software development methodologies. The classical methods are represented by waterfall and spiral models. In the context of the agile methods are described Scrum, Extreme Programming, Kanban and Scrumban. Regarding the standards of project management this thesis describes in detail the methodology PRINCE2 which at the end of the theoretical part will be compared to the standards of PMI and IPMA. The second part is practical and describes an adaptation of PRINCE2 for small projects and helps to decide which tools of PRINCE2 are required for small projects use and which ones can be ignored. In this thesis the process of managing product delivery within the PRINCE2 methodology is replaced by the agile methodology Scrumban that is adapted for a software development within analyzed organization. The thesis focuses on a more detailed description of the methodology Scrumban, established metrics and motivation within the development team.
Knowledge Sharing in an Agile Organization As enhancer of dynamic capabilities and enabler of innovation. : The Case of CompanyXPalminteri, Maria Rosaria, Wilcox, Colin January 2017 (has links)
In a rapidly growing and evolving environment, organizations must be able to reconfigure their resource base in order to adapt to changes. Several studies and research findings have already recognized knowledge management as a mean to enhance an organization’s dynamic capabilities and innovation. Effective knowledge management strategies have therefore become essential for an organization to achieve competitive advantage and finally innovate. Among the challenges for an effective knowledge management strategy, the transformation of "tacit" knowledge, that exists only in the experiences and mind of individuals and as such is difficult to be codified and transmitted, into "explicit" knowledge, which instead can be easily expressed and documented, is essential to guarantee continuous organizational learning. Modern software development processes, such as Agile, provide to organizations several knowledge sharing techniques, to aid in the transformation of knowledge from "tacit" to "explicit" one. This study aims at investigating the impact of agile knowledge sharing methodologies on both dynamic and innovation capabilities of a selected case study organization, and further analyses the factors that may be contributing to such relationship. The research is carried out by surveying a representative sample of employees of a German software development company, CompanyX. In total, 15 responses were received and a semi-structured face-to-face interview was conducted with one senior manager. Correlation and reliability testing are used as statistical tools to test both the reliability and validity of the model. Finally, the causality between the factors affecting knowledge sharing methodologies in use at CompanyX and the organization’s dynamic and innovation capabilities are analysed and compared to previous theoretical and empirical research findings. Several important observations are made as a result of our study. In particular, the overall research findings demonstrate that agile knowledge sharing methodologies can act as enhancers of CompanyX dynamic capabilities and enablers of innovation.
Page generated in 0.6145 seconds