35,231 research outputs found
Migrating agile methods to standardized development practice
Situated process and quality frame-works offer a way to resolve the tensions that arise when introducing agile methods into standardized software development engineering. For these to be successful, however, organizations must grasp the opportunity to reintegrate software development management, theory, and practice
Is project management the new management 2.0?
This paper considers the evolving nature of project management (PM) and offers a comparison with the evolving nature of management generally. Specifically, we identify a number of management trends that are drawn from a paper that documents a proposed âManagement 2.0â model, and we compare those trends to the way in which PM is maturing to embrace the challenges of modern organizational progress.Some theoretical frameworks are offered that assist in explaining the shift from the historically accepted âtools and techniquesâ model to a more nuanced and behaviorally driven paradigm that is arguably more appropriate to manage change in todayâs flexible and progressive organizations, and which provide a more coherent response, both in PM and traditional management, to McDonaldâs forces. In addition, we offer a number of examples to robustly support our assertions, based around the development of innovative products from Apple Inc. In using this metaphor to demonstrate the evolution of project-based work, we link PM with innovation and new product development.
Bridging the Gap Between Research and Practice: The Agile Research Network
We report an action research-oriented approach to investigating agile project management methods which aims to bridge the gap between academic research and agile practice. We have set up a research network of academics from two universities, through which we run focussed project-based research into agile methods. Organisations are invited to suggest an âagile challengeâ and we work closely with them to investigate how challenge affects them. Our approach is both academic and practical. We use appropriate research methods such as interviews, observation and discussion to clarify and explore the nature of the challenge. We then undertake a detailed literature review to identify practical approaches that may be appropriate for adoption, and report our findings. If the organisation introduces new practices or approaches as a result of our work, we conduct an academic evaluation. Alternatively, if we uncover an under-researched area, we propose undertaking some basic research. As befits the topic, we work iteratively and incrementally and produce regular outputs.
In this paper we introduce our approach, overview research methods used in the agile research literature, describe our research model, outline a case study, and discuss the advantages and disadvantages of our approach. We discuss the importance of producing outputs that are accessible to practitioners as well as researchers. Findings suggest that by investigating the challenges that organisations propose, we uncover problems that are of real relevance to the agile community and obtain rich insights into the facilitators and barriers that organisations face when using agile methods. Additionally, we find that practitioners are interested in research results as long as publications are relevant to their needs and are written accessibly. We are satisfied with the basic structure of our approach, but we anticipate that the method will evolve as we continue to work with collaborators
People in the E-Business: New Challenges, New Solutions
[Excerpt] Human Resource Planning Societyâs (HRPS) annual State of the Art/Practice (SOTA/P) study has become an integral contributor to HRPSâs mission of providing leading edge thinking to its members. Past efforts conducted in 1995, 1996, 1997, 1998, and 1999 have focused on identifying the issues on the horizon that will have a significant impact on the field of Human Resources (HR). This year, in a divergence from past practice, the SOTA/P effort aimed at developing a deeper understanding of one critical issue having a profound impact on organizations and HR, the rise of e-business. The rise of e-business has been both rapid and dramatic. One estimate puts the rate of adoption of the internet at 4,000 new users each hour (eMarketer, 1999) resulting in the expectation of 250 million people on line by the end of 2000, and 350 million by 2005 (Nua, 1999). E-commerce is expected to reach $1.3 trillion by 2003, and of that, 87 percent will go to the business to business (B2B) and 13 percent to the business to consumer (B2C) segments, respectively (Plumely, 2000)
Misaligned Values in Software Engineering Organizations
The values of software organizations are crucial for achieving high
performance; in particular, agile development approaches emphasize their
importance. Researchers have thus far often assumed that a specific set of
values, compatible with the development methodologies, must be adopted
homogeneously throughout the company. It is not clear, however, to what extent
such assumptions are accurate.
Preliminary findings have highlighted the misalignment of values between
groups as a source of problems when engineers discuss their challenges.
Therefore, in this study, we examine how discrepancies in values between groups
affect software companies' performance.
To meet our objectives, we chose a mixed method research design. First, we
collected qualitative data by interviewing fourteen (\textit{N} = 14) employees
working in four different organizations and processed it using thematic
analysis. We then surveyed seven organizations (\textit{N} = 184). Our analysis
indicated that value misalignment between groups is related to organizational
performance. The aligned companies were more effective, more satisfied, had
higher trust, and fewer conflicts.
Our efforts provide encouraging findings in a critical software engineering
research area. They can help to explain why some companies are more efficient
than others and, thus, point the way to interventions to address organizational
challenges.Comment: accepted for publication in Journal of Software: Evolution and
Proces
Coordinating Knowledge Work in Multi-Team Programs: Findings from a Large-Scale Agile Development Program
Software development projects have undergone remarkable changes with the
arrival of agile development methods. While intended for small, self-managing
teams, these methods are increasingly used also for large development programs.
A major challenge in programs is to coordinate the work of many teams, due to
high uncertainty in tasks, a high degree of interdependence between tasks and
because of the large number of people involved. This revelatory case study
focuses on how knowledge work is coordinated in large-scale agile development
programs by providing a rich description of the coordination practices used and
how these practices change over time in a four year development program with 12
development teams. The main findings highlight the role of coordination modes
based on feedback, the use of a number of mechanisms far beyond what is
described in practitioner advice, and finally how coordination practices change
over time. The findings are important to improve the outcome of large
knowledge-based development programs by tailoring coordination practices to
needs and ensuring adjustment over time.Comment: To appear in Project Management Journa
Applications of lean thinking: a briefing document
This report has been put together by the Health and Care Infrastructure Research and Innovation Centre (HaCIRIC) at the University of Salford for the Department of Health.
The need for the report grew out of two main simple questions,
o Is Lean applicable in sectors other than manufacturing?
o Can the service delivery sector learn from the success of lean in manufacturing and realise the benefits of its implementation?The aim of the report is to list together examples of lean thinking as it is evidenced in the
public and private service sector. Following a review of various sources a catalogue of evidence is put together in an organised manner which demonstrates that Lean principles
and techniques, when applied rigorously and throughout an entire organization/unit, they can have a positive impact on productivity, cost, quality, and timely delivery of services
Looking for Reasons behind Success in Dealing with Requirements Change
During development, requirements of software systems are subject to change. Unfortunately, managing changing requirements can take a lot of time and effort. Yet some companies show a better management of changes in requirements than others. Why? What is it that makes some projects deal with changing requirements better than others? We pursue the long term goal of understanding the mechanisms used to successfully deal with change in requirements. In this paper we gather knowledge about the state-of-the-art and the state-of-practice. We studied eight software development projects in four different companies --large and small, inclined toward structured and toward agile principles of development--, interviewing their project managers and analyzing their answers. Our findings include a list of practical (rather than theoretical) factors affecting the ability to cope with small changes in requirements. Results suggest a central role of size as a factor determining the flexibility showed either by the organization or by the software development team. We report the research method used and validate our results via expert interviews, who could relate to our findings
Learning more from crossing levels: Investigating agility at three levels of the organization
Scholars have tried to explain how organizations can build agile teams by
only looking at one level of analysis. We argue in this short paper that
lessons can be learned from organizational science results explaining variance
on three different abstraction levels of organizations. We suggest agility
needs to be explained from organizational (macro), the team (meso), and
individual (micro) levels to provide useful and actionable guidelines to
practitioners. We are currently designing such studies and hope that they will
eventually result in validated measurements that can be used to prevent
companies from investing in the wrong areas when trying to move towards more
agility
- âŠ