E-Delivery Training System using Agile Technology

E-learning represents a wide range of methods in order to provide education or online training of the electronic delivery of information. E-Learning provides interactive technologies and announcement systems to improve the learning experience. It has the potential to transform the way that teach and learn across the board. It cannot replace teachers and lecturers, but alongside existing methods it can enhance the quality and reach of their teaching. Normally speaking, this type of education is carried out during the average of the World Wide Web where the instructive organization construct its programs and materials obtainable on a special website in such a way that students are capable to make use of them and interrelate with effortlessness during closed or shared, networks, or the Internet, and during utilize of e-mail and online discussion groups. This work proposed the Agile technique development process as an iterative method based on collaboration. Agile would focus on version, growing development, hasty prototyping, and constant feedback and evaluation

Bridging the gap between research and agile practice: an evolutionary model

There is wide acceptance in the software engineering field that industry and research can gain significantly from each other and there have been several initiatives to encourage collaboration between the two. However there are some often-quoted challenges in this kind of collaboration. For example, that the timescales of research and practice are incompatible, that research is not seen as relevant for practice, and that research demands a different kind of rigour than practice supports. These are complex challenges that are not always easy to overcome. Since the beginning of 2013 we have been using an approach designed to address some of these challenges and to bridge the gap between research and practice, specifically in the agile software development arena. So far we have collaborated successfully with three partners and have investigated three practitioner-driven challenges with agile. The model of collaboration that we adopted has evolved with the lessons learned in the first two collaborations and been modified for the third. In this paper we introduce the collaboration model, discuss how it addresses the collaboration challenges between research and practice and how it has evolved, and describe the lessons learned from our experience

Agile Research - Getting Beyond the Buzzword

Oh yeah, we\u27re an Agile shop, we gave up Waterfall years ago. - product owners, managers, or could be anyone else. You will seldom have a conversation with a product or software development team member without the agile buzzword thrown at you at the drop of a hat. It would not be an oversell to say that Agile software development has been adopted at a large scale across several big and small organizations. Clearly, Agile is an ideology that is working, which made me explore more on its applicability in research. As someone who has been in the Information Technology sector for more than a decade and a half, and a new entrant in the research community, I am inclined to uplift the best practices from my IT experience and evaluate implementing them in research. The idea is to assess the provocative metaphor of agile research and the different research philosophies around the concept. The aim is to explore Agile research methodology, its applicability and find the scenarios where it can add value and those where it may not

The Impact of Organizational Culture and Structure on the Routinization of Agile Software Development Methodologies

Agile software development methodologies represent a departure from the heavy document-driven procedures of plan-driven approaches. As organizations continue to adopt agile methodologies, understanding the factors that influence the routinization of agile is a growing concern. In recent years, researchers have focused their attention to the issues of post-adoptive agile use in order to extend our knowledge on agile assimilation. However, little research has been conducted to expose the assimilation gaps that occur as organizations seek to increase the extent and intensity of their agile use. Following prior literature, our objective is to articulate a model that explains the impact of organizational culture and structure on the routinization of agile methods. Our theoretical model provides helpful insights that extend our of knowledge of agile assimilation in organizations

Estudio de mapeo sistemático de las herramientas y técnicas para la identificación de los niveles de agilidad del equipo de desarrollo en un proyecto de software

El presente estudio registra los instrumentos, herramientas y técnicas para identificar el nivel de agilidad, se realizó una investigación en base al Método del Mapeo Sistemático (SMS), se investigó en diferentes bibliotecas virtuales. Los instrumentos, herramientas y técnicas permiten identificar los niveles de agilidad tanto en las organizaciones y equipos. Se tiene como finalidad evaluar el conocimiento, además, el nivel de agilidad mediante diferentes escalas, al momento de desarrollar sus proyectos, contribuyen con el mejoramiento continuo.He present study records the instruments, tools and techniques to identify the level of agility, an investigation was carried out based on the Systematic Mapping Method (SMS), it was investigated in different virtual libraries. The instruments, tools and techniques allow to identify the levels of agility in both organizations and teams. The purpose is to evaluate knowledge, in addition, the level of agility through different scales, at the time of developing your projects, they contribute to continuous improvement

Success factors in information technology projects

The failure of IT projects has been a major problem over the decades. The previous study has found that big IT projects overran 45% of the cost, 7% of schedule and produced 56% less profit than expected (Mckinsey 2012). Today, the situation has not been changed significantly. It is crucial to explore critical success factors to enable software companies to avoid risks in project development across various industries. These factors should cover more organizational aspects among different customer businesses as IT projects are more challenging and diverse with a high level of novelty. The main aim of this thesis is to research organizational aspects in different software firms which can moderately im-pact IT project success and how these factors influence total project performance as IT projects have failed with many reasons over years. The study was analyzed on empirical data from the IT barometer 2014 data set of Finnish Data Processing Association. All senior managers were asked whether they agree or disagree that specified critical factors can impact on IT project success by selecting the respective scale. The study results found three of the most important factors which moderately impact the IT project success. IT architecture, enterprise architecture, and selection of IT solutions can enable software firms to gain business objectives and expected IT project outcomes during the implementation phase to meet market demands and customer satisfaction. In addition, only IT architecture and enterprise architecture can help the project team run a development project on time to gain product leadership and competitive advantages. There are other critical factors can enable IT projects to gain success in expected project outcomes during the implementation phase. In total project performance aspect, the study findings show that IT architecture can improve project timeliness better than the achievement of business objectives to gain good market share. Further, enterprise architecture has a moderate correlation with project time-to-market and achievement of business objectives to enhance project success against fierce rivalry among competitors within the software industry. The study found that the selection of IT solutions can only enable a project team to increase project competency in order to gain business objectives during development time. Hence, senior managers should consider the importance of these success factors during development phases to gain project success as expectations and improve total project performance for surpassing competitors on the market for profits and competitive advantages

Software Development and CSCW:Standardization and Flexibility in Large-Scale Agile Development

Identifying which agile methods and processes are most effective depends on the goals and aims of an organisation. Agile development promotes an environment of continuous improvement and trust within self-organising teams. Therefore, it is important to allow teams to have the flexibility to customize and tailor their chosen methods. However, in a large-scale agile deployment, there needs to be a degree of process standardization across the organisation; otherwise, different teams will not be able to effectively share knowledge and best practices. This paper addresses this classic CSCW issue of the tensions that arise between process standardization and flexibility in a large-scale agile deployment at the BBC