Highly Iterative Product Development Process for Engineering Projects

Article Preview

Abstract:

Many companies are exposed to the challenge to fulfill constantly growing heterogeneous costumer requirements and simultaneously deliver the highest quality standards for their products. One way to face these challenges is the highly iterative product development approach. The content of this approach is the division of the current development process in many short and iterative sub processes (sprints). This procedure enables a regular involvement of the customer in the development process and an early validation of the development status which jointly results in costumer-specific and marketable products. As a consequence of this short-cycled approach the requirements for the practiced process of development projects change fundamentally. However, most companies do not know how this new short-cycle development process has to look like for their daily project work. This is due to the fact that most published papers just deal with the description of how the highly iterative methods look like, however, without considering the challenges an implementation in a producing company involves. This paper aims at the presentation of a standard approach for the handling of highly iterative product development projects.

You might also be interested in these eBooks

Info:

Periodical:

Pages:

532-539

Citation:

Online since:

October 2015

Export:

Price:

* - Corresponding Author

[1] M. Mah, How Agile Projects Measure Up, and What This Means to You. In: Agile Product & Project Management Advisory Service Executive Reports, 9. Jg., Nr. 9, 2008, S. 1–20.

Google Scholar

[2] D.F. Rico, H.H. Sayani, S. Sone, The business value of Agile software methods. Maximizing ROI with just-in-time processes and documentation, Fort Lauderdale, FL: J. Ross Pub., (2009).

Google Scholar

[3] H. C. M Leon, J.A. Farris, G. Letens, Improving product development performance through iteration front-loading. IEEE Transactions on Engineering Management 60(3), 2013, p.552–565.

DOI: 10.1109/tem.2012.2228205

Google Scholar

[4] D. Karlström and P. Runeson, Integrating agile software development into stage-gate managed product development, Springer, 2006, pp.203-225.

DOI: 10.1007/s10664-006-6402-8

Google Scholar

[5] A. Kanane, Challenges related to the adoption of Scrum. Case Study of a financial IT company, (2014).

Google Scholar

[6] K. Schwaber, Agile project management with Scrum,: Microsoft Press, (2004).

Google Scholar

[7] R. Pichler, Scrum - agiles Projektmanagement erfolgreich einsetzen, 1. Aufl., Heidelberg: Dpunkt-Verl., (2008).

Google Scholar

[8] P.G. Smith, Flexible product development. Building agility for changing markets, 1. Aufl., San Francisco: Jossey-Bass, (2007).

Google Scholar

[9] P.G. Smith, K. Radeka, Flexible product development for a turbulent world. Is Agile" NPD the answer, In: PDMA Visions Magazine, 33. Jg., Nr. 2, 2009, S. 20–21.

Google Scholar

[10] Oppenheim, B. W., Lean product development flow. In: Systems Engineering, 7. Jg., Nr. 4, 2004, S. 352–376.

Google Scholar

[11] I.M. Baumgart, Modularisierung von Produkten im Anlagenbau, 1. Aufl., Aachen: Mainz, (2005).

Google Scholar

[12] J. Feldhusen, K. -H. Grote, Pahl/Beitz Konstruktionslehre. Methoden und Anwendung erfol-greicher Produktentwicklung, 8., vollst. überarb. Aufl., Berlin [u. a. ]: Springer, (2013).

DOI: 10.1007/978-3-642-29569-0

Google Scholar