Linking business and requirements engineering: is solution planning a missing activity in software product companies?

Lehtola, Laura; Kauppinen, Marjo; Vähäniitty, Jarno; Komssi, Marko

doi:10.1007/s00766-009-0078-8

Cited by 27 publications

(14 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…First a holistic collaborative work involving multiple stakeholders from business and software functions whereby speeding continuous planning and innovation of ideas [13]. Second continuously deploying of software builds through automating software delivery processes and eliminating wastes and this is known as continuous delivery [14].…”

Section: B Devopsmentioning

confidence: 99%

Enhancing Lean Software Development by using Devops Practices

Farid¹,

Helmy²,

Bahloul³

2017

ijacsa

View full text Add to dashboard Cite

Abstract-Competition between companies has made a great pressure to produce new features continuously as fast as possible, subsequently successful software companies needs to learn more about customers and get new features out to them more rapidly. Lean software development cannot integrate between development and operation teams. DevOps enables this merge between them and creates operational parts as one part of the development process and made it up to date during the development phase, so reduced errors during the deployment. The purpose of this paper is to investigate how one can use devOps practices to improve the performance of lean software development production process and introduce a new framework that merge lean and devOps process. The research has been evaluated on a sample of 2 departments in Faculty of Commerce at Helwan University. The results of this work have led to reduce the response delivery time for customers and rapid feedback provides accurate expectations for customer needs that lead to lower levels of deployment pains and lower change fail rates.

show abstract

Section: B Devopsmentioning

confidence: 99%

Enhancing Lean Software Development by using Devops Practices

Farid¹,

Helmy²,

Bahloul³

2017

ijacsa

View full text Add to dashboard Cite

show abstract

“…The only form of continuous planning is that which emerges from agile development approaches and is related to sprint iterations or at best, software releases, and is not widespread throughout the organization. However, just as agile seeks to enable software development to cope with frequent changes in the business environment, the nature of the business environment also requires that planning activities be done more frequently to ensure alignment between the needs of the business context and software development [37], and also requires a tight integration between planning and execution [32]. Given the ongoing interest in autonomous systems, it is also interesting that Knight et al [32] identify continuous planning as a key prerequisite for delivering autonomous systems.…”

Section: Continuous Planningmentioning

confidence: 99%

Continuous software engineering and beyond: trends and challenges

Fitzgerald

Stol

2014

Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering

142

113

View full text Add to dashboard Cite

Throughout its short history, software development has been characterized by harmful disconnects between important activities e.g., planning, development and implementation. The problem is further exacerbated by the episodic and infrequent performance of activities such as planning, testing, integration and releases. Several emerging phenomena reflect attempts to address these problems. For example, the Enterprise Agile concept has emerged as a recognition that the benefits of agile software development will be suboptimal if not complemented by an agile approach in related organizational function such as finance and HR. Continuous integration is a practice which has emerged to eliminate discontinuities between development and deployment. In a similar vein, the recent emphasis on DevOps recognizes that the integration between software development and its operational deployment needs to be a continuous one. We argue a similar continuity is required between business strategy and development, BizDev being the term we coin for this. These disconnects are even more problematic given the need for reliability and resilience in the complex and data-intensive systems being developed today. Drawing on the lean concept of flow, we identify a number of continuous activities which are important for software development in today's context. These activities include continuous planning, continuous integration, continuous deployment, continuous delivery, continuous verification, continuous testing, continuous compliance,continuous security, continuous use, continuous trust, continuous run-time monitoring, continuous improvement (both process and product), all underpinned by continuous innovation. We use the umbrella term, "Continuous *" (continuous star) to identify this family of continuous activities.

show abstract

“…Continuous planning at the project level is done in relation to what is known (e.g., looking two to four weeks forward), the plan is for the next iteration and the work that will be for today. Various industrial experiences (e.g., Lehtola et al, 2007Lehtola et al, , 2009) of companies have shown that they perform open-ended planning with a pre-defined rhythm. However, while planning can be undertaken at regular intervals, the horizon of the future is not fixed.…”

Section: Overviewmentioning

confidence: 99%

“…Company planning is often performed looking only one to two releases ahead, with planning for the near future given greater detail than for the remote future, which is only roughly outlined. Open-ended planning is an effective form of market-driven planning that understands decisions as involving various trade-offs between now and later (Lehtola et al, 2007(Lehtola et al, , 2009.…”

Section: Overviewmentioning

confidence: 99%

Continuous planning: an important aspect of agile and lean development

Suomalainen

Kuusela

Tihinen

2015

IJASM

View full text Add to dashboard Cite

Continuous planning is a relatively new and not yet fully studied field of research, especially from the perspective of agile and lean development organisations. To augment the knowledge in this field, this article presents both a literature review and empirical findings from three case studies that reveal how companies conduct continuous planning. The results indicate that continuous planning is not commonly adopted and applied throughout these organisations and that it currently involves only a certain kind of planning (e.g., release planning). The results of this study bring to light that the main elements of continuous planning (i.e., organisational, strategic and business planning) are tightly related to each other and thus should be considered when companies seek to improve their planning processes and practices. The importance of continuous planning will only increase dramatically in turbulent business environments that include ever shorter planning cycles and the need to improve transparency and knowledge-sharing in organisations.

show abstract

Linking business and requirements engineering: is solution planning a missing activity in software product companies?

Cited by 27 publications

References 20 publications

Enhancing Lean Software Development by using Devops Practices

Enhancing Lean Software Development by using Devops Practices

Continuous software engineering and beyond: trends and challenges

Continuous planning: an important aspect of agile and lean development

Contact Info

Product

Resources

About