Remote Working and Collaboration in Agile Teams

Agile software development relies heavily on tight and continuous collaboration, which becomes a challenge when team members work at a distance. Despite significant focus on distributed Agile working, remote working, when only one or two individuals are not co-located with the rest of the team, remains largely unexplored. We focus on one organisation with several such teams and investigate one in detail using distributed cognition – a theoretical framework for studying collaborative work. We present the results of a group retrospective, and a comparative analysis of collaboration in the team, taking the contrasting perspectives of the remote worker and his co-located teammates. The analysis shows substantial differences in three aspects: virtual artefacts; information flow; and the primacy of structure and facilities provided by collaborative platforms. Platforms that support meaningful collaboration and engagement for the remote worker, and create parity between all members of the team are crucial to integrating capability

What is the Evolution of Flexible Work in Corporations and What are the Key Trends?

[Excerpt] Around the world, especially in North America and Europe, businesses are exploring and embracing new ways of bringing flexibility to the workplace. This flexibility movement began as a talent initiative to accommodate working mothers and over time has evolved to include practices such as compressed workweeks, job sharing, phased work and much more. In a survey conducted by FlexJobs and WorldatWork, 80% of companies surveyed offered some kind of work flexibility options to their employees. In fact, flexible work opportunities are no longer viewed as a differentiator in the employee value proposition; it is now expected. Flexible work is here to stay and will continue to evolve in order to meet the needs of an agile, digital and millennial dominated workplace

Flexible Global Software Development (GSD): Antecedents of Success in Requirements Analysis

Globalization of software development has resulted in a rapid shift away from the traditional collocated, on-site development model, to the offshoring model. Emerging trends indicate an increasing interest in offshoring even in early phases like requirements analysis. Additionally, the flexibility offered by the agile development approach makes it attractive for adaptation in globally distributed software work. A question of significance then is what impacts the success of offshoring earlier phases, like requirements analysis, in a flexible and globally distributed environment? This article incorporates the stance of control theory to posit a research model that examines antecedent factors such as requirements change, facilitation by vendor and client site-coordinators, control, and computer-mediated communication. The impact of these factors on success of requirements analysis projects in a “flexible” global setting is tested using two quasi-experiments involving students from Management Development Institute, India and Marquette University, USA. Results indicate that formal modes of control significantly influence project success during requirements analysis. Further, facilitation by both client and vendor site coordinators positively impacts requirements analysis success

Distributed-Pair Programming can work well and is not just Distributed Pair-Programming

Background: Distributed Pair Programming can be performed via screensharing or via a distributed IDE. The latter offers the freedom of concurrent editing (which may be helpful or damaging) and has even more awareness deficits than screen sharing. Objective: Characterize how competent distributed pair programmers may handle this additional freedom and these additional awareness deficits and characterize the impacts on the pair programming process. Method: A revelatory case study, based on direct observation of a single, highly competent distributed pair of industrial software developers during a 3-day collaboration. We use recordings of these sessions and conceptualize the phenomena seen. Results: 1. Skilled pairs may bridge the awareness deficits without visible obstruction of the overall process. 2. Skilled pairs may use the additional editing freedom in a useful limited fashion, resulting in potentially better fluency of the process than local pair programming. Conclusion: When applied skillfully in an appropriate context, distributed-pair programming can (not will!) work at least as well as local pair programming

Collaborative Environments. Considerations Concerning Some Collaborative Systems

It is obvious, that all collaborative environments (workgroups, communities of practice, collaborative enterprises) are based on knowledge and between collaboration and knowledge management there is a strong interdependence. The evolution of information systems in these collaborative environments led to the sudden necessity to adopt, for maintaining the virtual activities and processes, the latest technologies/systems, which are capable to support integrated collaboration in business services. In these environments, portal-based IT platforms will integrate multi-agent collaborative systems, collaborative tools, different enterprise applications and other useful information systems.collaboration, collaborative environments, knowledge management, collaborative systems, portals, knowledge portals, agile development of portals

A MANAGED APPROACH OF INTERACTION BETWEEN AGILE SCRUM AND SOFTWARE CONFIGURATION MANAGEMENT SYSTEM

In current age the agile software development is one of the most popular software development methodology but due the mismanagement and lack of efficient handling of agile scrum and software configuration management system our software industry is facing a high rate of failed product, keeping this as my motivation, I have designed a efficient checklist which will help the industry to organized the interaction between agile scrum process and software configuration management system in a efficient and managed way and definitely that will increase the successful project in the software industry. Index-term : Agile Scrums, Software development, Software configuration management system, Checklist, Successful project

The Digital Transformation of Law: Are We Prepared for Artificially Intelligent Legal Practice?

We live in an instant access and on-demand world of information sharing. The global COVID-19 pandemic has accelerated the necessity of remote working and team collaboration. Work teams are exploring and utilizing the remote work platforms required to serve in place of stand-ups common in the agile workplace. Online tools are needed to provide visibility to the status of projects and the accountability necessary to ensure that tasks are completed on time and on budget. Digital transformation of organizational data is now the target of AI projects to provide enterprise transparency and predictive insights into the process of work. In order to preserve legal frameworks without losing the high ground of principled rule making, standard setting, and practical application, prompt action is required. Legal practitioners as well as legal academics must coalesce to present a united front to persuade their constituents (clients, students, and others looking to them for guidance) that AI will serve to safeguard human legal rights, responsibilities, and remedies as this digital transformation sweeps every industry sector