Towards a situated media practice: Reflections on the implementation of project-led problem-based learning

In the field of media practice education, project-based learning is utilized as a major pedagogic paradigm with the aim of mirroring professional practice within the curriculum. However, if the use of project-based learning is to be considered as more than just a way of administrating student activity, then educators need a critical understanding of how problem encounters order practice within the life cycle of a project. The drawing together of practice-based, project-based and problem-based approaches allows us to see the overlapping nature of these approaches and also differentiate them as unique pedagogies in their own right. It is argued here that this tension between similarity and difference requires a new way of thinking about mirroring professional practice within higher education, one which offers a theory of project-based learning as a productive pedagogy which places problem encounters at its heart

Considerations about Continuous Experimentation for Resource-Constrained Platforms in Self-Driving Vehicles

Autonomous vehicles are slowly becoming reality thanks to the efforts of many academic and industrial organizations. Due to the complexity of the software powering these systems and the dynamicity of the development processes, an architectural solution capable of supporting long-term evolution and maintenance is required. Continuous Experimentation (CE) is an already increasingly adopted practice in software-intensive web-based software systems to steadily improve them over time. CE allows organizations to steer the development efforts by basing decisions on data collected about the system in its field of application. Despite the advantages of Continuous Experimentation, this practice is only rarely adopted in cyber-physical systems and in the automotive domain. Reasons for this include the strict safety constraints and the computational capabilities needed from the target systems. In this work, a concept for using Continuous Experimentation for resource-constrained platforms like a self-driving vehicle is outlined.Comment: Copyright 2017 Springer. Paper submitted and accepted at the 11th European Conference on Software Architecture. 8 pages, 1 figure. Published in Lecture Notes in Computer Science vol 10475 (Springer), https://link.springer.com/chapter/10.1007/978-3-319-65831-5_

Adopt Agile Methodology for Building Wealth Management Platform Building

Agile software development is becoming very important software development methodology in the IT world because it is iterative and its agility. This research shows how the agile methodology helps to deploy the project smoothly by saving time and money. This research also shows the benefits of adopting agile than following traditional procedure. The result of the research would help to adopt and implement the agile methodology and would help to achieve the business goals

Managing Business Process Transformation Projects Using Contextual Hybrid Agile Methodology

Business and business processes never cease to change, and this is especially true with today’s accelerating pace of changing business environment. Executives and project teams in both traditional and Agile organizations across industries have been increasingly motivated to find a flexible project management methodology that can work well and can be readily customized in the context of each of their own organization. This thesis seeks to first abstract the concept and practices of the Agile methodology by examining the hallmarks of both traditional and Agile project management through comparison. It then constructs a contextualized model by identifying key characteristics of a project team and analyzes the most relevant factors that help determine specific Agile practices to adopt. The end goal is to identify an effective and flexible project methodology that business process transformation project teams can use to build or enhance their operating models

OpenScrum: Scrum methodology to improve shared understanding in an open-source community

While we continue to see rise in the adoption of agile methods for software development, there has been a call to study the appropriateness of agile methods in open-source and other emerging contexts. This paper examines Scrum methodology adopted by a large, globally distributed team which builds an open-source electronic medical records platform called OpenMRS. The research uses a mixed method approach, by doing quantitative analysis of source-code, issue tracker as well as community activity (IRC logs, Mailing lists, wiki) in pre and post Scrum adoption, covering a period of 4 years. Later we conducted semi-structured interviews with core developers and followed it up with group discussions to discuss the analysis of the quantitative data and get their views on our findings. Since the project is "domain heavy", contributors (developers and implementers) need to have certain health informatics understanding before making significant contributions. This puts knowledge-sharing and "bus factor" as critical points of management for the community. The paper presents ideas about a tailored Scrum methodology that might better suited for open-source communities to improve knowledge-sharing and community participation, instead of just agilit