Search results
1 – 10 of over 3000Teemu Lappi and Kirsi Aaltonen
Agile methodologies are widely used to manage the technical complexity of software development, and project governance can provide feasible means of organizational support for…
Abstract
Purpose
Agile methodologies are widely used to manage the technical complexity of software development, and project governance can provide feasible means of organizational support for complex project success. The purpose of this paper is to: analyze the project governance practices of public sector organizations, illustrate what kind of impact these practices have on agile software projects and describe the tensions of agile project governance.
Design/methodology/approach
The research is based on qualitative research strategy and applies elaborative logic with analyses of three case projects in the Finnish public sector.
Findings
The findings of the research describe how project governance practices can be categorized into six dimensions: business case, contracting, controlling, steering, decision-making and capability building. The results illustrate how these practices either support or detract the performance of agile projects. The results also show that there are two interfaces to agile project that create most tensions to governance – the public sector and technology.
Originality/value
The study contributes to both project management and information and communication technology theories by combining technical aspects of agile methodologies with micro-level project governance practices. The study also adds original value to academics by introducing the new concept of “agile project governance.” The results of this study will allow public sector project organizations to design appropriate governance mechanisms for agile projects, and to identify the challenges and tensions that need to be considered and managed in the process.
Details
Keywords
Su Voon Khoo, Nur Hairani A. Rahman and Nurul Liyana M. Kamil
The purpose of this paper is to evaluate the influence of budgeting process elements (budget participation, preparation, implementation and evaluation) on budget performance of…
Abstract
Purpose
The purpose of this paper is to evaluate the influence of budgeting process elements (budget participation, preparation, implementation and evaluation) on budget performance of government.
Design/methodology/approach
A cross-sectional survey was administered among budget officers from government agencies, departments, and units in Malaysia. Descriptive and regression analyses were used to examine the relationship between the budgeting process and budget performance.
Findings
The findings revealed the significant influence of the two predictors: (1) budget participation and (2) budget implementation and evaluation, on budget performance. Both have positive and significant impacts on budget performance. However, budget preparation appeared to have no significant relationship with budget performance, although there is positive effect.
Originality/value
This study provides empirical evidence on the budgeting process factors that influence budget performance. The findings hopefully are of interest to government officials, especially frontline bureaucrats, who seek to ensure that budget performance meets expectations in Malaysia and other countries.
Details
Keywords
The authors reviews the leadership responsibilities involved in managing an organization that practices Agile management.
Abstract
Purpose
The authors reviews the leadership responsibilities involved in managing an organization that practices Agile management.
Design/methodology/approach
Outlines the best practices of major corporations that have adopted Agile processes both for teams and C-suite leadership.
Findings
Agile leaders spend less time reviewing the work of subordinates. They add value by adapting corporate strategies, leading critical agile teams, spending time with customers, mentoring individuals and coaching teams.
Practical implications
It is the C-suite leadership’s responsibility to establish and maintain a hierarchy of competence rather than a bureaucratic hierarchy of authority.
Originality/value
Describes how top management at some of the world’s largest and most successful corporations are adopting Agile practices to spur innovation and promote continuously adding customer vale.
The purpose of this paper is to examine the views of the author, who has written extensively on the management tools needed for continuous innovation, and who believes that an…
Abstract
Purpose
The purpose of this paper is to examine the views of the author, who has written extensively on the management tools needed for continuous innovation, and who believes that an Agile management process methodology that has revolutionized software development, has the potential to transform manufacturing.
Design/methodology/approach
The paper offers a glimpse of what Agile manufacturing will look like from the experience of Wikispeed, a California C‐Corporation that in three months developed a functional road‐safety‐legal automobile prototype able to travel 100 miles per gallon.
Findings
At Wikispeed as in Agile software development, work proceeds by trying to identify what customers want, defining those wants in terms of precisely articulated tests, prioritizing which tests are to be worked on, working in short cycles to deliver features or products that meet the tests, finding out from customers whether that's what they really want, and then continuing the cycle once again.
Research limitations/implications
The Wikispeed case is reported on.
Practical implications
In the Agile process, self‐organizing teams work in short cycles called “sprints” and develop the features and products in a series of projects or modules to facilitate rapid, customer‐valued innovation.
Originality/value
With Agile, the work of project teams enables a firm's product to continuously evolve in the light of the experience they gain and through customer feedback.
Details
Keywords
- Radical transformation of manufacturing
- Auto manufacturing
- In‐shoring plans
- radical management techniques
- Agile manufacturing
- Self‐organizing teams
- Rapid innovation
- Continuous product evolution
- Wikispeed
- Product owner role
- an Agile budget
- Customer‐visible value
- Manufacturing industries
- Manufacturing systems
Subhas C. Misra and Virender Singh
Software development life cycle (SDLC) has always been the core methodology for any software engineer that depicts the entire development process which an organization is bound to…
Abstract
Purpose
Software development life cycle (SDLC) has always been the core methodology for any software engineer that depicts the entire development process which an organization is bound to utilize to achieve successful software. The purpose of this paper is to bring forth a conceptual model after analysing the best practices in SDLC, and extracting the best out of agile methodologies and the open source software, thereby bringing forward an optimised structure.
Design/methodology/approach
The OASDLC is hypothesized specifically for “Brihaspati” project and is formulated keeping in mind the gaps and limitations posed by existing SDLC models. OASDLC is further put to test for achieving lower costs and efforts involved. The tests are further substantiated by means of hypothesis validation through execution of a survey based research.
Findings
It has been observed that the present conceptual model further optimizes the efforts involved while adopting such a practice.
Originality/value
This paper proposes a novel SDLC model so as to achieve a best practice for a software project. On analysing the issues involved such as tight budget and timelines, it led the authors to formulate a newer concept “Open Agile Software Development Life Cycle model” (OASDLC).
Details
Keywords
Keratiloe Mogotsi, Amanda Bowen and Clare Mitchell
The learning outcomes focus on enabling higher-order learning for students to critically assess Agile project management in philanthropic settings, specifically compare and…
Abstract
Learning outcomes
The learning outcomes focus on enabling higher-order learning for students to critically assess Agile project management in philanthropic settings, specifically compare and contrast Agile project management versus traditional project management in the context of a non-profit organisation (The Solidarity Fund) during a crisis; discuss and evaluate the role and contribution of philanthropy during times of crisis; rate the value additions and contributions of Agile approaches in philanthropy; evaluate the phases of Agile (unconventional) project management executed by The Solidarity Fund; and develop a review of the impact of the work done by The Solidarity Fund in terms of the approach that the Fund used. How effective/not effective was it?
Case overview/synopsis
Chaos, crisis and confusion: the three “C”s that succinctly condense the status quo during the COVID-19 pandemic. The roles and contributions of non-profit organisations gained recognition as countries worldwide responded to the crisis to save lives and livelihoods.
In South Africa, there was a sense of urgency and considerable pressure for a multi-stakeholder approach led by the government to save as many South African lives as possible. The conditions, however, were the opposite of traditional project management methodologies that advocate for the management of the triple constraints, namely, cost, time and scope.
How could cost be managed in a project without a set budget and which was reliant on philanthropy? How could time be managed without a set deadline and while tackling an invisible enemy – a virus that changed dynamics on a daily basis and – how could scope be managed in a context where the future was increasingly uncertain?
Complexity academic level
This case study can be useful for students undertaking postgraduate diploma in business, master of business administration (MBA), master of management courses.
Supplementary material
Teaching notes are available for educators only.
Subject code
CSS 11: Strategy.
Details
Keywords
Early research into Agile approaches explored particular practices or quantified improvements in code production. Less well researched is how Agile teams are managed. The project…
Abstract
Purpose
Early research into Agile approaches explored particular practices or quantified improvements in code production. Less well researched is how Agile teams are managed. The project manager (PM) role is traditionally one of “command and control” but Agile methods require a more facilitative approach. How this changing role plays out in practice is not yet clearly understood. The purpose of this paper is to provide insight into how adopting Agile techniques shape the working practices of PMs and critically reflect on some of the tensions that arise.
Design/methodology/approach
An ethnographic approach was used to surface a richer understanding of the issues and tensions faced by PMs as Agile methods are introduced. Ethnographic fiction conveys the story to a wider audience.
Findings
Agile approaches shift responsibility and spread expert knowledge seeming to undermine the traditional PM function. However, the findings here show various scenarios that allow PMs to wrest control and become more of a “gate-keeper”. Ethnographic fiction communicates a sense of the PMs frustration with the conflict between the need to control and the desire for teams to take more responsibility.
Originality/value
Stories provide insight and communicate the experiential feel behind issues faced by PMs adopting Agile to surface useful knowledge. The objective is not how to measure knowledge, but how to recognize it. These reflections are valuable to fellow researchers as well as practitioners and contribute to the growing literature on Agile project management.
Details
Keywords
Pallavi Srivastava and Shilpi Jain
Scrum, an agile software development method, has gained major interest among software development organizations. The scrum master should be well equipped with specific leadership…
Abstract
Purpose
Scrum, an agile software development method, has gained major interest among software development organizations. The scrum master should be well equipped with specific leadership traits and exhibit leadership behavior to effectively manage his/her team. However, in a distributed team, which is spread across geographies, having scrum master to lead the project team at each location is not viable. Therefore, every member in the team is expected to have the capability to become one. This paper aims to explore the leadership mechanisms desired for effective functioning of distributed self-organized scrum team members, leading to project success and overall customer satisfaction.
Design/methodology/approach
A qualitative research methodology with an open-ended questionnaire is followed by semi-structured in-depth interviews. The unit of analysis is a scrum master.
Findings
The qualitative findings unearth the kind of leadership mechanisms required for scrum masters and the team members in a self-organizing scrum team, leading to their project success and customer satisfaction. It includes a set of leadership approaches and behaviors explicitly related to the role of scrum masters. Both inductive and deductive approaches are used to develop a leadership framework applicable for distributed self-organized scrum teams.
Research limitations/implications
The proposed framework can be empirically tested with a large number of teams and more software organizations.
Practical implications
Organizations can use these identified specific leadership approaches and behaviors as parameters for identifying and selecting the potential scrum masters. They can be further trained on them to be an effective scrum master.
Originality/value
There is scant literature on the leadership mechanisms necessary for distributed scrum teams and their impact on project performance. This paper addresses this gap.
Details
Keywords
Albi Thomas and M. Suresh
This study aims to identify the agile-sustainability readiness factors and analyze them in the context of health-care organization. In this study, agile-sustainability refers to…
Abstract
Purpose
This study aims to identify the agile-sustainability readiness factors and analyze them in the context of health-care organization. In this study, agile-sustainability refers to “adapt to the changing environment and respond quickly by maximum using the resources as well as supporting the three pillars of sustainability”.
Design/methodology/approach
The “total interpretive structural modelling” (TISM) is used to examine the interrelationships of the identified readiness factors, and to classify the identified readiness factors based on its power to drive and depend on other factors, “Matrice d’impacts croisés multiplication appliquée á un classment (MICMAC) analysis” was used.
Findings
This study used a “literature review and experts’ opinion” to identify ten agile-sustainability preparedness characteristics. Organizational leadership, multi-skilled and multi-knowledgeable employees and decision-making autonomy were identified as critical elements in this study.
Research limitations/implications
The research focuses primarily on readiness for agile-sustainability in health-care sector.
Practical implications
This research aids health-care administrators and managers in their decision-making. This study suggests that the evaluation of the readiness factors would promote in raising service standards, ensuring an agile and sustainable health-care operations. The readiness elements that support effective implementation of agile-sustainability in health care require a higher priority from health-care management.
Originality/value
This study created a structural model for health-care organizations based on the TISM-based preparedness for agile-sustainability framework, which is a novel effort for adopting agile-sustainability in health care.
Details
Keywords
The author contrasts 20th Century hierarchical management with Agile influenced 21st Century management, which is more suited to modern realities.
Abstract
Purpose
The author contrasts 20th Century hierarchical management with Agile influenced 21st Century management, which is more suited to modern realities.
Design/methodology/approach
Understanding how 20th Century and 21st Century management differ offers an evidenced-based theory why today’s leading firms are leading and why yesterday’s giants are flailing.
Findings
For 21st Century management – the pioneering mode of Agile enterprises and of leading Silicon Valley firms, as well as individual businesses in Europe and China–the goal of the firm is to create customers.
Practical implications
Because the firm’s goal is to create value for customers in a dynamic environment, sustainable strategy must incorporate creating new businesses that attract new customers.
Originality/value
The author compares and contrasts the practices, principles, processes and mindsets of 20th Century management and those of the leading 21st Century firms that have become the most valuable firms on the planet as well as the leading global brands.